> drush up -vd
...
The external command could not be executed due to an application error. [error]

and only after applying attached patch im am able to debug what happens (in my case sweaver freaks out).

daring to set major as quite some issues in the queue smell like they can be smashed with this.

but in the end i think we should fix this one level deeper: #1547432: drush_invoke_process() should default to integrate errors
which would obsolete this patch.

Comments

geek-merlin’s picture

Status: Active » Needs review
StatusFileSize
new944 bytes
mrf’s picture

Status: Needs review » Reviewed & tested by the community

Just applied this patch and everything now works as expected. Instead of just telling me there was an error I can see what the error is that is preventing execution (in my case a PHP fatal in a module).

It would have taken a lot more detective work on my end to figure the reason behind the failure without the patch.

greg.1.anderson’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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

Ace Cooper’s picture

Priority: Major » Normal
Status: Closed (fixed) » Active

This isn't really fixed. I still get the same error trying to run updatedb on my shared hosting (my setup):

#drush updatedb
The following updates are pending:
...
Do you wish to run all pending updates? (y/n): y
The external command could not be executed due to an application error. [error]
Finished performing updates. [ok]

However, I still managed to finish all the updated with usual update.php in browser without any warnings.

greg.1.anderson’s picture

Status: Active » Closed (fixed)

Drush does not support php-cgi.