MySQL crashing

emagine_alex

• March 24, 2014 10:35

Had mysql crash twice in two days, kind of randomly. [Removed] Nothing was going on the first time, the second had somewhat of a decent load. Never had this happen on a box before. Anyone seen this error?

• 

  emagine_alex

  • March 24, 2014 17:30

  Here is the ulimit [~]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 15634 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 15634 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

  0
• 

  cPanelMichael

  • March 31, 2014 12:53

  Hello :) Please ensure you paste the notable part of the error messages directly in this thread using the code tags. Thank you.

  0
• 

  emagine_alex

  • March 31, 2014 15:40

  140325 21:17:05 InnoDB: Waiting for the background threads to start 140325 21:17:06 InnoDB: 5.5.36 started; log sequence number 4479295 140325 21:17:06 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 140325 21:17:06 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 140325 21:17:06 [Note] Server socket created on IP: '0.0.0.0'. 140325 21:17:06 [Note] Event Scheduler: Loaded 0 events 140325 21:17:06 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 140331 15:23:55 mysqld_safe Number of processes running now: 0 140331 15:23:55 mysqld_safe mysqld restarted 140331 15:23:59 [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. 140331 15:24:00 [Note] Plugin 'FEDERATED' is disabled. 140331 15:24:00 InnoDB: The InnoDB memory heap is disabled 140331 15:24:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140331 15:24:00 InnoDB: Compressed tables use zlib 1.2.3 140331 15:24:00 InnoDB: Using Linux native AIO 140331 15:24:03 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137363456 bytes) failed; errno 12 140331 15:24:03 InnoDB: Completed initialization of buffer pool 140331 15:24:03 InnoDB: Fatal error: cannot allocate memory for the buffer pool 140331 15:24:03 [ERROR] Plugin 'InnoDB' init function returned error. 140331 15:24:03 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140331 15:24:04 [ERROR] Unknown/unsupported storage engine: InnoDB 140331 15:24:04 [ERROR] Aborting 140331 15:24:05 [Note] /usr/sbin/mysqld: Shutdown complete
  

  0
• 

  cPanelMichael

  • April 07, 2014 18:26

  Could you paste the contents of your /etc/my.cnf file? Thanks.

  0
• 

  emagine_alex

  • April 08, 2014 20:57

  [mysqld] innodb_buffer_pool_size = 1024M max_connections = 200 key_buffer = 32M myisam_sort_buffer_size = 32M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1024 thread_cache_size = 286 interactive_timeout = 25 wait_timeout = 1000 connect_timeout = 10 max_allowed_packet = 16M max_connect_errors = 10 query_cache_limit = 1M query_cache_size = 16M query_cache_type = 1 tmp_table_size = 16M [mysqld_safe] open_files_limit = 10192 [mysqldump] quick max_allowed_packet = 16M [myisamchk] key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 16M local-infile=0 [COLOR="silver">- - - Updated - - - Still crashing, and it starting to more and more now.

  0
• 

  cPanelMichael

  • April 09, 2014 18:09

  The following output in your MySQL error log is relevant here: [QUOTE]140331 15:24:03 InnoDB: Fatal error: cannot allocate memory for the buffer pool
  Is this a VPS? If so, do you notice any fail counts for parameters in /proc/user_beancounters? How much memory is available on the server? Thank you.

  0

Please sign in to leave a comment.