Public bug reported: On a server dedicated as a MySQL database server, MySQL keeps randomly "terminating with status 1" (from /var/log/daemon.log) and then immediately starting again. MySQL-Server version 5.1.49 seems to include the fix as per this bug entry: http://bugs.mysql.com/bug.php?id=34236
Here are some timestamps from daemon.log from when Mysql terminated: Jul 4 12:53:28 lightning init: mysql main process (9796) terminated with status 1 Jul 4 22:28:31 lightning init: mysql main process (8123) terminated with status 1 Jul 5 04:03:13 lightning init: mysql main process (20731) terminated with status 1 MySQL Error logs describe the following stack trace. probably due to the use of yaSSL when configuring mysql to use ssl. http://bugs.mysql.com/bug.php?id=34236 *** PS: The server uses SSL connections through MySQL *** 110721 11:17:02 - mysqld got signal 11 ; key_buffer_size=524288000 read_buffer_size=131072 max_used_connections=13 max_threads=151 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 842111 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x7f1d3406c780 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 = 0x7f1d3be68e58 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f1d64bb51a9] /usr/sbin/mysqld(handle_segfault+0x404) [0x7f1d648c2884] /lib/libpthread.so.0(+0xf8f0) [0x7f1d641338f0] /usr/sbin/mysqld(yaSSL::SSL_SESSION::GetBornOn() const+0) [0x7f1d64bf1170] /usr/sbin/mysqld(yaSSL::Sessions::Flush()+0x35) [0x7f1d64bf28e5] /usr/sbin/mysqld(yaSSL::sendFinished(yaSSL::SSL&, yaSSL::ConnectionEnd, yaSSL::BufferOutput)+0x5f0) [0x7f1d64bff1d0] /usr/sbin/mysqld(yaSSL_accept+0x114) [0x7f1d64be5194] /usr/sbin/mysqld(+0x636f60) [0x7f1d64b99f60] /usr/sbin/mysqld(+0x369ad6) [0x7f1d648ccad6] /usr/sbin/mysqld(handle_one_connection+0x135) [0x7f1d648cd545] /lib/libpthread.so.0(+0x69ca) [0x7f1d6412a9ca] /lib/libc.so.6(clone+0x6d) [0x7f1d62c6070d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at (nil) is an invalid pointer thd->thread_id=42360 thd->killed=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. 110721 11:17:02 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 110721 11:17:02 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... Package information: ii mysql-server 5.1.41-3ubuntu12.10 MySQL database server (metapackage depending ii mysql-server-5.1 5.1.41-3ubuntu12.10 MySQL database server binaries ii mysql-server-core-5.1 5.1.41-3ubuntu12.10 MySQL database core server files Reproducible: No, it is a random behaviour. It happens after running thousands of queries... ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/828036 Title: MySQL daemon keeps dying and restarting when using ssl connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/828036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
