focus
By:
focus

Weekly backups causing database crash

May 12, 2015 1.6k views
MySQL Backups WordPress Ubuntu

Every Saturday night when a backup runs it crashes our site. We will either end up with a db connection error or just a white screen. Below are the mysql error logs. I've tried going through SSH and repairing the tables it lists as crashed and it says they successfully repair but then the next Saturday it crashes again and I get the same errors.

150510 7:56:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150510 7:56:41 [Note] Plugin 'FEDERATED' is disabled.
150510 7:56:41 InnoDB: The InnoDB memory heap is disabled
150510 7:56:41 InnoDB: Mutexes and rwlocks use GCC atomic builtins
150510 7:56:41 InnoDB: Compressed tables use zlib 1.2.8
150510 7:56:41 InnoDB: Using Linux native AIO
150510 7:56:41 InnoDB: Initializing buffer pool, size = 128.0M
150510 7:56:41 InnoDB: Completed initialization of buffer pool
150510 7:56:41 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib
logfiles!
150510 7:56:41 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
150510 7:56:41 InnoDB: Waiting for the background threads to start
150510 7:56:42 InnoDB: 5.5.37 started; log sequence number 189133924
150510 7:56:42 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150510 7:56:42 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150510 7:56:42 [Note] Server socket created on IP: '127.0.0.1'.
150510 7:56:42 [Note] Event Scheduler: Loaded 0 events
150510 7:56:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.37-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './phpmyadmin/pmarecent' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './phpmyadmin/pma
recent'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wpaiowpsloginactivity' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
aiowpsloginactivity'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wplayerslider' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
layerslider'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wpoptions' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
options'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wppostmeta' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
postmeta'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wpposts' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
posts'
150510 7:56:43 [ERROR] /usr/sbin/mysqld: Table './wordpress/wpusermeta' is marked as crashed and should be repaired
150510 7:56:43 [Warning] Checking table: './wordpress/wp
usermeta'

1 comment
  • You are running out of memory.... has nothing to do with the backups unless that's consuming memory. To fix it. You either need to add more memory, or tune your services to use less memory.

1 Answer

This question was answered by @thinkingmedia:

You are running out of memory.... has nothing to do with the backups unless that's consuming memory. To fix it. You either need to add more memory, or tune your services to use less memory.

View the original comment

Have another answer? Share your knowledge.