Timeline for HTTP error 500 when backup entire site
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 13, 2017 at 14:38 | comment | added | rovr138 | That MySQL error is usually due to reaching a limit on MySQL. You're going to have to break it into chunks. Would running backup-and-migrate locally be an option? You can use mysqldump to get a database and run your process locally. | |
| Mar 13, 2017 at 14:37 | answer | added | Wim Mostrey | timeline score: 2 | |
| Mar 13, 2017 at 14:33 | comment | added | MarkDQ | @rovr138 I added the error message received by the web host provider | |
| Mar 13, 2017 at 14:32 | history | edited | MarkDQ | CC BY-SA 3.0 |
added the error message received by the web host provider
|
| Mar 12, 2017 at 2:51 | answer | added | Travis Johnston | timeline score: 1 | |
| Mar 11, 2017 at 23:44 | comment | added | rovr138 |
It's hard from this data to point to anything. But if a smaller backup works, I'm leaning towards memory. Instantiate top and try creating it. If it's not memory, maybe a timeout. For both, check your apache configuration.
|
|
| Mar 11, 2017 at 23:08 | history | asked | MarkDQ | CC BY-SA 3.0 |