061214 00:13:04 mysqld started /opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 061214 0:13:06 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 061214 0:13:06 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 061214 0:13:06 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 061214 0:13:06 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 061214 0:13:06 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 061214 0:13:06 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000254' position: 102 061214 0:13:06 [Note] SCHEDULER: Manager thread booting 061214 0:13:06 [Note] SCHEDULER: Loaded 0 events 061214 0:13:06 [Note] SCHEDULER: Suspending operations 061214 0:16:51 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 061214 0:19:57 [Note] /opt/mysql/bin/mysqld: Normal shutdown 061214 0:19:57 [Note] SCHEDULER: Killing manager thread 3 061214 0:19:57 [Note] SCHEDULER: Waiting the manager thread to reply 061214 0:19:57 [Note] SCHEDULER: Resuming operations 061214 0:19:57 [Note] SCHEDULER: Manager thread started with id 3 061214 0:19:57 [Note] SCHEDULER: Shutting down 061214 0:19:57 [Note] SCHEDULER: Waiting for worker threads to finish 061214 0:19:57 [Note] SCHEDULER: Emptying the queue 061214 0:19:57 [Note] SCHEDULER: Stopped 061214 0:21:35 [Note] Slave I/O thread killed while connecting to master 061214 0:21:35 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000013', position 245294931 061214 0:21:35 [Note] Error reading relay log event: slave SQL thread was killed 061214 0:21:35 [Note] /opt/mysql/bin/mysqld: Shutdown complete 061214 00:21:36 mysqld ended 061214 00:26:40 mysqld started 061214 0:26:42 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 061214 0:26:42 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 061214 0:26:42 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 061214 0:26:42 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 061214 0:26:42 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 061214 0:26:42 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000255' position: 102 061214 0:26:42 [Note] SCHEDULER: Manager thread booting 061214 0:26:42 [Note] SCHEDULER: Loaded 0 events 061214 0:26:42 [Note] SCHEDULER: Suspending operations 061214 0:30:27 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 061214 1:39:30 [Note] /opt/mysql/bin/mysqld: Normal shutdown 061214 1:39:30 [Note] SCHEDULER: Killing manager thread 3 061214 1:39:30 [Note] SCHEDULER: Waiting the manager thread to reply 061214 1:39:30 [Note] SCHEDULER: Resuming operations 061214 1:39:30 [Note] SCHEDULER: Manager thread started with id 3 061214 1:39:30 [Note] SCHEDULER: Shutting down 061214 1:39:30 [Note] SCHEDULER: Waiting for worker threads to finish 061214 1:39:30 [Note] SCHEDULER: Emptying the queue 061214 1:39:30 [Note] SCHEDULER: Stopped 061214 1:41:37 [Note] Slave I/O thread killed while connecting to master 061214 1:41:37 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000013', position 245294931 061214 1:41:37 [Note] Error reading relay log event: slave SQL thread was killed 061214 1:41:37 [Note] /opt/mysql/bin/mysqld: Shutdown complete 061214 01:41:38 mysqld ended 061214 02:02:05 mysqld started 061214 2:02:07 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 061214 2:02:07 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 061214 2:02:07 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 061214 2:02:07 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 061214 2:02:07 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 061214 2:02:07 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000256' position: 102 061214 2:02:07 [Note] SCHEDULER: Manager thread booting 061214 2:02:07 [Note] SCHEDULER: Loaded 0 events 061214 2:02:07 [Note] SCHEDULER: Suspending operations 061214 2:05:51 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 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. 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=262144000 read_buffer_size=2093056 max_used_connections=102 max_connections=350 threads_connected=102 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329797 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 061214 03:02:06 mysqld restarted /opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 061214 3:02:08 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 061214 3:02:08 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 061214 3:02:08 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 061214 3:02:08 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 061214 3:02:08 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000257' position: 102 061214 3:02:08 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 061214 3:02:08 [Note] SCHEDULER: Manager thread booting 061214 3:02:08 [Note] SCHEDULER: Loaded 0 events 061214 3:02:08 [Note] SCHEDULER: Suspending operations 061214 3:03:17 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_signature_data' is marked as crashed and should be repaired 061214 3:03:17 [Warning] Checking table: 'ó3' 061214 3:04:31 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_token_data' is marked as crashed and should be repaired 061214 3:04:31 [Warning] Checking table: 'ôŸ' 061214 3:05:53 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 061214 3:05:59 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_stats' is marked as crashed and should be repaired 061214 3:05:59 [Warning] Checking table: 'E±J' 061214 3:24:06 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_virtual_uids' is marked as crashed and should be repaired 061214 3:24:06 [Warning] Checking table: '6Ôá' 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. 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=262144000 read_buffer_size=2093056 max_used_connections=107 max_connections=350 threads_connected=18 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329797 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 070107 01:44:31 mysqld restarted /opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070107 1:45:05 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 1:45:05 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 070107 1:45:05 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 1:45:05 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 070107 1:45:05 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 1:45:05 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000258' position: 102 070107 1:45:05 [Note] SCHEDULER: Manager thread booting 070107 1:45:05 [Note] SCHEDULER: Loaded 0 events 070107 1:45:05 [Note] SCHEDULER: Suspending operations 070107 1:47:26 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_token_data' is marked as crashed and should be repaired 070107 1:47:26 [Warning] Checking table: '%˜ÿ' 070107 1:48:49 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_signature_data' is marked as crashed and should be repaired 070107 1:48:49 [Warning] Checking table: '-¿ ' 070107 1:48:50 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 070107 1:49:49 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_stats' is marked as crashed and should be repaired 070107 1:49:49 [Warning] Checking table: '.IR' 070107 1:56:13 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_virtual_uids' is marked as crashed and should be repaired 070107 1:56:13 [Warning] Checking table: '/–á' 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. 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=262144000 read_buffer_size=2093056 max_used_connections=105 max_connections=350 threads_connected=104 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329797 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 070107 08:45:23 mysqld restarted /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070107 8:45:56 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 8:45:56 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 070107 8:45:56 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 8:45:56 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 070107 8:45:56 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 8:45:56 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000259' position: 102 070107 8:45:56 [Note] SCHEDULER: Manager thread booting 070107 8:45:56 [Note] SCHEDULER: Loaded 0 events 070107 8:45:56 [Note] SCHEDULER: Suspending operations 070107 8:49:41 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 070107 9:17:34 [Note] /opt/mysql/bin/mysqld: Normal shutdown 070107 9:17:34 [Note] SCHEDULER: Killing manager thread 3 070107 9:17:34 [Note] SCHEDULER: Waiting the manager thread to reply 070107 9:17:34 [Note] SCHEDULER: Resuming operations 070107 9:17:34 [Note] SCHEDULER: Manager thread started with id 3 070107 9:17:34 [Note] SCHEDULER: Shutting down 070107 9:17:34 [Note] SCHEDULER: Waiting for worker threads to finish 070107 9:17:34 [Note] SCHEDULER: Emptying the queue 070107 9:17:34 [Note] SCHEDULER: Stopped 070107 9:18:09 [Note] Slave I/O thread killed while connecting to master 070107 9:18:09 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000013', position 245294931 070107 9:18:09 [Note] Error reading relay log event: slave SQL thread was killed 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. 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=262144000 read_buffer_size=2093056 max_used_connections=6 max_connections=350 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329797 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 070107 09:18:09 mysqld restarted /opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070107 9:18:41 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 9:18:41 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 070107 9:18:41 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 9:18:41 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 070107 9:18:41 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 9:18:41 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000260' position: 102 070107 9:18:41 [Note] SCHEDULER: Manager thread booting 070107 9:18:41 [Note] SCHEDULER: Loaded 0 events 070107 9:18:41 [Note] SCHEDULER: Suspending operations 070107 9:21:17 [Note] /opt/mysql/bin/mysqld: Normal shutdown 070107 9:21:17 [Note] SCHEDULER: Killing manager thread 3 070107 9:21:17 [Note] SCHEDULER: Waiting the manager thread to reply 070107 9:21:17 [Note] SCHEDULER: Resuming operations 070107 9:21:17 [Note] SCHEDULER: Manager thread started with id 3 070107 9:21:17 [Note] SCHEDULER: Shutting down 070107 9:21:17 [Note] SCHEDULER: Waiting for worker threads to finish 070107 9:21:17 [Note] SCHEDULER: Emptying the queue 070107 9:21:17 [Note] SCHEDULER: Stopped 070107 9:22:26 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 070107 9:22:26 [Note] Slave I/O thread killed while connecting to master 070107 9:22:26 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000013', position 245294931 070107 9:22:26 [Note] Error reading relay log event: slave SQL thread was killed 070107 9:22:26 [Note] /opt/mysql/bin/mysqld: Shutdown complete 070107 09:22:26 mysqld ended 070107 09:34:18 mysqld started 070107 9:34:29 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 9:34:29 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 070107 9:34:29 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 9:34:29 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=iss-relay-bin' to avoid this problem. 070107 9:34:29 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 9:34:29 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000013' at position 245294931, relay log './iss-relay-bin.000261' position: 102 070107 9:34:29 [Note] SCHEDULER: Manager thread booting 070107 9:34:29 [Note] SCHEDULER: Loaded 0 events 070107 9:34:29 [Note] SCHEDULER: Suspending operations 070107 9:37:59 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_signature_data' is marked as crashed and should be repaired 070107 9:37:59 [Warning] Checking table: 'N±S' 070107 9:38:14 [ERROR] Slave I/O thread: error connecting to master 'repl@10.1.58.26:3306': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 070107 9:38:14 [Note] Slave I/O thread killed while connecting to master 070107 9:38:14 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000013', position 245294931 070107 9:38:14 [Note] Error reading relay log event: slave SQL thread was killed 070107 9:39:08 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_virtual_uids' is marked as crashed and should be repaired 070107 9:39:08 [Warning] Checking table: '/Ñ' 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. 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=262144000 read_buffer_size=2093056 max_used_connections=106 max_connections=350 threads_connected=19 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329797 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 070107 21:37:51 mysqld restarted /opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070107 21:38:26 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 21:38:26 [Warning] 'user' entry '(null)@node2-iss' ignored in --skip-name-resolve mode. 070107 21:38:26 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 21:38:26 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.11-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 21:38:26 [Note] SCHEDULER: Manager thread booting 070107 21:38:26 [Note] SCHEDULER: Loaded 0 events 070107 21:38:26 [Note] SCHEDULER: Suspending operations 070107 21:57:47 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_token_data' is marked as crashed and should be repaired 070107 21:57:47 [Warning] Checking table: '+O' 070107 21:58:52 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_signature_data' is marked as crashed and should be repaired 070107 21:58:52 [Warning] Checking table: '[±ƒ' 070107 21:59:16 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_virtual_uids' is marked as crashed and should be repaired 070107 21:59:16 [Warning] Checking table: 'ŽQ' 070107 22:00:03 [ERROR] /opt/mysql/bin/mysqld: Table './dspam/dspam_stats' is marked as crashed and should be repaired 070107 22:00:03 [Warning] Checking table: '¨Ù' 070107 23:50:04 [Note] /opt/mysql/bin/mysqld: Normal shutdown 070107 23:50:04 [Note] SCHEDULER: Killing manager thread 1 070107 23:50:04 [Note] SCHEDULER: Waiting the manager thread to reply 070107 23:50:04 [Note] SCHEDULER: Resuming operations 070107 23:50:04 [Note] SCHEDULER: Manager thread started with id 1 070107 23:50:04 [Note] SCHEDULER: Shutting down 070107 23:50:04 [Note] SCHEDULER: Waiting for worker threads to finish 070107 23:50:04 [Note] SCHEDULER: Emptying the queue 070107 23:50:04 [Note] SCHEDULER: Stopped 070107 23:50:06 [Note] /opt/mysql/bin/mysqld: Shutdown complete 070107 23:50:07 mysqld ended 070107 23:55:39 mysqld started 070107 23:55:39 [ERROR] /opt/mysql/bin/mysqld: unknown option '--skip-bdb' 070107 23:55:39 mysqld ended 070107 23:56:59 mysqld started 070107 23:57:26 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070107 23:57:26 [Warning] 'user' entry '@node2-iss' ignored in --skip-name-resolve mode. 070107 23:57:26 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070107 23:57:26 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 070107 23:57:26 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.15-beta-nightly-20070103-standard-debug-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070107 23:57:26 [Note] SCHEDULER: Loaded 0 events 070108 0:44:31 [Note] /opt/mysql/bin/mysqld: Normal shutdown 070108 0:44:31 [Note] SCHEDULER: Purging queue. 0 events 070108 0:44:34 [Note] /opt/mysql/bin/mysqld: Shutdown complete 070108 00:44:34 mysqld ended 070108 00:44:37 mysqld started 070108 0:44:53 [Warning] 'user' entry 'root@node2-iss' ignored in --skip-name-resolve mode. 070108 0:44:53 [Warning] 'user' entry '@node2-iss' ignored in --skip-name-resolve mode. 070108 0:44:53 [Warning] 'user' entry 'repl@templar2.atlas.ops.us.digitar.com' ignored in --skip-name-resolve mode. 070108 0:44:53 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 070108 0:44:53 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: '5.1.15-beta-nightly-20070103-standard-debug-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 070108 0:44:53 [Note] SCHEDULER: Loaded 0 events Assertion failed: fixed == 1, file item.h, line 1601 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. 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=262144000 read_buffer_size=2093056 max_used_connections=105 max_connections=350 threads_connected=103 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1329787 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 070108 02:22:55 mysqld restarted /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070108 02:31:08 mysqld started /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070108 02:33:02 mysqld ended 070108 02:33:21 mysqld started /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070108 02:35:21 mysqld started /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired 070108 02:57:56 mysqld started /opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired