080207 22:45:38 mysqld started 080207 22:45:38 InnoDB: Started; log sequence number 7 2231732721 080207 22:45:38 [Note] /opt/mysql/libexec/mysqld: ready for connections. Version: '5.0.51a-log' socket: '/opt/mysql/data/mysql.sock' port: 3306 Source distribution 080208 5:17:49 - 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=10485760 read_buffer_size=131072 max_used_connections=6 max_connections=40 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 97279 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0xace2d30 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... Cannot determine thread, fp=0x567ef958, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x818c030 0x841cc5b 0x8294d57 0x81a6219 Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x56471210 is invalid pointer thd->thread_id=5093 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 080208 05:17:50 mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 7 2234443747 080208 5:17:50 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 7 2234443987 080208 5:17:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 080208 5:17:52 InnoDB: Started; log sequence number 7 2234443987 080208 5:17:52 [Note] /opt/mysql/libexec/mysqld: ready for connections. Version: '5.0.51a-log' socket: '/opt/mysql/data/mysql.sock' port: 3306 Source distribution 080208 5:35:33 - 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=10485760 read_buffer_size=131072 max_used_connections=5 max_connections=40 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 97279 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0xb1819c0 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... Cannot determine thread, fp=0x567cb958, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x818c030 0x841cc5b 0x8294d57 0x81a6219 0x81ac5fc 0x81acbeb 0x81ae297 0x81aedda 0x5c850b 0x4b8b2e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0xb1f5d68 = SELECT * FROM vsm_cross WHERE f_num1 = '96129530' UNION SELECT * FROM vsm_cross WHERE f_num2 = '96129530' UNION SELECT * FROM vsm_cross WHERE f_num1 = '47005' AND f_maker1='SUPLEX' UNION SELECT * FROM vsm_cross WHERE f_num2 = '47005' AND f_maker2='SUPLEX' UNION SELECT * FROM vsm_cross WHERE f_num1 = 'RH1655' AND f_maker1='KAYABA-Flex' UNION SELECT * FROM vsm_cross WHERE f_num2 = 'RH1655' AND f_maker2='KAYABA-Flex' UNION SELECT * FROM vsm_cross WHERE f_num1 = '49341' AND f_maker1='SPIDAN' UNION SELECT * FROM vsm_cross WHERE f_num2 = '49341' AND f_maker2='SPIDAN' thd->thread_id=251 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 080208 05:35:33 mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 7 2234784138 080208 5:35:33 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 7 2234784784 080208 5:35:33 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 080208 5:35:34 InnoDB: Started; log sequence number 7 2234784784 080208 5:35:34 [Note] /opt/mysql/libexec/mysqld: ready for connections. Version: '5.0.51a-log' socket: '/opt/mysql/data/mysql.sock' port: 3306 Source distribution 080208 7:59:30 - 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=10485760 read_buffer_size=131072 max_used_connections=4 max_connections=40 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 97279 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0xba66750 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... Cannot determine thread, fp=0x56787658, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x818c030 0x8295591 0x829571d 0x82144e0 0x81a679f 0x81ac5fc 0x81acbeb 0x81ae297 0x81aedda 0x5c850b 0x4b8b2e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x56600478 is invalid pointer thd->thread_id=2716 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. pure virtual method called Number of processes running now: 0 080208 07:59:31 mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 7 2236427482 080208 7:59:31 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 7 2236431946 080208 7:59:32 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 080208 7:59:33 InnoDB: Started; log sequence number 7 2236431946 080208 7:59:33 [Note] /opt/mysql/libexec/mysqld: ready for connections. Version: '5.0.51a-log' socket: '/opt/mysql/data/mysql.sock' port: 3306 Source distribution 080208 10:19:36 [Note] /opt/mysql/libexec/mysqld: Normal shutdown 080208 10:30:33 mysqld started 080208 10:30:34 InnoDB: Started; log sequence number 7 2264742928 080208 10:30:34 [Note] /opt/mysql/libexec/mysqld: ready for connections. Version: '5.0.51a-log' socket: '/opt/mysql/data/mysql.sock' port: 3306 Source distribution