mysql mariadb keeps crashing
160206 2:01:04 [Note] InnoDB: Memory barrier is not used
160206 2:01:04 [Note] InnoDB: Compressed tables use zlib 1.2.7
160206 2:01:04 [Note] InnoDB: Using Linux native AIO
160206 2:01:04 [Note] InnoDB: Not using CPU crc32 instructions
160206 2:01:04 [Note] InnoDB: Initializing buffer pool, size = 3.0G
160206 2:01:05 [Note] InnoDB: Completed initialization of buffer pool
160206 2:01:05 [Note] InnoDB: Highest supported file format is Barracuda.
160206 2:01:05 [Note] InnoDB: Log scan progressed past the checkpoint lsn 22820778979
160206 2:01:05 [Note] InnoDB: Database was not shutdown normally!
160206 2:01:05 [Note] InnoDB: Starting crash recovery.
160206 2:01:05 [Note] InnoDB: Reading tablespace information from the .ibd files...
160206 2:08:15 [Note] InnoDB: Restoring possible half-written data pages
160206 2:08:15 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 22820795360
160206 2:08:16 [ERROR] mysqld: Can't create/write to file '/tmp/ibucgqi1' (Errcode: 2 "No such file or directory")
2016-02-06 02:08:16 7f93b531b080 InnoDB: Error: unable to create temporary file; errno: 2
2016-02-06 02:08:16 7f93b531b080 InnoDB: Assertion failure in thread 140272376852608 in file dict0dict.cc line 1111
InnoDB: Failing assertion: dict_foreign_err_file
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 5.6 Reference Manual :: 14.18.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
160206 2:08:16 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see Reporting Bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.0.23-MariaDB-cll-lve
key_buffer_size=268435456
read_buffer_size=131072
max_used_connections=0
max_threads=502
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1364472 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x3d)[0xbcb4cd]
/usr/sbin/mysqld(handle_fatal_signal+0x515)[0x725db5]
/lib64/libpthread.so.0(+0xf100)[0x7f93b4f06100]
/lib64/libc.so.6(gsignal+0x37)[0x7f93b36b95f7]
/lib64/libc.so.6(abort+0x148)[0x7f93b36bace8]
/usr/sbin/mysqld[0x9ffdc0]
/usr/sbin/mysqld[0x9f7968]
/usr/sbin/mysqld[0x973ef7]
/usr/sbin/mysqld[0x8ab7c5]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x727c04]
/usr/sbin/mysqld[0x5db75d]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x551)[0x5dcbd1]
/usr/sbin/mysqld[0x53ca2a]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x546)[0x540eb6]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f93b36a5b15]
/usr/sbin/mysqld[0x53527d]
Keeps getting the above on our CL 7 cpanel server. my.cnf file contents: [mysqld] slow-query-log=1 long-query-time=1 slow-query-log-file="/var/log/mysql-slow.log" log-error="/var/log/mysqld.log" local-infile=0 max_connections=500 max_user_connections=30 key_buffer = 128M thread_stack = 128K thread_cache_size = 8 table_cache = 5192 max_heap_table_size = 256M query_cache_limit = 4M query_cache_size = 512M wait_timeout=60 connect_timeout=20 join_buffer_size = 128K tmp_table_size = 16M max_heap_table_size = 256M table_open_cache = 8192 key_buffer_size = 256M innodb_file_per_table innodb_buffer_pool_size = 3G # This is crucial to avoid checkpointing all the time: innodb_log_file_size = 512M max_allowed_packet=268435456 top - 02:29:51 up 29 min, 1 user, load average: 1.36, 1.30, 0.91 Tasks: 270 total, 1 running, 268 sleeping, 0 stopped, 1 zombie %Cpu(s): 3.3 us, 1.3 sy, 0.1 ni, 76.8 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 10070616 total, 551064 free, 1906332 used, 7613220 buff/cache KiB Swap: 7812092 total, 7812092 free, 0 used. 7595780 avail Mem
-
160206 2:08:16 [ERROR] mysqld: Can't create/write to file '/tmp/ibucgqi1' (Errcode: 2 "No such file or directory") 2016-02-06 02:08:16 7f93b531b080 InnoDB: Error: unable to create temporary file; errno: 2 2016-02-06 02:08:16 7f93b531b080 InnoDB: Assertion failure in thread 140272376852608 in file dict0dict.cc line 1111
What is the permission and disk space status of your /tmp directory ?0 -
Hello :) Please ensure you have available disk space and inodes on the /tmp partition: df -h df -i
Thank you.0
Please sign in to leave a comment.
Comments
2 comments