Closed (fixed)
Project:
Drush
Version:
7.x-4.5
Component:
Core Commands
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
1 Dec 2011 at 10:58 UTC
Updated:
2 Jun 2012 at 10:21 UTC
Hi.
I have several sites, and recently got on one of them this error:
"Drush command terminated abnormally due to an unrecoverable error."
Another site (an exact copy of this one) is working fine.
I tried looking for exit() as described here on similar issues, but could not find anything unusual.
Any idea how to sort this out?
Thanks!
Comments
Comment #1
greg.1.anderson commentedPlease read the section Please do the following when submitting an issue to drush for guidance.
Comment #2
greg.1.anderson commentedComment #3
PvO commentedIs this "Master" also the for windows users like the one on http://drush.ws/drush_windows_installer ?
Comment #4
greg.1.anderson commentedYes. The Windows installer was sync'ed with HEAD on master on 23 November. Pull from master to update Drush on Windows prior to the next reroll of the installer.
Comment #5
PvO commentedSorry, I do not know what you mean by
Do you mean upgrading DRUSH?
Would you be so kind to esplain, maybe give the DRUSH command?
Comment #6
greg.1.anderson commentedSorry, I can't support Drush upgrades on Windows. Please see the git instructions for details.
Comment #8
SyRenity commentedHi.
Sorry for delay in reply.
Following the reference to create issue guide:
* Looked at rest of similar issues - no solution that I can use as I don't know which module causes the issue
* Tried the head version - still happens
* Below is result of running Drush in debug mode:
* Getting the drush status:
Bad site:
Good site:
Thanks in advance!
Comment #9
greg.1.anderson commentedUnless you want to step through the bootstrap in a debugger, the only thing I can suggest is disable about half the modules in the site, and try to isolate which one is causing the problem (enabling / disabling different modules after each test).
Comment #10
SyRenity commentedHow can I use the debugger? Any guidelines for this?
Thanks.
Comment #11
greg.1.anderson commentedSorry, I don't support php debuggers. If you are new to php debugging, then maybe divide-and-conquer will be a more productive technique. Good luck.
Comment #12
jonhattanTypically this happens when a module does a drupal_goto in hook_init unconditionally. In such a case you need to identify the module and ask in its queue to fix it. See #1230132: drupal_goto() kills drush if called in hook_init()