Site offline error when connecting to DB...
qbnflaco - August 26, 2009 - 19:33
| Project: | Backup and Migrate |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I don't know if it's just my default install of acquia drupal stack with no password, but whenever I try doing a backup of the default db, it gives me the site offline screen. It even happens when I try to do a download of the file.
#1
*no password for mysql user
#2
Is there an error on the offline screen (like cannot connect to db or similar) or is it the standard site offline message text?
#3
standard offline text message.
#4
There was an error below it...
The mysqli error was: Can't connect to MySQL server on '127.0.0.1' (10061).
Could this be because the acquia drupal stack uses port 33066? I would think this was being read directly from the settings.php file which has it correct.
#5
This will sound obvious, but have you checked to see if the
Take site offlineoption is checked in theAdvanced Backup\Advanced Options?Also this option is not putting the site back online after the backup finished, instead it give page-not-found error.
#6
same thing if that option is checked or not.
#7
Is there any php extension that is required for this? Acquia removes alot of the unneeded extensions for php. THen again I guess it would have given me a php error. Just putting this out there.
#8
It is in fact reading the info from the settings.php but I guess I've never tried this with a non-standard port and don't suse Acquia's stack myself. Does your db connection string have a port in it (ie mysqli://user:pass@sever:port/dbname)? If that's the case then I suppose that port could be being lost when the settings are read.
#9
yes it does have the port number in it.
#10
Can you try the latest dev release? Some port handling code went into the module (for an unrelated issue) and it will hopefully take care of this issue. Reopen if it doesn't
#11
Automatically closed -- issue fixed for 2 weeks with no activity.