Drush error on Acquia Cloud Free sites

Drush error on Acquia Cloud Free sites

7 posts / 0 new
Last post
f.elnatour@alhayat.com's picture
f.elnatour
Points: 1
Drush error on Acquia Cloud Free sites

Hello,

Today I noticed that drush on a site we have on Acquia Cloud Free in not working any more. We first noticed it when we could not synchronize the DB using Acquia Dev Desktop. After a bit of investigation, I checked Drush on the server and it was showing errors.

It is unlikely that this is an application-related problem, and it seems more like a platform-related issue, because we have our site hosted only on Dev environment but nevertheless executing $drush status on the Test environment (which has nothing yet) also shows the same error. Also, another free application that we have on the same free server also has the same issue.

The error showing is:

$ ssh user.env@free-someId.devcloud.hosting.acquia.com

$ drush status

Fatal error: Call to undefined function pm_drush_command() in /usr/local/drush8/vendor/drush/drush/commands/core/core.drush.inc on line 1065
Drush command terminated abnormally due to an unrecoverable error.                                                                      [error]
Error: Call to undefined function pm_drush_command() in /usr/local/drush8/vendor/drush/drush/commands/core/core.drush.inc, line 1065

Please help.

Status: 
Unresolved
f.elnatour@alhayat.com's picture
f.elnatour
Points: 1

We are still having this issue. Anybody else also experiencing the same problem?

Status Change: 
Unresolved
dmyburgh's picture
david.myburgh
Points: 99

You can try "drush cc drush" to update drush's list of commands and then retry "drush status". Also go into your site's docroot folder and try drush status from there.

f.elnatour@alhayat.com's picture
f.elnatour
Points: 1

Thanks David for the suggestion. Unfortunately, this did not work. :(

I got the same error when performing any of the suggested commands

Fatal error: Call to undefined function pm_drush_command() in /usr/local/drush8/vendor/drush/drush/commands/core/core.drush.inc on line 1065
Drush command terminated abnormally due to an unrecoverable error.                                                                      [error]
Error: Call to undefined function pm_drush_command() in /usr/local/drush8/vendor/drush/drush/commands/core/core.drush.inc, line 1065
greg@salsadigital.com.au's picture
greg
Points: 0

Also having issues with a free AC site. These are some of the errors we are getting when trying to run drush commands:

drush cc all
Unable to create /home/[sitename]/.drush/cache/default.                                                                                                                             [error]
Unable to create /mnt/tmp/[sitename]f9enuhdxgg/drush-[sitename].                                                                                                                      [error]
Drush must have a writable cache directory; please insure that one of the following locations is writable: /home/[sitename],/mnt/tmp/[sitename]f9enuhdxgg                             [error]

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 130968 bytes) in /usr/local/drush8/vendor/drush/drush/includes/filesystem.inc on line 362

and:

fopen(): Filename cannot be empty filesystem.inc:422                                                                                      [warning]
fwrite() expects parameter 1 to be resource, boolean given filesystem.inc:423                                                             [warning]
stream_get_meta_data() expects parameter 1 to be resource, boolean given filesystem.inc:424                                               [warning]
fclose() expects parameter 1 to be resource, boolean given filesystem.inc:426                                                             [warning]
fopen(): Filename cannot be empty filesystem.inc:422                                                                                      [warning]
fwrite() expects parameter 1 to be resource, boolean given filesystem.inc:423                                                             [warning]
stream_get_meta_data() expects parameter 1 to be resource, boolean given filesystem.inc:424                                               [warning]
fclose() expects parameter 1 to be resource, boolean given filesystem.inc:426                                                             [warning]
sh: 1: Syntax error: redirection unexpected
Unable to create /home/[sitename]/.drush/cache/complete.                                                                                      [error]
Unable to create /mnt/tmp/[sitename]zvebkk2rgn/drush-[sitename].                                                                                [error]
Drush must have a writable cache directory; please insure that one of the following locations is writable:                                  [error]
/home/[sitename],/mnt/tmp/[sitename]zvebkk2rgn
Unable to create /home/[sitename]/.drush/cache/complete.                                                                                      [error]
Unable to create /mnt/tmp/[sitename]zvebkk2rgn/drush-[sitename].                                                                                [error]
Drush must have a writable cache directory; please insure that one of the following locations is writable:                                  [error]
/home/[sitename],/mnt/tmp/[sitename]zvebkk2rgn
No Drupal site found, only 'drush' cache was cleared.                                                                                     [warning]

What we notice as a bug on the admin UI (that lead us to the drush errors) is that in the Views admin UI, when any field is clicked, the various sections in the settings dialog ("Style settings", "No results behavior", "Rewrite results" and "More") are not rendered as links, so cannot be expanded. This happens with any view and any field.

The same code and db work fine on our local.

greg@salsadigital.com.au's picture
greg
Points: 0

Ignoring the 2 spam comments above :) ...

Just wanted to report back that our issue was due to reaching our space quota. Removing files and db backups making more space seems to have sorted things out for us.

dmyburgh's picture
david.myburgh
Points: 99

Grrr. Spam removed! Thanks for reporting back with the solution, Greg.