1

I have a LEMP server in a Ubuntu instance and my MySQL are shutting down automatically... I have no idea what's happening.

I had to manually restart it to keep the site online

Here is my mysql log

171228  9:33:37 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use$
171228  9:33:37 [Note] Plugin 'FEDERATED' is disabled.
171228  9:33:37 InnoDB: The InnoDB memory heap is disabled
171228  9:33:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171228  9:33:37 InnoDB: Compressed tables use zlib 1.2.8
171228  9:33:37 InnoDB: Using Linux native AIO
171228  9:33:37 InnoDB: Initializing buffer pool, size = 32.0M
171228  9:33:37 InnoDB: Completed initialization of buffer pool
171228  9:33:37 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!
171228  9:33:37  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...
171228  9:33:37  InnoDB: Waiting for the background threads to start
171228  9:33:38 InnoDB: 5.5.53 started; log sequence number 19047428748
171228  9:33:38 InnoDB: !!! innodb_force_recovery is set to 1 !!!
171228  9:33:38 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
171228  9:33:38 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
171228  9:33:38 [Note] Server socket created on IP: '0.0.0.0'.
171228  9:33:38 [Warning] 'user' entry 'prestashop@%' has both a password and an authentication plugin specified. The password will be ignored.
171228  9:33:38 [Warning] 'user' entry 'tanda@%' has both a password and an authentication plugin specified. The password will be ignored.
171228  9:33:38 [Note] Event Scheduler: Loaded 0 events
171228  9:33:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.53-0ubuntu0.14.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)

[Edit][Solved] Apparently it was lack of memory. I enabled Swap memory and the problem was solved.

  • Seems the end of the log is showing MySQL was up, check your syslog and share that too. – Bhuvanesh Dec 28 '17 at 11:59
  • I had to manually restart it to keep the site online – Renalcio Carlos Junior Dec 28 '17 at 12:02
  • @RenalcioCarlosJunior MySQL is showing a successful recovery after a crash, the interesting part of the log is what is immediately before that, whatever was logged before 171228 9:33:37. I do not think (but do not know for sure) that "The log sequence number in ibdata files does not match" can happen on a clean stop, so you may be facing logical or physical (disk) corruption of your files-- but that is only a speculation until you share the log before the (re)start. – jynus Dec 28 '17 at 21:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.