Hi,

after upgrading to Drush-Head, I'm unable to use the stand-alone Drush anymore. This applies for Drupal installations of version 5 and 6 unter Debian GNU/Linux, and FreeBSD. In all environments the module version of Drush was working fine. Before "upgrading" to HEAD, I deleted the directory ./sites/all/modules/drush, but did not disable/uninstall the module (should I have done this?). The error message:

Drush was not able to start (bootstrap) Drupal.                                                                                 [error]
Hint: This error can only occur once the database connection has already been succesfully initiated, therefor this error
generally points to a site configuration issue, and not a problem connecting to the database.

On the shell promt, some very strage outputs appear:

Drush was attempting to connect to : 
  [...]
  Database Name     : drupal
  Database Name     : ...
  Database          : Connected
  Drupal Bootstrap  : Successful
  [...]

Greetings, -asb

* The field "Database Name" appears twice, in the second appearance it's the database password, not the database name.
* The error says above: "Drush was not able to start (bootstrap) Drupal". The error below says: "Drupal Bootstrap: Successful". Now what?

Comments

adrian’s picture

adrian commented
Status: Active » Needs work

It was setting the bootstrap phase, BEFORE the actual bootstrap was attempted. So that's fixed.
I also fixed the duplicate name of the field.

This is only to make the error message make sense, and doesn't fix the actual issue with it not bootstrapping, so please test again.

Run the command with the '--verbose=2' option, which will give you a lot more context as to what is going wrong.

Unfortunately for us DRUSH_BOOTSTRAP_DRUPAL_FULL is a bit of a black box. It's very tricky to get useful error messages out of that, and all we can do is try to fail gracefully when something goes wrong.

Please let me know once you've debugged further.

asb’s picture

asb commented

Hi Adrian,

thanks for the quick reply; if things don't work anymore, they tend to show how incredibly useful they are if they work ;)

# drush --verbose=2 status
Found command: status                                                                                                           [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 6.10 root directory at /var/www/drupal                                                                        [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]

Fatal error: Cannot redeclare pm_drush_help() (previously declared in /var/www/drupal2/sites/all/modules/drush/commands/pm/pm.drush.inc:29) in /var/www/drupal/sites/all/modules/drush_extras/pm.drush.inc on line 67
Drush was not able to start (bootstrap) Drupal.

Drush is called from /var/www/drupal and aliased to /var/www/drupal2/sites/all/modules/drush/drush.php, so the "previously declared..." statement seems to be correct correct; however, the reference to /var/www/drupal/sites/all/modules/drush_extras/pm.drush.inc is irritating since the "drush_extras" module is (was) installed, but is disabled (but not deleted). After deleting the module's folder, Drush started working again on this D6 site.

Calling Drush from /var/www/drupal2 - a D5 site - results in a slightly different behaviour; on this site, "drush_extras" was deleted already. Output:

# drush --verbose=2 status
Found command: status                                                                                                           [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal2                                                                         [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login()                                                                         [bootstrap]
[...]

# drush --verbose=2 refresh
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal2                                                                         [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login()                                                                         [bootstrap]
The command 'drush.php refresh' could not be executed.

Same error with --uri http://fqdn or other parameters ("The command 'drush.php http://www.mysite.com watchdog show' could not be executed." etc.)

On another D6 site, Drush partially works better:

# drush --verbose=2 refresh
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 6.10 root directory at /var/www/drupal3                                                                      [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Found command: refresh                                                                                                          [bootstrap]
Including version specific file : /var/www/drupal2/sites/all/modules/drush/commands/pm/update_info/drupal_6.inc                    [notice]
Refreshing update status information ...
Done.
[...]
# drush --verbose=2 update
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 6.10 root directory at /var/www/drupal3                                                                      [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Found command: update                                                                                                           [bootstrap]
Including version specific file : /var/www/drupal2/sites/all/modules/drush/commands/core/drupal/update_6.inc                       [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 30720 bytes) in /var/www/drupal3/modules/locale/locale.install on line 100

But:

# drush --verbose=2 cron
[...]
Found command: cron                                                                                                             [bootstrap]
Cron run successfully.

On a forth - D5 - site, it goes like this:

# drush --verbose=2 status
Found command: status                                                                                                           [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal4                                                                    [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login()
[...]

# drush --verbose=2 refresh
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal4                                                                    [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login()                                                                         [bootstrap]
The command 'drush.php refresh' could not be executed.

# drush --verbose=2 update
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal4                                                                    [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Found command: update                                                                                                           [bootstrap]
Including version specific file : /var/www/drupal2/sites/all/modules/drush/commands/core/drupal/update_5.inc                       [notice]

[OK, but:]

# drush --verbose=2 upgrade
Drush bootstrap phase : _drush_bootstrap_drupal_root()                                                                          [bootstrap]
Initialized Drupal 5.16 root directory at /var/www/drupal4                                                                    [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site()                                                                          [bootstrap]
Initialized Drupal site default at sites/default                                                                                [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()                                                                 [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database()                                                                      [bootstrap]
Successfully connected to the Drupal database.                                                                                  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full()                                                                          [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login()                                                                         [bootstrap]
The command 'drush.php upgrade' could not be executed.                                                                          [error]

Strange, very strange... Either I'm making major mistakes, or the old Drush versions were working a lot better, especially on D5.

Thanks for any hints!
-asb

adrian’s picture

adrian commented
Status: Needs work » Postponed (maintainer needs more info)

Firstly :
you have the drush_extras module still hanging around. you need to delete all instances of it.

Secondly :
The 'refresh' command requires the 'update' module to be enabled on the site.

Thirdly :
In the latest HEAD, we changed the update command into 'updatedb', the command that was upgrade was renamed to 'updatecode',
and the plan is to create a 'update' command eventually that does an updatecode and then an updatedb, but this hasn't happened yet.

You should use the 'help' command, which will show you a list of all the commands that you can use in that specific context.

The php memory error you will need to change your php.ini settings to avoid.

mojzis’s picture

mojzis commented

I think the instructions to remove drush_extras should be somewhere (on the project page ?) in bold for a while ...

asb’s picture

asb commented

> you have the drush_extras module still hanging around. you need to delete all instances of it.

As stated above, after noticing the error regarding drush_extras, I deleted it from all sites. Without exception. "drush_extras" is gone. Really.

> The 'refresh' command requires the 'update' module to be enabled on the site.

What kind of module or extension is this? On drupal.org, there's no "update" module ("No projects found in this category"). At my D5 sites, I've installed and enabled update status and upgrade status modules; in D6, those are in core already, more or less. Or am I missing something?

> In the latest HEAD, we changed the update command into 'updatedb', the command that was upgrade was renamed to 'updatecode'

# drush updatecode
The command 'drush.php updatecode' could not be executed.                                                                       [error]

> You should use the 'help' command, which will show you a list of all the commands that you can use in that specific context.

Good idea since currently this seems to change on a daily basis. With the most recent version from HEAD, there seems to be no equivalent for "upgrade" anymore (that "updatecode" you mentioned above ;)

# drush help | grep updatecode
{{{nothing}}}

> The php memory error you will need to change your php.ini settings to avoid.

Maybe, but not probable. The site and /admin/reports/updates are running fine, PHP's memory_limit is "24M" and there are very few modules. Why would PHP-CLI require more memory than the operational website?

Final question: Is Drush currently still a tool for end users (like site admins/sysops), or is it for coders/developers only?

Greetings, -asb

mojzis’s picture

mojzis commented

Update :
It is one of the core optional - "update status"

adrian’s picture

adrian commented

What kind of module or extension is this? On drupal.org, there's no "update" module ("No projects found in this category"). At my D5 sites, I've installed and enabled update status and upgrade status modules; in D6, those are in core already, more or less. Or am I missing something?

The update module is for d6, the update_status is used for D5. I don't actually think that command will work as is at present on D5.

> In the latest HEAD, we changed the update command into 'updatedb', the command that was upgrade was renamed to 'updatecode'

# drush updatecode
The command 'drush.php updatecode' could not be executed. [error]

You need to have specified both --root and --uri , or be in the site directory of the site you are working on.
if the sites is sites/default you don't need to specify --uri, and you may simply be in the drupal root.

> You should use the 'help' command, which will show you a list of all the commands that you can use in that specific context.
Good idea since currently this seems to change on a daily basis. With the most recent version from HEAD, there seems to be no equivalent for "upgrade" anymore (that "updatecode" you mentioned above ;)
# drush help | grep updatecode
{{{nothing}}}

Same as above, the command is only available if you have a site you can call it on available.

> The php memory error you will need to change your php.ini settings to avoid.
Maybe, but not probable. The site and /admin/reports/updates are running fine, PHP's memory_limit is "24M" and there are very few modules. Why would PHP-CLI require more memory than the operational website?

Your error message stated :

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 30720 bytes) in /var/www/drupal3/modules/locale/locale.install on line 100

Some operating systems have separate php.ini files for modphp and php-cli, debian comes to mind.
check the applicable php.ini file.

Final question: Is Drush currently still a tool for end users (like site admins/sysops), or is it for coders/developers only?

Drush 2.x is currently being actively developed and is heading for Alpha 2 at present, with an almost complete rewrite in between.
It's still intended as a tool for sysadmin/sysops, and it will function far better for the purpose than it previously has.
Here's a small writeup of SOME of the changes that have happened in the last month : http://groups.drupal.org/node/20625

It's going to get a lot more stable shortly, as the major refactoring work has been completed.

mojzis’s picture

mojzis commented

adrian THANKS for the php.ini hint ! I've been counting my bytes for the last 2 hours :-) I think this should go somewhere into the readme probably ...

asb’s picture

asb commented
Status: Postponed (maintainer needs more info) » Postponed

[D5]

> I don't actually think that command will work as is at present on D5.

That explains the problems, if currently drush can't be used to upgrade D5 sites modules anymore (all commands from above were run from each site's root).

Still I don't understand why the previous and working version was unpublished, forcing users to "upgrade" to alpha code that - at least currently - can't functionally fully replace the unpublished (but stable) release version. However, I don't want to waste any more of your time discussing this.

A notice/warning on the project page stating that (a) currently there's no supported and fully functional Drush for D5 sites, and (b) that end-users like site admins/sysops currently shouldn't use Drush-Head since the code is actively developed and thus not ready for production environments would be helpful.

Changing status to "postponed" and hoping that support for D5 will be added soon again.

Thanks & greetings, -asb

adrian’s picture

adrian commented
Status: Postponed » Fixed

Turns out it does work. I tested it myself.

You need to
a) drush.php dl update_status
b) log into the site and enable the update_status module. the enable command is d6 only
c) drush.php refresh
d) drush.php update

asb’s picture

asb commented

Hi,

downloaded the newly published Alpha2 for D5, uncompressed it in my home directory, pointed alias to the new location, and deleted all "drush" directories from the /sites/all/modules directories. Indeed, this version/configuration behaves differently. I think, running Drush from outside Drupal's module directories seems to be crucial.

* D5 success: 1 site
* D5 failed/errors: 5 sites
* D6 success: 5 sites
* D6 failed/errors: 1 sites

D5 failure #1 (site "ci", running drush from the site's root as user "root"):

# drush refresh
Refreshing update status information ...
Done.
# drush update
[...]
Code updates will be made to the following projects:
Create from Web [createfromweb-]

Note: Updated modules can potentially break your site. It's not recommended to update production sites without prior testing.
Note: A backup of your package will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Do you really want to continue? (y/n): y
Unable to download  to /var/www/ci/sites/all/modules/ from                                                                 [error]
Updating project createfromweb failed. Restoring previously installed version.                                                  [error]
Backups were saved into the directory /var/www/ci/backup/modules/20090416191911.                                           [ok]
Cache cleared.
An error occurred at function : core_cache_clear                                                                                [error]
You should now run `drush updatedb` or visit update.php through your browser.
An error occurred at function : pm_updatecode                                                                                   [error]
An error occurred at function : pm_update                                                                                       [error]

D5 failures #2 and #3 (sites "fo", "ec" and several others, each running drush from the site's root):

(identical error with site "ci")

D5 failure #4 (site "em", running drush from the site's root):

# drush update
Refreshing update status information ...
Done.
Update information last refreshed: 16. April 2009 - 19:04

Update status information on all installed and enabled Drupal modules:
  Name  Installed version       Proposed version        Status
  ----  -----------------       ----------------        ------

No code updates available.                                                                                                      [ok]

As it appears, Drush thinks that no modules are enabled/installed. That is not quite true - on this site we're running quite a bunch of modules (~90, including Drupal core); according to /admin/logs/updates, three of them have Updates available. Something seems to be broken here.

D6 failure #1 (site "ed", running drush from the site's root as user "asb"; that one's on FreeBSD 7.0 thus the different paths):

# drush refresh
PHP Notice:  Undefined variable: options in /usr/home/asb/drush/includes/command.inc on line 71
Notice: Undefined variable: options in /usr/home/asb/drush/includes/command.inc on line 71
PHP Notice:  Undefined index:  custom in /usr/home/asb/drush/includes/context.inc on line 93
Notice: Undefined index:  custom in /usr/home/asb/drush/includes/context.inc on line 93
PHP Notice:  Constant DRUSH_PM_NO_VERSION already defined in /usr/home/asb/drush/commands/pm/pm.drush.inc on line 34
Notice: Constant DRUSH_PM_NO_VERSION already defined in /usr/home/asb/drush/commands/pm/pm.drush.inc on line 34
PHP Notice:  Undefined index:  path in /usr/home/asb/drush/includes/environment.inc on line 417
Notice: Undefined index:  path in /usr/home/asb/drush/includes/environment.inc on line 417
PHP Warning:  session_start(): Cannot send session cookie - headers already sent by (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 1029
PHP Warning:  session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 1029
PHP Warning:  Cannot modify header information - headers already sent by (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 630
PHP Warning:  Cannot modify header information - headers already sent by (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 631
PHP Warning:  Cannot modify header information - headers already sent by (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 632
PHP Warning:  Cannot modify header information - headers already sent by (output started at /usr/home/asb/drush/includes/command.inc:71) in /usr/local/www/.../includes/bootstrap.inc on line 633
Refreshing update status information ...
Done.

Greetings, -asb

moshe weitzman’s picture

moshe weitzman commented
Assigned: Unassigned » owen barton

That D6 output has no failures. It just has a lot of notices which we will fix in next alpha. See #435010: PHP NOTICE for a workaround.

Grugnog2 may look into the D5 errors.

asb’s picture

asb commented

Hi,

don't get me wrong; I love Drush a lot, I like to use it on a regular basis, and I think that the rewrite was a very huge leap in the right direction (providing the groundwork to get something like the maintenance section of Mediawiki into Drupal). The only real complaint I had was the lack of properly updated information, but that has been fixed mostly in the meantime. Thank you very much for the work you're doing on Drush!

That said, I think the issue about Drush-HEAD not being able to bootstrap is fixed (I think it works again since I moved the "Drush" directory out of Drupal's ./modules directory, as stated on the project page); as my last report showed, the failures are now caused by other issues; to summarize shortly:

* 4 of the D5 sites have the "Createfromweb" module installed; this module has been unpublished/revoked. As it seems, Drush can't handle this special case properly (yet). On my D6 sites I have no unpublished/revoked modules running, so I can't tell if this only applies for D5 sites.
* The complete failure of Drush on one of the D5 sites (empty modules list) seems to be an exception; this might be caused by something completely different; however, at the moment only "Drush" operations are affected (I experienced such an empty modules list before on another D5 site, but there ./admin/build/modules was also falsly empty).
* The errors/warnings on the D6 installation on FreeBSD 7.0 might have other causes, also; currently I'm getting a "500 Internal Error" from the webserver (Lighttpd), and other Drush operations don't work at all; I think, using Drush with D6 is pretty safe at the moment, so this seems to be an exception/special case, also.

Maybe it would be best to open new issues for the remaining problems, as far as Drush is afected?

Thanks & greetings, -asb

bramface’s picture

bramface commented
Status: Closed (fixed) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jrdixey’s picture

jrdixey commented
Version: » All-versions-3.1
Priority: Critical » Major
Status: Fixed » Active

I had a very similar problem after updating Drush to All-versions-3.1 (the current recommended version). My intention was to start using it for maintenance and updates instead of Drush 2. This is with a Drupal 6.15 install.

Roughly, this is what I did:
- used Drush 2 to take the site offline using drush eval command
- downloaded and unzipped Drush 3.1 into the /home/drush directory (where I had previously run Drush 2)
Drush 'could not execute', so after a little investigating ...
- downloaded the Console_Table PEAR package and dropped it into home/drush/includes, renamed to table.inc
(as recommended here: http://joachimwillems.be/node/36)
Drush still wouldn't run, so after a bit more investigating ...
- configured drushrc.php to use the correct db, using the example file as a guide, and dropped it into home/drush
(I've not had to do this before, but figured Drush 3 might require it)
- listed all modules into a file (modulelist.txt), then disabled them using the .txt file as input, with Drush 3.1
(this is the way I usually disabled modules with Drush 2)

The drush disable command grumbled that I should have used drush pm-disable, so I re-ran with the correct command:
drush pm-disable `cat modulelist.txt`

Got the following error:

Fatal error: Unsupported operand types in /home/drupal/includes/form.inc on line 517
Drush command could not be completed.

This was displayed at the end of a list of all the modules that Drush reported had been disabled.

At this point I could not re-enabled the modules, take the site out of maintenance mode, or run any other Drush commands; attempting to run Drupal from the browser with ?q=user to force login also produced a bootstrap error (strangely enough, not quite the same one) and a WSOD.

So, I restored from backup files and database. No harm done, but I thought I should submit this error and see if I can find out how to avoid it in future (aside from going back to using Drush 2.x).

I poked around a little bit and found that there is a new syntax available in Drush 3:
drush pm-disable `drush pm-list --pipe --type=module --status=enabled`

Is this the preferred way to do it, rather than using drush pm-list to output the list first and then importing it to drush pm-disable?

BTW if reopening this issue is not the right thing to do, let me know and I'll start a new issue instead.

greg.1.anderson’s picture

greg.1.anderson commented
Category: bug » support

- downloaded and unzipped Drush 3.1 into the /home/drush directory (where I had previously run Drush 2)

I hope that you removed drush 2, and did not mash the two together...

Generally speaking, you can pm-update your drupal installation without disabling all of your modules first.

I can't tell what might have caused your problem above.

jrdixey’s picture

jrdixey commented

Ha ha, no, I didn't mash the two together - I changed the name of the "drush" directory to "drush-2", then created a new directory "drush", then unzipped the Drush 3.1 files into it.

Good to have that confirmed, about not having to disable the modules first - it's been a while since I've done a core update but I think I'd already started doing it without disabling modules. Maybe I would have run into this before in Drush 2 if I'd tried that previously, I don't know. (I'll try it today on a test version of the site and see what happens though.)

One other thing I'd forgotten about but found in my notes:
Before I attempted to disable all the modules, I ran drush cache-clear with no arguments. I saw an error related to the fgets command (sorry no further details recorded). Cache-clear all ran with no errors.

greg.1.anderson’s picture

greg.1.anderson commented

Your error message in #16 is a drupal message, not a drush message; could be that you're having trouble with a drupal module.

jrdixey’s picture

jrdixey commented

Yes, it's a Drupal error. What I was wondering was whether the pm-disable process in Drush might have modified the Drupal code (bootstrap) in such a way that it could have caused the error message. I do have a lot of modules though, so disabling them one by one for the upgrade (or not disabling them at all) might be a good idea.

greg.1.anderson’s picture

greg.1.anderson commented

I've upgraded drupal 6.5 or so to 6.17 without disabling modules, and I've upgraded 6.15 to 6.17 with drush without any problems.

There is one example I can think of where the drush bootstrap is different than the browser bootstrap is that the browser will always set the base url correctly, whereas drush will set the uri to whatever the --uri (or -l) parameter is. If you're using site aliases, the uri passed to drush must be the name of the folder that contains settings.php (e.g. 'default'), which can cause problems with some modules. Try drush -r /path/to/root -l http://youruri.com pmdisable modulename and see if this works better than drush -r /path/to/root -l default pm-disable modulename if there is a difference in your configuration. Doing this one module at a time would help isolate the problem.

jrdixey’s picture

jrdixey commented

Hi Greg, Sorry for the delay in answering this - I moved back to Drush 2 and did the security updates without disabling modules. But I will try this again with Drush 3 when I get a chance. Feel free to close this if you want to.

owen barton’s picture

owen barton commented
Component: Code » PM (dl, en, up ...)
Status: Active » Closed (cannot reproduce)

This looks like some kind of broken module dependency perhaps, but there is not much we can do without a way to reproduce it reliably. If you can simplify the issue to a concise set of steps please reopen and we can take a look.

sheldonkreger’s picture

sheldonkreger commented

I am running XAMPP on Ubuntu to build a Drupal 7.12 site locally.

"drush dl example" worked after I changed some file permissions to allow writing and execution. However, "drush en example" did not work.

The solution is to visit your site's "settings.php" file and make the following changes:
OLD CODE (Line 203 for me):

$databases = array (
  'default' => 
  array (
    'default' => 
    array (
      'database' => 'mydatabase',
      'username' => 'myusername',
      'password' => 'mypw',
      'host' => 'localhost',
      'port' => '',
      'driver' => 'mysql',
      'prefix' => '',
    ),
  ),
);

NEW CODE:

$databases = array (
  'default' => 
  array (
    'default' => 
    array (
      'database' => 'mydatabase',
      'username' => 'myusername',
      'password' => 'mypw',
      'host' => '127.0.0.1',
      'port' => '',
      'driver' => 'mysql',
      'prefix' => '',
    ),
  ),
);

In short, I changed the value of 'host' to 127.0.01 rather than "localhost". Great victory.

bis20’s picture

bis20 commented

AFTER 1 Day Confusing:

Just change "sqli" to "sql" (if mysql supported) in settings.php.

this solve my problem. :)

Screenack’s picture

Screenack commented

FYI for those researching their problem #24 threw me a bone.

My settings.php file is using conditional logic based on this statement:

switch($_SERVER['SERVER_NAME'])

wherein matching db connection string statements will load. However, drush doesn't parse settings.php in this manner so I had to populate the default switch with the correct database. Problem solved.