Description:
the mysqld runs for round about a year without problems. last week it happens first time. it happens avery day 1 to 3 times.
i did a filesystemcheck, changed the hardware of the server, reinstalled mysql (binaries and libraries).
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 100903 14:12:29 - mysqld got signal 11;
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: This could be because you hit a bug. It is also possible that this binary
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: or one of the libraries it was linked against is corrupt, improperly built,
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: or misconfigured. This error can also be caused by malfunctioning hardware.
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: We will try our best to scrape up some info that will hopefully help diagnose
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: the problem, but since we have already crashed, something is definitely wrong
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: and this may fail.
Sep 3 14:12:29 d04s5-server01 mysqld[3746]:
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: key_buffer_size=33554432
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: read_buffer_size=131072
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: max_used_connections=106
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: max_connections=500
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: threads_connected=1
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: It is possible that mysqld could use up to
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1120764 K
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: bytes of memory
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Hope that's ok; if not, decrease some variables in the equation.
Sep 3 14:12:29 d04s5-server01 mysqld[3746]:
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: thd=0xace1e7b0
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Attempting backtrace. You can use the following information to find out
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: where mysqld died. If you see no messages after this, something went
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: terribly wrong...
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Cannot determine thread, fp=0xa7e17628, backtrace may not be correct.
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Stack range sanity check OK, backtrace follows:
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x81f2333
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x82f601a
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x82f60ca
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x82f6296
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x82f63ad
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x826d5fa
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x820af37
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x820e08b
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x820eded
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x820fa2a
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0x82103f4
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0xb7f984fb
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: 0xb7dacf5e
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: New value of fp=(nil) failed sanity check, terminating stack trace!
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: stack trace is much more helpful in diagnosing the problem, so please do
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: resolve it
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Trying to get some variables.
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: Some pointers may be invalid and cause the dump to abort...
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: thd->query at 0x8b38ff0 = UPDATE jt_uebernachtungen SET uebernachtungen_ID = '4057',no_nights = '',zi_art = '2',zi_typ = '1',dz_mit = '00073-4058 - Herr Techniker Ton',hotel = '3',reisezeitraum = '3',verzehrgutschein = '1',roomdrop_fr = '',notiz = '',notizintern = '' WHERE uebernachtungen_ID=4057
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: thd->thread_id=4979
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Sep 3 14:12:29 d04s5-server01 mysqld[3746]: information that should help you find out what is causing the crash.
Sep 3 14:12:29 d04s5-server01 mysqld_safe[8071]: Number of processes running now: 0
Sep 3 14:12:29 d04s5-server01 mysqld_safe[8073]: restarted
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: The log sequence number in ibdata files does not match
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: the log sequence number in the ib_logfiles!
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: 100903 14:12:29 InnoDB: Database was not shut down normally!
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: Starting crash recovery.
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: Reading tablespace information from the .ibd files...
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: Restoring possible half-written data pages from the doublewrite
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: InnoDB: buffer...
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: 100903 14:12:29 InnoDB: Started; log sequence number 0 4952241
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: 100903 14:12:29 [Note] /usr/sbin/mysqld: ready for connections.
Sep 3 14:12:29 d04s5-server01 mysqld[8076]: Version: '5.0.51a-3ubuntu5.7-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Sep 3 14:12:53 d04s5-server01 mysqld[8076]: 100903 14:12:53 [ERROR] Got error 127 when reading table './jt_db/jt_uebernachtungen'
Sep 3 14:12:54 d04s5-server01 mysqld[8076]: 100903 14:12:54 [ERROR] Got error 127 when reading tab
resolve_stack_dump:
0x81f2333 handle_segfault + 771
0x82f601a _ZN11Query_cache16invalidate_tableEP17Query_cache_block + 42
0x82f60ca _ZN11Query_cache16invalidate_tableEP8st_table + 42
0x82f6296 _ZN11Query_cache16invalidate_tableEP10TABLE_LIST + 54
0x82f63ad _ZN11Query_cache10invalidateEP3THDP10TABLE_LISTc + 157
0x826d5fa _Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesb + 5018
0x820af37 _Z21mysql_execute_commandP3THD + 18055
0x820e08b _Z11mysql_parseP3THDPKcjPS2_ + 379
0x820eded _Z16dispatch_command19enum_server_commandP3THDPcj + 3149
0x820fa2a _Z10do_commandP3THD + 170
0x82103f4 handle_one_connection + 2164
0xb7f984fb _end + -1350351357
0xb7dacf5e _end + -1352363930
root@d04s5-server01:~#
How to repeat:
the mysqld restarts periodicly, hundreds of times it works and sometimes mysqld got signal 11.
