New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
MYSQL crashing and restarting
Hi guys,
I've been trying to locate the cause of this issue but not been able to, my mysql on my KVM VPS is crashing and auto rebooting.
I've already tried increasing the size of the ibd log file, also tried running a repair on the databases but i'm not sure what else I can try.
151206 17:11:19 [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.
151206 17:11:19 [Note] Plugin 'FEDERATED' is disabled.
151206 17:11:19 InnoDB: The InnoDB memory heap is disabled
151206 17:11:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151206 17:11:19 InnoDB: Compressed tables use zlib 1.2.8
151206 17:11:19 InnoDB: Using Linux native AIO
151206 17:11:19 InnoDB: Initializing buffer pool, size = 128.0M
151206 17:11:19 InnoDB: Completed initialization of buffer pool
151206 17:11:19 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 45255578280
151206 17:11:19 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 45255671032
151206 17:11:19 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 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
151206 17:11:20 InnoDB: Waiting for the background threads to start
151206 17:11:21 InnoDB: 5.5.46 started; log sequence number 45255671032
151206 17:11:21 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
151206 17:11:21 [Note] - '127.0.0.1' resolves to '127.0.0.1';
151206 17:11:21 [Note] Server socket created on IP: '127.0.0.1'.
151206 17:11:21 [Note] Event Scheduler: Loaded 0 events
151206 17:11:21 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.46-0ubuntu0.14.04.2-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
22:11:27 UTC - mysqld got signal 11 ;
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.
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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=10
max_threads=151
thread_count=5
connection_count=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fad79ac2270
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 = 7fad7437be98 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fad779e6ec0]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fad778d1025]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fad76660340]
/usr/sbin/mysqld(+0x603485)[0x7fad77af8485]
/usr/sbin/mysqld(+0x572a23)[0x7fad77a67a23]
/usr/sbin/mysqld(+0x59d5e1)[0x7fad77a925e1]
/usr/sbin/mysqld(+0x59db21)[0x7fad77a92b21]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x2a)[0x7fad778d4b6a]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x557)[0x7fad77863647]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0xc4c)[0x7fad777bb63c]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x551)[0x7fad777bcba1]
/usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x4e)[0x7fad777bd46e]
/usr/sbin/mysqld(+0x33733e)[0x7fad7782c33e]
/usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x570)[0x7fad7783cd50]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x220)[0x7fad7783d810]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x4a5)[0x7fad77828155]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xcb)[0x7fad77823ecb]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x144)[0x7fad778246f4]
/usr/sbin/mysqld(+0x2f0ef0)[0x7fad777e5ef0]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2860)[0x7fad777edac0]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x160)[0x7fad777f1f90]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1df2)[0x7fad777f4522]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x7fad77881126]
/usr/sbin/mysqld(handle_one_connection+0x41)[0x7fad77881181]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fad76658182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fad75d7b47d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fad2c019460): is an invalid pointer
Connection ID (thread ID): 208
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Comments
try use mysqltuner.pl check issues
What CPU is it running on?
Its running on L5520. I meanwhile restored /var/lib/mysql from my backups which fixed the issue though its weird what happened.
You crashed and recovery failed.
Never mind, I was thinking of TSX crashing pthread. But your CPU is too old to have TSX instructions.