I am running drush -vd updb --yes || exit 1 to upgrade D6 to D7 then I got this error several times atleast.

Bootstrap to phase 0. [0.01 sec, 4.79 MB]                            [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drush() [0.01 sec, 5.08 MB] [bootstrap]
Cache HIT cid: 5.0-commandfiles-0-eae08ebb5299072299ae95f485024c57 [0.02 sec, 5.09 MB]                                                                                                                                               [debug]
Bootstrap to phase 0. [0.06 sec, 11.02 MB]                                                                                                                                                                                       [bootstrap]
Bootstrap to phase 2. [0.08 sec, 11.03 MB]                                                                                                                                                                                       [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_root() [0.09 sec, 11.03 MB]                                                                                                                                                      [bootstrap]
Initialized Drupal 7.14 root directory at /var/www/vhosts/git/html [0.12 sec, 15.06 MB]                                                                                                                                          [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site() [0.12 sec, 15.07 MB]                                                                                                                                                      [bootstrap]
Initialized Drupal site default at sites/default [0.12 sec, 15.07 MB]                                                                                                                                                               [notice]
Cache MISS cid: 5.0-commandfiles-2-d0694fde84f442a7d33c2119cff575f2 [0.13 sec, 15.07 MB]                                                                                                                                             [debug]
Cache SET cid: <em class="placeholder">5.0-commandfiles-2-d0694fde84f442a7d33c2119cff575f2</em> [0.27 sec, 15.09 MB]                                                                                                                 [debug]
Found command: updatedb (commandfile=core) [0.28 sec, 16.05 MB]                                                                                                                                                                  [bootstrap]
Segmentation fault

Any idea what is segmentation fault is?

1 Answer 1


Drupal is very sensitive to the order you do things when doing a major system upgrade. You must follow the instructions in UPGRADE.txt exactly; in particular, if you run updatedb just once, after upgrading your core and all of your contrib code, then the upgrade is sure to go wrong. The symptoms can vary; I would expect that this is probably what is causing your segmentation fault.

If you look at the UPGRADE.txt instructions closely, you will see that you need to run updatedb on core only, with no contrib modules enabled; after that, you must upgrade your contrib modules one at a time, upgrading their code and then running updatedb for each one. If a module that has a schema in the database has update hooks that need to run, then updatedb will run them, even if the module is not enabled, so you must be extremely exacting in your code management, or the upgrade will fail. It is also critical that you upgrade your modules in the right order, because a module will clearly need to have its dependencies available in order to successfully complete its updatedb processes. If you have a lot of modules, this process can be extremely tedious.

The Drush Site Upgrade command can be used to automate this process to a large degree. There are still some things that you need to do manually, but it will walk you through the UPGRADE.txt instructions one step at a time, offering to do most of the steps for you automatically. It will even give you advice about replacement modules for some contrib projects not available in D7, and will run the content migrate code to insure that you CCK content gets upgraded too.

If you go through all of the steps faithfully, and you are still getting a segmentation fault, it could be that your system is running out of memory. Adjust your settings in php.ini to adjust. If this still doesn't work, you could be encountering a bug in a contrib module. When this happens, you can try asking for support in the issue queue of the particular module that is causing you problems. If this does not get you anywhere, your final resort is to build a new Drupal 7 site from scratch using similar modules, and migrate your data using Drupal to Drupal migration. In the futue, Drush Site Upgrade will also support the d2d upgrade path, but for now you'll need to do it manually.

Postscript: Understanding what a segmentation fault is is not really important to solving your problem, but there is a good definition on Wikipedia here: http://en.wikipedia.org/wiki/Segmentation_fault.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.