No success goes un-sabotaged

Submitted by Drupalguy on Thu, 10/23/2014 - 20:28

No success goes un-sabotaged

Currently my sites are on Aegir and I must admit that their performance is noticeably better. This gives me incentive to work to keep things on the Aegir Platform but things still are not great. With the new code update I ran into more issues.

Before you can upgrade on Aegir you have to run a "verify" (which is good) and all but one of the sites passed. If a site does not pass you are stuck, you cannot do anything to it. You cannot update, backup, enable, delete, nothing. The error I was getting was totally useless. The error I was getting was:

"Drush was not able to start (bootstrap) the Drupal database."
"Hint: This may occur when Drush is trying to:
* bootstrap a site that has not been installed or does not have a
configured database.In this case you can select another site with
a working database setup by specifying the URI to use with the
--uri parameter on the command line. See `drush topic docs-aliases`
for details.
* connect the database through a socket. The socket file may be
wrong or the php-cli may have no access to it in a jailed shell.
See for details.

I tried, Aegir Help, Google and was not able to find much information as to what action to take.
The lack of documentation (as well as the ambiguity of what information that was out there) leaves a lot to be desired. I did finally figure out what the difficulty was. As it turns out the issue was related to Drush. Drush does not use the site configuration to get it's information to access the database. Instead it stores the information in the "drushrc.php" file in the sites folder for that particular site (since in Aegir that information is no longer in the settings.php file). The drushrc.php file for the particular site that was having this difficulty could not find the database information for the site (of course the error could not say that). So all I had to do was edit the drushrc.php file adding the database info and the site was finally able to verify.

The guy who writes these error messages needs to learn how to speak English and in a way that expresses the problem in a more obvious way (instead of in techno-code).

Blog tags