Error on trying to backup from a C5 install
Permalink
I've been trying to backup a site on C5 but am getting this scary looking error. I know the database is quite large and have managed to back it up from the cpanel of the server but not from within C5. Any ideas what this might be anyone?
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.
Thanks for that John as I was having problems on my test server I thought I would try and rectify the issue and took the plunge and bought your voodoo backup block. However last night I adjusted some settings on your block and the whole site went a bit cranky.
Lost the edit bar at the top and the javascript stopped working. This was before I even ran a backup. I'm now a bit spooked. However the broadband was being very slow at this point. This morning everything is fine but could you tell me can your backup corrupt a live site database? I have taken another backup via phpMyadmin but would like to try your system...
Lost the edit bar at the top and the javascript stopped working. This was before I even ran a backup. I'm now a bit spooked. However the broadband was being very slow at this point. This morning everything is fine but could you tell me can your backup corrupt a live site database? I have taken another backup via phpMyadmin but would like to try your system...
With support issues generally, please open a support request.
http://www.concrete5.org/marketplace/addons/backup-voodoo/support/...
A support request will notify me by PM immediately and will include your environment details. Just posting on the forums, there is a risk that I would miss the post buried beneath 2000 spams for online live soccer streaming :) You could be left wondering why I had not responded.
Anyway, to the details:
When configuring, Backup Voodoo only works with its own database tables and configuration entries.
When running a backup, by default Backup Voodoo puts the site into maintenance mode and then takes it out of maintenance mode when it has completed. To do so requires a change to a single Config table entry that is 'owned' by concrete5 (ie not owned by Backup Voodoo). This is to keep the database and files as stable through the multi-pass process and prevent 'skew' of data. (You can disable this behaviour in the settings tab).
Neither of the above could cause the transient symptoms you describe.
The only point where Backup Voodoo makes big changes to a database is when you use the built in database restore facility. To use that you need to go through multiple warnings, so are unlikely to have done so by accident. If a restore failed, the symptoms would not be transient!
Your description suggests to me that one of more of the c5 core assets that need to be loaded across the web to show a page got lost or corrupted somewhere on the way and the page was incomplete. So it arises from a combination of server, browser and network glitches. Along with the slow broadband, I would be happy with that conclusion. It is something I have experienced myself when doing general site editing and is usually resolved by a browser refresh. A bit like missing posts and double posting on these forums.
It may also be that late at night your server is running various jobs, either c5 jobs or even your hosting companies own maintenance jobs. These could slow the server down and influence the above.
The best diagnostic for such symptoms is to set network traffic recording in the developer console and see what is not loading. However, because this is all transient and nearly all way out of any of our control, even knowing which asset is getting lost on the network, there is nothing you or I can do about it.
W.R.T configuring and running Backup Voodoo, it is safe to configure Backup Voodoo at any time of day. All that does is change Backup Voodoo's own tables. On a live site, I recommend running when the site is unlikely to be busy because it will be in maintenance mode for the short time it takes to run a backup, so site visitors will be locked out during that period.
http://www.concrete5.org/marketplace/addons/backup-voodoo/support/...
A support request will notify me by PM immediately and will include your environment details. Just posting on the forums, there is a risk that I would miss the post buried beneath 2000 spams for online live soccer streaming :) You could be left wondering why I had not responded.
Anyway, to the details:
When configuring, Backup Voodoo only works with its own database tables and configuration entries.
When running a backup, by default Backup Voodoo puts the site into maintenance mode and then takes it out of maintenance mode when it has completed. To do so requires a change to a single Config table entry that is 'owned' by concrete5 (ie not owned by Backup Voodoo). This is to keep the database and files as stable through the multi-pass process and prevent 'skew' of data. (You can disable this behaviour in the settings tab).
Neither of the above could cause the transient symptoms you describe.
The only point where Backup Voodoo makes big changes to a database is when you use the built in database restore facility. To use that you need to go through multiple warnings, so are unlikely to have done so by accident. If a restore failed, the symptoms would not be transient!
Your description suggests to me that one of more of the c5 core assets that need to be loaded across the web to show a page got lost or corrupted somewhere on the way and the page was incomplete. So it arises from a combination of server, browser and network glitches. Along with the slow broadband, I would be happy with that conclusion. It is something I have experienced myself when doing general site editing and is usually resolved by a browser refresh. A bit like missing posts and double posting on these forums.
It may also be that late at night your server is running various jobs, either c5 jobs or even your hosting companies own maintenance jobs. These could slow the server down and influence the above.
The best diagnostic for such symptoms is to set network traffic recording in the developer console and see what is not loading. However, because this is all transient and nearly all way out of any of our control, even knowing which asset is getting lost on the network, there is nothing you or I can do about it.
W.R.T configuring and running Backup Voodoo, it is safe to configure Backup Voodoo at any time of day. All that does is change Backup Voodoo's own tables. On a live site, I recommend running when the site is unlikely to be busy because it will be in maintenance mode for the short time it takes to run a backup, so site visitors will be locked out during that period.
Even so, you could still try and backuop through phpMyAdmin as described in this howto and it may get you round the problem.
http://www.concrete5.org/documentation/how-tos/developers/backup-a-...
Normally I would also suggest my Backup Voodoo addon. But in this case I caution that it would only help if the error arises from running into server resource limits. If it comes from some other cause (as I speculated above), then Voodoo could run into the same problem as the regular backup does.
http://www.concrete5.org/marketplace/addons/backup-voodoo/...