MySQL Forums
Forum List  »  General

MySql crashes
Posted by: Wim Roffel
Date: March 16, 2016 03:59AM

Once every few days my website will be reduced to a white screen with the text "Link to database cannot be established: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)".

I am on an Ubuntu 14 server with Mysql 5.5.47. Until now I have solved the problem with typing "reboot" in the console but I would like to prevent the problem from occurring. I noted that before the reboot the system reported that it contained 7 zombie processes who had gone after the reboot.

My MySQL error log for today looks as follows:
160315 16:20:08 [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.
160315 16:20:08 [Note] Plugin 'FEDERATED' is disabled.
160315 16:20:08 InnoDB: The InnoDB memory heap is disabled
160315 16:20:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160315 16:20:08 InnoDB: Compressed tables use zlib 1.2.8
160315 16:20:08 InnoDB: Using Linux native AIO
160315 16:20:08 InnoDB: Initializing buffer pool, size = 128.0M
160315 16:20:08 InnoDB: Completed initialization of buffer pool
160315 16:20:09 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 238444175
160315 16:20:09 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...
InnoDB: Doing recovery: scanned up to log sequence number 238444644
160315 16:20:09 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
160315 16:20:09 InnoDB: Waiting for the background threads to start
160315 16:20:10 InnoDB: 5.5.47 started; log sequence number 238444644
160315 16:20:10 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160315 16:20:10 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160315 16:20:10 [Note] Server socket created on IP: '127.0.0.1'.
160315 16:20:10 [Note] Event Scheduler: Loaded 0 events
160315 16:20:10 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.47-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
160315 16:20:12 [ERROR] /usr/sbin/mysqld: Table './topsnoep/ps_myparcel' is marked as crashed and should be repaired
160315 16:20:12 [Warning] Checking table: './topsnoep/ps_myparcel'
160315 18:37:16 [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.
160315 18:37:16 [Note] Plugin 'FEDERATED' is disabled.
160315 18:37:16 InnoDB: The InnoDB memory heap is disabled
160315 18:37:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160315 18:37:16 InnoDB: Compressed tables use zlib 1.2.8
160315 18:37:16 InnoDB: Using Linux native AIO
160315 18:37:16 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(135987200 bytes) failed; errno 12
160315 18:37:16 InnoDB: Completed initialization of buffer pool
160315 18:37:16 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160315 18:37:16 [ERROR] Plugin 'InnoDB' init function returned error.
160315 18:37:16 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160315 18:37:16 [ERROR] Unknown/unsupported storage engine: InnoDB
160315 18:37:16 [ERROR] Aborting

160315 18:37:16 [Note] /usr/sbin/mysqld: Shutdown complete

160315 18:37:17 [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.
160315 18:37:17 [Note] Plugin 'FEDERATED' is disabled.
160315 18:37:17 InnoDB: The InnoDB memory heap is disabled
160315 18:37:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160315 18:37:17 InnoDB: Compressed tables use zlib 1.2.8
160315 18:37:17 InnoDB: Using Linux native AIO
160315 18:37:17 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(135987200 bytes) failed; errno 12
160315 18:37:17 InnoDB: Completed initialization of buffer pool
160315 18:37:17 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160315 18:37:17 [ERROR] Plugin 'InnoDB' init function returned error.
160315 18:37:17 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160315 18:37:17 [ERROR] Unknown/unsupported storage engine: InnoDB
160315 18:37:17 [ERROR] Aborting

160315 18:37:17 [Note] /usr/sbin/mysqld: Shutdown complete

160316 5:10:00 [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.
160316 5:10:00 [Note] Plugin 'FEDERATED' is disabled.
160316 5:10:00 InnoDB: The InnoDB memory heap is disabled
160316 5:10:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160316 5:10:00 InnoDB: Compressed tables use zlib 1.2.8
160316 5:10:00 InnoDB: Using Linux native AIO
160316 5:10:00 InnoDB: Initializing buffer pool, size = 128.0M
160316 5:10:00 InnoDB: Completed initialization of buffer pool
160316 5:10:00 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!
160316 5:10:00 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...
160316 5:10:00 InnoDB: Waiting for the background threads to start
160316 5:10:01 InnoDB: 5.5.47 started; log sequence number 238511451
160316 5:10:01 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160316 5:10:01 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160316 5:10:01 [Note] Server socket created on IP: '127.0.0.1'.
160316 5:10:01 [Note] Event Scheduler: Loaded 0 events
160316 5:10:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.47-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

Can someone help me to understand and solve what goes wrong here?

Options: ReplyQuote


Subject
Written By
Posted
MySql crashes
March 16, 2016 03:59AM
March 16, 2016 09:54AM
March 16, 2016 11:06AM
March 16, 2016 11:38AM
March 16, 2016 05:39PM
March 19, 2016 02:56PM
March 19, 2016 10:38PM
March 20, 2016 11:53AM
March 21, 2016 05:12PM
March 25, 2016 07:45AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.