Mysqld Stopping
Posted: Sat May 03, 2014 3:27 pm
Hello
Mysqld is stopping sometimes. (a time per two days)
Here is my log file
InnoDB: mmap(137363456 bytes) failed; errno 12
Is there any script to check if is stopped, start again? Or am i have to change my 512mb droplet to 1GB ram?
Is there any way to get rid of stopping?
Thank you.
Mysqld is stopping sometimes. (a time per two days)
Here is my log file
Code: Select all
140503 17:23:26 mysqld_safe Number of processes running now: 0
140503 17:23:26 mysqld_safe mysqld restarted
140503 17:23:27 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140503 17:23:29 [Note] Plugin 'FEDERATED' is disabled.
140503 17:23:29 InnoDB: The InnoDB memory heap is disabled
140503 17:23:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140503 17:23:29 InnoDB: Compressed tables use zlib 1.2.3
140503 17:23:29 InnoDB: Using Linux native AIO
140503 17:23:29 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140503 17:23:29 InnoDB: Completed initialization of buffer pool
140503 17:23:29 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140503 17:23:29 [ERROR] Plugin 'InnoDB' init function returned error.
140503 17:23:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140503 17:23:29 [ERROR] Unknown/unsupported storage engine: InnoDB
140503 17:23:29 [ERROR] Aborting
140503 17:23:29 [Note] /usr/libexec/mysqld: Shutdown complete
140503 17:23:29 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
#service mysqld start
140503 18:17:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140503 18:17:00 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140503 18:17:00 [Note] Plugin 'FEDERATED' is disabled.
140503 18:17:00 InnoDB: The InnoDB memory heap is disabled
140503 18:17:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140503 18:17:00 InnoDB: Compressed tables use zlib 1.2.3
140503 18:17:00 InnoDB: Using Linux native AIO
140503 18:17:00 InnoDB: Initializing buffer pool, size = 128.0M
140503 18:17:00 InnoDB: Completed initialization of buffer pool
140503 18:17: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!
140503 18:17: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...
140503 18:17:00 InnoDB: Waiting for the background threads to start
140503 18:17:01 InnoDB: 5.5.37 started; log sequence number 2446149
140503 18:17:01 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
140503 18:17:01 [Note] - '127.0.0.1' resolves to '127.0.0.1';
140503 18:17:01 [Note] Server socket created on IP: '127.0.0.1'.
140503 18:17:01 [Note] Event Scheduler: Loaded 0 events
140503 18:17:01 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.37' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
Is there any script to check if is stopped, start again? Or am i have to change my 512mb droplet to 1GB ram?
Is there any way to get rid of stopping?
Thank you.