051211 23:49:30 mysqld restarted 051211 23:49:30 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051211 23:49:30 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... 051211 23:49:30 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 3439873964. InnoDB: Doing recovery: scanned up to log sequence number 0 3439874353 051211 23:49:30 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051211 23:49:30 InnoDB: Flushing modified pages from the buffer pool... 051211 23:49:31 InnoDB: Started; log sequence number 0 3439874353 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=174 max_connections=500 threads_connected=124 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 00:07:56 mysqld restarted 051212 0:07:56 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 0:07:56 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... 051212 0:07:56 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 3440447908. InnoDB: Doing recovery: scanned up to log sequence number 0 3440454097 051212 0:07:56 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 0:07:56 InnoDB: Flushing modified pages from the buffer pool... 051212 0:07:56 InnoDB: Started; log sequence number 0 3440454097 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=127 max_connections=500 threads_connected=80 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 02:21:51 mysqld restarted 051212 2:21:51 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 2:21:51 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... 051212 2:21:51 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 3442410874. InnoDB: Doing recovery: scanned up to log sequence number 0 3442410962 051212 2:21:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 2:21:51 InnoDB: Flushing modified pages from the buffer pool... 051212 2:21:52 InnoDB: Started; log sequence number 0 3442410962 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=170 max_connections=500 threads_connected=124 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 11:58:50 mysqld restarted 051212 11:58:50 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 11:58: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... 051212 11:58:50 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4118249500. InnoDB: Doing recovery: scanned up to log sequence number 0 4118251049 051212 11:58:50 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 11:58:50 InnoDB: Flushing modified pages from the buffer pool... 051212 11:58:50 InnoDB: Started; log sequence number 0 4118251049 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=177 max_connections=500 threads_connected=130 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 13:39:54 mysqld restarted 051212 13:39:54 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 13:39:54 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... 051212 13:39:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4121039643. InnoDB: Doing recovery: scanned up to log sequence number 0 4121039643 051212 13:39:55 InnoDB: Flushing modified pages from the buffer pool... 051212 13:39:55 InnoDB: Started; log sequence number 0 4121039643 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=160 max_connections=500 threads_connected=113 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 14:32:11 mysqld restarted 051212 14:32:11 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 14:32:11 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... 051212 14:32:11 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4123731607. InnoDB: Doing recovery: scanned up to log sequence number 0 4123732251 051212 14:32:11 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 14:32:11 InnoDB: Flushing modified pages from the buffer pool... 051212 14:32:11 InnoDB: Started; log sequence number 0 4123732251 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=248 max_connections=500 threads_connected=199 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 17:40:08 mysqld restarted 051212 17:40:08 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 17:40:08 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... 051212 17:40:08 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4130473234. InnoDB: Doing recovery: scanned up to log sequence number 0 4130473563 051212 17:40:08 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 17:40:08 InnoDB: Flushing modified pages from the buffer pool... 051212 17:40:08 InnoDB: Started; log sequence number 0 4130473563 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=211 max_connections=500 threads_connected=165 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 18:28:36 mysqld restarted 051212 18:28:36 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 18:28:36 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... 051212 18:28:36 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4131794729. InnoDB: Doing recovery: scanned up to log sequence number 0 4131795476 051212 18:28:36 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 18:28:37 InnoDB: Flushing modified pages from the buffer pool... 051212 18:28:37 InnoDB: Started; log sequence number 0 4131795476 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=165 max_connections=500 threads_connected=118 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 18:53:37 mysqld restarted 051212 18:53:37 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 18:53:37 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... 051212 18:53:37 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4132336317. InnoDB: Doing recovery: scanned up to log sequence number 0 4132337054 051212 18:53:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 18:53:37 InnoDB: Flushing modified pages from the buffer pool... 051212 18:53:37 InnoDB: Started; log sequence number 0 4132337054 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=208 max_connections=500 threads_connected=160 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 19:12:52 mysqld restarted 051212 19:12:52 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 19:12:53 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... 051212 19:12:53 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4132900982. InnoDB: Doing recovery: scanned up to log sequence number 0 4132901526 051212 19:12:53 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 051212 19:12:53 InnoDB: Flushing modified pages from the buffer pool... 051212 19:12:53 InnoDB: Started; log sequence number 0 4132901526 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=190 max_connections=500 threads_connected=143 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 19:51:57 mysqld restarted 051212 19:51:57 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 19:51:57 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... 051212 19:51:57 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4134908251. InnoDB: Doing recovery: scanned up to log sequence number 0 4134908755 051212 19:51:57 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 19:51:57 InnoDB: Flushing modified pages from the buffer pool... 051212 19:51:57 InnoDB: Started; log sequence number 0 4134908755 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=301 max_connections=500 threads_connected=249 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 19:58:37 mysqld restarted 051212 19:58:37 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 19:58:37 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... 051212 19:58:37 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4134990780. InnoDB: Doing recovery: scanned up to log sequence number 0 4134991380 051212 19:58:37 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 051212 19:58:37 InnoDB: Flushing modified pages from the buffer pool... 051212 19:58:37 InnoDB: Started; log sequence number 0 4134991380 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=212 max_connections=500 threads_connected=158 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 20:09:13 mysqld restarted 051212 20:09:13 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 20:09:14 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... 051212 20:09:14 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4135572265. InnoDB: Doing recovery: scanned up to log sequence number 0 4135573468 051212 20:09:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 20:09:14 InnoDB: Flushing modified pages from the buffer pool... 051212 20:09:14 InnoDB: Started; log sequence number 0 4135573468 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=317 max_connections=500 threads_connected=266 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 21:25:50 mysqld restarted 051212 21:25:50 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 21:25:51 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... 051212 21:25:51 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4136131627. InnoDB: Doing recovery: scanned up to log sequence number 0 4136133015 051212 21:25:51 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 051212 21:25:51 InnoDB: Flushing modified pages from the buffer pool... 051212 21:25:51 InnoDB: Started; log sequence number 0 4136133015 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=236 max_connections=500 threads_connected=190 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 21:42:08 mysqld restarted 051212 21:42:08 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 21:42:08 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... 051212 21:42:08 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4136545060. InnoDB: Doing recovery: scanned up to log sequence number 0 4136545313 051212 21:42:09 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 051212 21:42:09 InnoDB: Flushing modified pages from the buffer pool... 051212 21:42:09 InnoDB: Started; log sequence number 0 4136545313 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=226 max_connections=500 threads_connected=178 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 22:01:30 mysqld restarted 051212 22:01:30 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 22:01:30 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... 051212 22:01:30 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4137903923. InnoDB: Doing recovery: scanned up to log sequence number 0 4137905702 051212 22:01:30 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 22:01:30 InnoDB: Flushing modified pages from the buffer pool... 051212 22:01:30 InnoDB: Started; log sequence number 0 4137905702 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=209 max_connections=500 threads_connected=160 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 22:13:56 mysqld restarted 051212 22:13:56 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 22:13:57 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... 051212 22:13:57 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4138455652. InnoDB: Doing recovery: scanned up to log sequence number 0 4138456571 051212 22:13:57 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 22:13:57 InnoDB: Flushing modified pages from the buffer pool... 051212 22:13:57 InnoDB: Started; log sequence number 0 4138456571 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=214 max_connections=500 threads_connected=167 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 22:39:37 mysqld restarted 051212 22:39:37 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 22:39:38 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... 051212 22:39:38 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4139575406. InnoDB: Doing recovery: scanned up to log sequence number 0 4139576413 051212 22:39:38 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 22:39:38 InnoDB: Flushing modified pages from the buffer pool... 051212 22:39:38 InnoDB: Started; log sequence number 0 4139576413 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=179 max_connections=500 threads_connected=131 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 23:09:04 mysqld restarted 051212 23:09:04 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 23:09:04 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... 051212 23:09:04 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4141393629. InnoDB: Doing recovery: scanned up to log sequence number 0 4141394077 051212 23:09:04 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 23:09:04 InnoDB: Flushing modified pages from the buffer pool... 051212 23:09:04 InnoDB: Started; log sequence number 0 4141394077 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=191 max_connections=500 threads_connected=144 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 23:31:12 mysqld restarted 051212 23:31:12 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 23:31:12 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... 051212 23:31:12 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4142703119. InnoDB: Doing recovery: scanned up to log sequence number 0 4142703958 051212 23:31:13 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 23:31:13 InnoDB: Flushing modified pages from the buffer pool... 051212 23:31:13 InnoDB: Started; log sequence number 0 4142703958 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=153 max_connections=500 threads_connected=106 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3881468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051212 23:51:34 mysqld restarted 051212 23:51:34 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051212 23:51:34 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... 051212 23:51:34 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4143542336. InnoDB: Doing recovery: scanned up to log sequence number 0 4143543181 051212 23:51:34 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051212 23:51:34 InnoDB: Flushing modified pages from the buffer pool... 051212 23:51:34 InnoDB: Started; log sequence number 0 4143543181 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 051213 0:11:22 [Note] /usr/local/libexec/mysqld: Normal shutdown 051213 0:11:24 InnoDB: Starting shutdown... 051213 0:11:27 InnoDB: Shutdown completed; log sequence number 0 4144818356 051213 0:11:27 [Note] /usr/local/libexec/mysqld: Shutdown complete 051213 00:11:27 mysqld ended 051213 00:11:27 mysqld started 051213 0:11:27 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 0:11:28 InnoDB: Started; log sequence number 0 4144818356 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=130 max_connections=400 threads_connected=84 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 01:06:43 mysqld restarted 051213 1:06:43 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 1:06:43 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... 051213 1:06:43 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4147204986. InnoDB: Doing recovery: scanned up to log sequence number 0 4147205014 051213 1:06:43 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 1:06:44 InnoDB: Flushing modified pages from the buffer pool... 051213 1:06:44 InnoDB: Started; log sequence number 0 4147205014 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=119 max_connections=400 threads_connected=73 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 02:04:07 mysqld restarted 051213 2:04:07 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 2:04:07 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... 051213 2:04:07 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4148879287. InnoDB: Doing recovery: scanned up to log sequence number 0 4148879392 051213 2:04:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 2:04:07 InnoDB: Flushing modified pages from the buffer pool... 051213 2:04:07 InnoDB: Started; log sequence number 0 4148879392 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=112 max_connections=400 threads_connected=64 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 07:03:10 mysqld restarted 051213 7:03:10 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 7:03:10 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... 051213 7:03:10 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 534203655. InnoDB: Doing recovery: scanned up to log sequence number 1 534203655 051213 7:03:10 InnoDB: Flushing modified pages from the buffer pool... 051213 7:03:11 InnoDB: Started; log sequence number 1 534203655 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=126 max_connections=400 threads_connected=80 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 08:57:57 mysqld restarted 051213 8:57:57 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 8:57:57 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... 051213 8:57:57 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 536910928. InnoDB: Doing recovery: scanned up to log sequence number 1 536911238 051213 8:57:57 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 8:57:57 InnoDB: Flushing modified pages from the buffer pool... 051213 8:57:57 InnoDB: Started; log sequence number 1 536911238 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=172 max_connections=400 threads_connected=125 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 10:10:46 mysqld restarted 051213 10:10:46 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 10:10:46 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... 051213 10:10:46 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 539047927. InnoDB: Doing recovery: scanned up to log sequence number 1 539048988 051213 10:10:46 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 051213 10:10:46 InnoDB: Flushing modified pages from the buffer pool... 051213 10:10:46 InnoDB: Started; log sequence number 1 539048988 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=227 max_connections=400 threads_connected=181 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 11:10:19 mysqld restarted 051213 11:10:19 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 11:10: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... 051213 11:10:19 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 542759544. InnoDB: Doing recovery: scanned up to log sequence number 1 542765611 051213 11:10:19 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 11:10:20 InnoDB: Flushing modified pages from the buffer pool... 051213 11:10:20 InnoDB: Started; log sequence number 1 542765611 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=259 max_connections=400 threads_connected=208 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 12:09:41 mysqld restarted 051213 12:09:41 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 12:09:41 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... 051213 12:09:41 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 544826985. InnoDB: Doing recovery: scanned up to log sequence number 1 544827545 051213 12:09:41 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 12:09:42 InnoDB: Flushing modified pages from the buffer pool... 051213 12:09:42 InnoDB: Started; log sequence number 1 544827545 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=170 max_connections=400 threads_connected=121 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 591868 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 12:30:12 mysqld restarted 051213 12:30:12 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 12:30:12 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... 051213 12:30:12 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 564479418. InnoDB: Doing recovery: scanned up to log sequence number 1 564496794 051213 12:30:12 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 051213 12:30:12 InnoDB: Flushing modified pages from the buffer pool... 051213 12:30:12 InnoDB: Started; log sequence number 1 564496794 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 051213 13:09:57 [Note] /usr/local/libexec/mysqld: Normal shutdown 051213 13:10:00 InnoDB: Starting shutdown... 051213 13:10:03 InnoDB: Shutdown completed; log sequence number 1 566456222 051213 13:10:03 [Note] /usr/local/libexec/mysqld: Shutdown complete 051213 13:10:03 mysqld ended 051213 13:10:04 mysqld started 051213 13:10:04 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 13:10:04 InnoDB: Started; log sequence number 1 566456222 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=184 max_connections=400 threads_connected=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 13:40:00 mysqld restarted 051213 13:40:00 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 13:40:00 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... 051213 13:40:00 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 567610648. InnoDB: Doing recovery: scanned up to log sequence number 1 567611295 051213 13:40:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 13:40:00 InnoDB: Flushing modified pages from the buffer pool... 051213 13:40:00 InnoDB: Started; log sequence number 1 567611295 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=164 max_connections=400 threads_connected=116 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 14:00:41 mysqld restarted 051213 14:00:41 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 14:00:41 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... 051213 14:00:41 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 568205763. InnoDB: Doing recovery: scanned up to log sequence number 1 568208343 051213 14:00:42 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 051213 14:00:42 InnoDB: Flushing modified pages from the buffer pool... 051213 14:00:42 InnoDB: Started; log sequence number 1 568208343 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=175 max_connections=400 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 14:54:51 mysqld restarted 051213 14:54:51 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 14:54:51 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... 051213 14:54:51 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 570474764. InnoDB: Doing recovery: scanned up to log sequence number 1 570474764 051213 14:54:51 InnoDB: Flushing modified pages from the buffer pool... 051213 14:54:51 InnoDB: Started; log sequence number 1 570474764 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=183 max_connections=400 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 15:01:52 mysqld restarted 051213 15:01:52 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 15:01:52 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... 051213 15:01:52 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 570737900. InnoDB: Doing recovery: scanned up to log sequence number 1 570738675 051213 15:01:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 15:01:52 InnoDB: Flushing modified pages from the buffer pool... 051213 15:01:52 InnoDB: Started; log sequence number 1 570738675 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=75 max_connections=400 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 15:02:27 mysqld restarted 051213 15:02:27 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 15:02:27 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... 051213 15:02:27 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 570741311. InnoDB: Doing recovery: scanned up to log sequence number 1 570741613 051213 15:02:27 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 15:02:27 InnoDB: Flushing modified pages from the buffer pool... 051213 15:02:27 InnoDB: Started; log sequence number 1 570741613 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=159 max_connections=400 threads_connected=111 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 15:35:54 mysqld restarted 051213 15:35:54 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 15:35:55 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... 051213 15:35:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 572432319. InnoDB: Doing recovery: scanned up to log sequence number 1 572432781 051213 15:35:55 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 15:35:55 InnoDB: Flushing modified pages from the buffer pool... 051213 15:35:55 InnoDB: Started; log sequence number 1 572432781 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=157 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 15:53:50 mysqld restarted 051213 15:53:50 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 15:53: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... 051213 15:53:50 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 573322572. InnoDB: Doing recovery: scanned up to log sequence number 1 573324368 051213 15:53:50 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 15:53:50 InnoDB: Flushing modified pages from the buffer pool... 051213 15:53:50 InnoDB: Started; log sequence number 1 573324368 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=177 max_connections=400 threads_connected=130 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 16:16:43 mysqld restarted 051213 16:16:43 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 16:16:43 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... 051213 16:16:43 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 574123902. InnoDB: Doing recovery: scanned up to log sequence number 1 574123902 051213 16:16:43 InnoDB: Flushing modified pages from the buffer pool... 051213 16:16:43 InnoDB: Started; log sequence number 1 574123902 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=117 max_connections=400 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 16:20:51 mysqld restarted 051213 16:20:51 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 16:20:51 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... 051213 16:20:51 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 574378508. InnoDB: Doing recovery: scanned up to log sequence number 1 574379186 051213 16:20:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 16:20:51 InnoDB: Flushing modified pages from the buffer pool... 051213 16:20:51 InnoDB: Started; log sequence number 1 574379186 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 051213 16:48:16 [Note] /usr/local/libexec/mysqld: Normal shutdown 051213 16:48:18 InnoDB: Starting shutdown... 051213 16:48:22 InnoDB: Shutdown completed; log sequence number 1 575866904 051213 16:48:22 [Note] /usr/local/libexec/mysqld: Shutdown complete 051213 16:48:22 mysqld ended 051213 16:48:22 mysqld started 051213 16:48:22 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 16:48:22 InnoDB: Started; log sequence number 1 575866904 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 051213 17:02:09 [Note] /usr/local/libexec/mysqld: Normal shutdown 051213 17:02:09 [ERROR] /usr/local/libexec/mysqld: Sort aborted 051213 17:02:11 InnoDB: Starting shutdown... 051213 17:02:14 InnoDB: Shutdown completed; log sequence number 1 576477164 051213 17:02:14 [Note] /usr/local/libexec/mysqld: Shutdown complete 051213 17:02:14 mysqld ended 051213 17:02:14 mysqld started 051213 17:02:14 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 17:02:15 InnoDB: Started; log sequence number 1 576477164 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=181 max_connections=400 threads_connected=131 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 17:10:18 mysqld restarted 051213 17:10:18 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 17:10:18 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... 051213 17:10:18 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 576838937. InnoDB: Doing recovery: scanned up to log sequence number 1 576839862 051213 17:10:18 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 17:10:18 InnoDB: Flushing modified pages from the buffer pool... 051213 17:10:18 InnoDB: Started; log sequence number 1 576839862 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=56 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 18:34:42 mysqld restarted 051213 18:34:42 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 18:34:43 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... 051213 18:34:43 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 579741627. InnoDB: Doing recovery: scanned up to log sequence number 1 579743258 051213 18:34:43 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 051213 18:34:43 InnoDB: Flushing modified pages from the buffer pool... 051213 18:34:43 InnoDB: Started; log sequence number 1 579743258 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=52 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 18:42:40 mysqld restarted 051213 18:42:40 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 18:42:40 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... 051213 18:42:40 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 579913105. InnoDB: Doing recovery: scanned up to log sequence number 1 579913930 051213 18:42:40 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 18:42:40 InnoDB: Flushing modified pages from the buffer pool... 051213 18:42:40 InnoDB: Started; log sequence number 1 579913930 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=59 max_connections=400 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 19:01:25 mysqld restarted 051213 19:01:25 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 19:01:25 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... 051213 19:01:25 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 580450753. InnoDB: Doing recovery: scanned up to log sequence number 1 580457655 051213 19:01:25 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 19:01:25 InnoDB: Flushing modified pages from the buffer pool... 051213 19:01:25 InnoDB: Started; log sequence number 1 580457655 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=71 max_connections=400 threads_connected=25 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 19:09:11 mysqld restarted 051213 19:09:11 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 19:09:11 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... 051213 19:09:11 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 581491752. InnoDB: Doing recovery: scanned up to log sequence number 1 581492707 051213 19:09:11 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 051213 19:09:11 InnoDB: Flushing modified pages from the buffer pool... 051213 19:09:11 InnoDB: Started; log sequence number 1 581492707 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=58 max_connections=400 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 19:14:52 mysqld restarted 051213 19:14:52 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 19:14:52 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... 051213 19:14:52 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 582002505. InnoDB: Doing recovery: scanned up to log sequence number 1 582012362 051213 19:14:52 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 051213 19:14:52 InnoDB: Flushing modified pages from the buffer pool... 051213 19:14:52 InnoDB: Started; log sequence number 1 582012362 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=53 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 19:30:11 mysqld restarted 051213 19:30:11 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 19:30:11 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... 051213 19:30:11 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 582446175. InnoDB: Doing recovery: scanned up to log sequence number 1 582449498 051213 19:30:11 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 051213 19:30:11 InnoDB: Flushing modified pages from the buffer pool... 051213 19:30:11 InnoDB: Started; log sequence number 1 582449498 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=50 max_connections=400 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 19:45:00 mysqld restarted 051213 19:45:00 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 19:45:00 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... 051213 19:45:00 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 583579000. InnoDB: Doing recovery: scanned up to log sequence number 1 583579125 051213 19:45:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 051213 19:45:00 InnoDB: Flushing modified pages from the buffer pool... 051213 19:45:00 InnoDB: Started; log sequence number 1 583579125 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=71 max_connections=400 threads_connected=23 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:34:07 mysqld restarted 051213 20:34:07 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:34:07 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... 051213 20:34:07 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 585992747. InnoDB: Doing recovery: scanned up to log sequence number 1 586011167 051213 20:34:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 20:34:07 InnoDB: Flushing modified pages from the buffer pool... 051213 20:34:07 InnoDB: Started; log sequence number 1 586011167 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=135 max_connections=400 threads_connected=87 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:36:45 mysqld restarted 051213 20:36:45 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:36:45 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... 051213 20:36:45 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 586049235. InnoDB: Doing recovery: scanned up to log sequence number 1 586049643 051213 20:36:45 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 20:36:45 InnoDB: Flushing modified pages from the buffer pool... 051213 20:36:45 InnoDB: Started; log sequence number 1 586049643 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=185 max_connections=400 threads_connected=133 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:43:23 mysqld restarted 051213 20:43:23 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:43:24 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... 051213 20:43:24 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 586204865. InnoDB: Doing recovery: scanned up to log sequence number 1 586206198 051213 20:43:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 20:43:24 InnoDB: Flushing modified pages from the buffer pool... 051213 20:43:24 InnoDB: Started; log sequence number 1 586206198 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=51 max_connections=400 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:44:26 mysqld restarted 051213 20:44:26 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:44:26 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... 051213 20:44:26 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 586253033. InnoDB: Doing recovery: scanned up to log sequence number 1 586253874 051213 20:44:27 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 051213 20:44:27 InnoDB: Flushing modified pages from the buffer pool... 051213 20:44:27 InnoDB: Started; log sequence number 1 586253874 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=57 max_connections=400 threads_connected=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:52:42 mysqld restarted 051213 20:52:42 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:52:42 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... 051213 20:52:42 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 587155152. InnoDB: Doing recovery: scanned up to log sequence number 1 587155862 051213 20:52:43 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 20:52:43 InnoDB: Flushing modified pages from the buffer pool... 051213 20:52:43 InnoDB: Started; log sequence number 1 587155862 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=53 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 20:58:15 mysqld restarted 051213 20:58:15 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 20:58:15 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... 051213 20:58:15 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 587401064. InnoDB: Doing recovery: scanned up to log sequence number 1 587413536 051213 20:58:15 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 20:58:15 InnoDB: Flushing modified pages from the buffer pool... 051213 20:58:15 InnoDB: Started; log sequence number 1 587413536 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=67 max_connections=400 threads_connected=19 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:06:59 mysqld restarted 051213 21:06:59 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:06:59 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... 051213 21:06:59 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 587969787. InnoDB: Doing recovery: scanned up to log sequence number 1 587971727 051213 21:06:59 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:06:59 InnoDB: Flushing modified pages from the buffer pool... 051213 21:06:59 InnoDB: Started; log sequence number 1 587971727 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=56 max_connections=400 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:17:48 mysqld restarted 051213 21:17:48 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:17:48 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... 051213 21:17:48 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588389031. InnoDB: Doing recovery: scanned up to log sequence number 1 588389909 051213 21:17:48 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:17:48 InnoDB: Flushing modified pages from the buffer pool... 051213 21:17:48 InnoDB: Started; log sequence number 1 588389909 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=54 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:18:32 mysqld restarted 051213 21:18:32 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:18:32 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... 051213 21:18:32 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588432510. InnoDB: Doing recovery: scanned up to log sequence number 1 588433035 051213 21:18:32 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:18:32 InnoDB: Flushing modified pages from the buffer pool... 051213 21:18:32 InnoDB: Started; log sequence number 1 588433035 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=66 max_connections=400 threads_connected=14 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:22:42 mysqld restarted 051213 21:22:42 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:22:42 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... 051213 21:22:42 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588571599. InnoDB: Doing recovery: scanned up to log sequence number 1 588575529 051213 21:22:42 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:22:42 InnoDB: Flushing modified pages from the buffer pool... 051213 21:22:42 InnoDB: Started; log sequence number 1 588575529 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=62 max_connections=400 threads_connected=14 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:24:01 mysqld restarted 051213 21:24:01 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:24:01 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... 051213 21:24:01 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588622687. InnoDB: Doing recovery: scanned up to log sequence number 1 588623504 051213 21:24:01 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:24:01 InnoDB: Flushing modified pages from the buffer pool... 051213 21:24:01 InnoDB: Started; log sequence number 1 588623504 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=64 max_connections=400 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:27:48 mysqld restarted 051213 21:27:48 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:27:48 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... 051213 21:27:48 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588699348. InnoDB: Doing recovery: scanned up to log sequence number 1 588700688 051213 21:27:48 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:27:48 InnoDB: Flushing modified pages from the buffer pool... 051213 21:27:48 InnoDB: Started; log sequence number 1 588700688 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=57 max_connections=400 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:28:43 mysqld restarted 051213 21:28:43 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:28:43 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... 051213 21:28:44 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588719298. InnoDB: Doing recovery: scanned up to log sequence number 1 588722068 051213 21:28:44 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 051213 21:28:44 InnoDB: Flushing modified pages from the buffer pool... 051213 21:28:44 InnoDB: Started; log sequence number 1 588722068 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=53 max_connections=400 threads_connected=3 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:31:29 mysqld restarted 051213 21:31:29 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:31:29 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... 051213 21:31:29 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 588790614. InnoDB: Doing recovery: scanned up to log sequence number 1 588790614 051213 21:31:29 InnoDB: Flushing modified pages from the buffer pool... 051213 21:31:29 InnoDB: Started; log sequence number 1 588790614 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=57 max_connections=400 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:46:56 mysqld restarted 051213 21:46:56 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:46:56 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... 051213 21:46:56 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 589488035. InnoDB: Doing recovery: scanned up to log sequence number 1 589503515 051213 21:46:56 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 051213 21:46:56 InnoDB: Flushing modified pages from the buffer pool... 051213 21:46:56 InnoDB: Started; log sequence number 1 589503515 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=57 max_connections=400 threads_connected=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:50:31 mysqld restarted 051213 21:50:31 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:50: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... 051213 21:50:31 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 589588731. InnoDB: Doing recovery: scanned up to log sequence number 1 589591024 051213 21:50:31 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 051213 21:50:31 InnoDB: Flushing modified pages from the buffer pool... 051213 21:50:31 InnoDB: Started; log sequence number 1 589591024 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=55 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 21:58:33 mysqld restarted 051213 21:58:33 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 21:58:34 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... 051213 21:58:34 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 589841032. InnoDB: Doing recovery: scanned up to log sequence number 1 589842508 051213 21:58:34 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 21:58:34 InnoDB: Flushing modified pages from the buffer pool... 051213 21:58:34 InnoDB: Started; log sequence number 1 589842508 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=76 max_connections=400 threads_connected=28 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:05:48 mysqld restarted 051213 22:05:48 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:05:48 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... 051213 22:05:48 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590347038. InnoDB: Doing recovery: scanned up to log sequence number 1 590351560 051213 22:05:48 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 051213 22:05:48 InnoDB: Flushing modified pages from the buffer pool... 051213 22:05:48 InnoDB: Started; log sequence number 1 590351560 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=49 max_connections=400 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:08:16 mysqld restarted 051213 22:08:16 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:08:16 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... 051213 22:08:16 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590373614. InnoDB: Doing recovery: scanned up to log sequence number 1 590377904 051213 22:08:16 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:08:16 InnoDB: Flushing modified pages from the buffer pool... 051213 22:08:16 InnoDB: Started; log sequence number 1 590377904 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=56 max_connections=400 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:14:03 mysqld restarted 051213 22:14:03 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:14:03 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... 051213 22:14:03 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590487684. InnoDB: Doing recovery: scanned up to log sequence number 1 590492499 051213 22:14:03 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:14:04 InnoDB: Flushing modified pages from the buffer pool... 051213 22:14:04 InnoDB: Started; log sequence number 1 590492499 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=61 max_connections=400 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:14:59 mysqld restarted 051213 22:14:59 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:14:59 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... 051213 22:14:59 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590520271. InnoDB: Doing recovery: scanned up to log sequence number 1 590520993 051213 22:14:59 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:14:59 InnoDB: Flushing modified pages from the buffer pool... 051213 22:14:59 InnoDB: Started; log sequence number 1 590520993 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=61 max_connections=400 threads_connected=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:17:25 mysqld restarted 051213 22:17:25 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:17:25 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... 051213 22:17:25 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590579023. InnoDB: Doing recovery: scanned up to log sequence number 1 590579023 051213 22:17:25 InnoDB: Flushing modified pages from the buffer pool... 051213 22:17:25 InnoDB: Started; log sequence number 1 590579023 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=64 max_connections=400 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:18:13 mysqld restarted 051213 22:18:13 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:18:14 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... 051213 22:18:14 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590604167. InnoDB: Doing recovery: scanned up to log sequence number 1 590606904 051213 22:18:14 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 051213 22:18:14 InnoDB: Flushing modified pages from the buffer pool... 051213 22:18:14 InnoDB: Started; log sequence number 1 590606904 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=59 max_connections=400 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:18:52 mysqld restarted 051213 22:18:52 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:18:52 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... 051213 22:18:52 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590620574. InnoDB: Doing recovery: scanned up to log sequence number 1 590621058 051213 22:18:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:18:52 InnoDB: Flushing modified pages from the buffer pool... 051213 22:18:52 InnoDB: Started; log sequence number 1 590621058 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=52 max_connections=400 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:19:36 mysqld restarted 051213 22:19:36 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:19:36 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... 051213 22:19:36 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590644689. InnoDB: Doing recovery: scanned up to log sequence number 1 590650603 051213 22:19:36 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:19:36 InnoDB: Flushing modified pages from the buffer pool... 051213 22:19:36 InnoDB: Started; log sequence number 1 590650603 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=69 max_connections=400 threads_connected=20 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:23:40 mysqld restarted 051213 22:23:40 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:23:41 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... 051213 22:23:41 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590772387. InnoDB: Doing recovery: scanned up to log sequence number 1 590774462 051213 22:23:41 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 051213 22:23:41 InnoDB: Flushing modified pages from the buffer pool... 051213 22:23:41 InnoDB: Started; log sequence number 1 590774462 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=18 max_connections=400 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:24:52 mysqld restarted 051213 22:24:52 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:24:52 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... 051213 22:24:52 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590781404. InnoDB: Doing recovery: scanned up to log sequence number 1 590782140 051213 22:24:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:24:52 InnoDB: Flushing modified pages from the buffer pool... 051213 22:24:52 InnoDB: Started; log sequence number 1 590782140 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=58 max_connections=400 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:25:33 mysqld restarted 051213 22:25:33 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:25: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... 051213 22:25:33 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590788366. InnoDB: Doing recovery: scanned up to log sequence number 1 590788666 051213 22:25:33 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:25:33 InnoDB: Flushing modified pages from the buffer pool... 051213 22:25:33 InnoDB: Started; log sequence number 1 590788666 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=86 max_connections=400 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:29:38 mysqld restarted 051213 22:29:38 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:29:38 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... 051213 22:29:38 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590857009. InnoDB: Doing recovery: scanned up to log sequence number 1 590871754 051213 22:29:38 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 22:29:38 InnoDB: Flushing modified pages from the buffer pool... 051213 22:29:38 InnoDB: Started; log sequence number 1 590871754 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=61 max_connections=400 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:30:43 mysqld restarted 051213 22:30:43 [Warning] Changed limits: max_open_files: 20000 max_connections: 400 table_cache: 9795 051213 22:30:43 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... 051213 22:30:43 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 590890435. InnoDB: Doing recovery: scanned up to log sequence number 1 590891737 051213 22:30:43 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 051213 22:30:43 InnoDB: Flushing modified pages from the buffer pool... 051213 22:30:43 InnoDB: Started; log sequence number 1 590891737 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=33554432 read_buffer_size=1044480 max_used_connections=60 max_connections=400 threads_connected=18 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 965052 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 22:53:11 mysqld restarted 051213 22:53:11 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 22:53:11 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... 051213 22:53:11 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 591391520. InnoDB: Doing recovery: scanned up to log sequence number 1 591393349 051213 22:53:11 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 051213 22:53:11 InnoDB: Flushing modified pages from the buffer pool... 051213 22:53:11 InnoDB: Started; log sequence number 1 591393349 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=62 max_connections=500 threads_connected=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 23:02:41 mysqld restarted 051213 23:02:41 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 23:02:42 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... 051213 23:02:42 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 591594776. InnoDB: Doing recovery: scanned up to log sequence number 1 591595827 051213 23:02:42 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 051213 23:02:42 InnoDB: Flushing modified pages from the buffer pool... 051213 23:02:42 InnoDB: Started; log sequence number 1 591595827 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=55 max_connections=500 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 23:04:28 mysqld restarted 051213 23:04:28 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 23:04:28 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... 051213 23:04:28 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 591635294. InnoDB: Doing recovery: scanned up to log sequence number 1 591709378 051213 23:04:28 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 23:04:28 InnoDB: Flushing modified pages from the buffer pool... 051213 23:04:29 InnoDB: Started; log sequence number 1 591709378 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=92 max_connections=500 threads_connected=42 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 23:23:55 mysqld restarted 051213 23:23:55 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 23:23:55 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... 051213 23:23:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 593327738. InnoDB: Doing recovery: scanned up to log sequence number 1 593335512 051213 23:23:55 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 051213 23:23:55 InnoDB: Flushing modified pages from the buffer pool... 051213 23:23:55 InnoDB: Started; log sequence number 1 593335512 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=83 max_connections=500 threads_connected=36 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 23:34:33 mysqld restarted 051213 23:34:34 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 23:34:34 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... 051213 23:34:34 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 594529499. InnoDB: Doing recovery: scanned up to log sequence number 1 594611412 051213 23:34:34 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 23:34:34 InnoDB: Flushing modified pages from the buffer pool... 051213 23:34:34 InnoDB: Started; log sequence number 1 594611412 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=52 max_connections=500 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051213 23:41:49 mysqld restarted 051213 23:41:49 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051213 23:41:49 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... 051213 23:41:49 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 595008414. InnoDB: Doing recovery: scanned up to log sequence number 1 595008790 051213 23:41:49 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051213 23:41:49 InnoDB: Flushing modified pages from the buffer pool... 051213 23:41:49 InnoDB: Started; log sequence number 1 595008790 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=54 max_connections=500 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 00:11:12 mysqld restarted 051214 0:11:12 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 0:11:12 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... 051214 0:11:12 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 596859176. InnoDB: Doing recovery: scanned up to log sequence number 1 596865570 051214 0:11:12 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 0:11:13 InnoDB: Flushing modified pages from the buffer pool... 051214 0:11:13 InnoDB: Started; log sequence number 1 596865570 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=122 max_connections=500 threads_connected=76 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 12:46:23 mysqld restarted 051214 12:46:23 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 12:46:23 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... 051214 12:46:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1285574065. InnoDB: Doing recovery: scanned up to log sequence number 1 1285575825 051214 12:46:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 12:46:24 InnoDB: Flushing modified pages from the buffer pool... 051214 12:46:24 InnoDB: Started; log sequence number 1 1285575825 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=95 max_connections=500 threads_connected=48 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 12:49:39 mysqld restarted 051214 12:49:39 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 12:49:39 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... 051214 12:49:39 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1285623210. InnoDB: Doing recovery: scanned up to log sequence number 1 1285626531 051214 12:49:39 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 051214 12:49:39 InnoDB: Flushing modified pages from the buffer pool... 051214 12:49:39 InnoDB: Started; log sequence number 1 1285626531 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=103 max_connections=500 threads_connected=54 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 13:53:03 mysqld restarted 051214 13:53:03 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 13:53:03 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... 051214 13:53:03 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1287103442. InnoDB: Doing recovery: scanned up to log sequence number 1 1287106770 051214 13:53:03 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 051214 13:53:04 InnoDB: Flushing modified pages from the buffer pool... 051214 13:53:04 InnoDB: Started; log sequence number 1 1287106770 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=83 max_connections=500 threads_connected=29 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 13:54:44 mysqld restarted 051214 13:54:44 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 13:54:44 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... 051214 13:54:44 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1287125605. InnoDB: Doing recovery: scanned up to log sequence number 1 1287125605 051214 13:54:44 InnoDB: Flushing modified pages from the buffer pool... 051214 13:54:44 InnoDB: Started; log sequence number 1 1287125605 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=128 max_connections=500 threads_connected=80 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 14:27:26 mysqld restarted 051214 14:27:26 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 14:27:26 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... 051214 14:27:26 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1293696310. InnoDB: Doing recovery: scanned up to log sequence number 1 1293699294 051214 14:27:26 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 14:27:26 InnoDB: Flushing modified pages from the buffer pool... 051214 14:27:26 InnoDB: Started; log sequence number 1 1293699294 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=101 max_connections=500 threads_connected=52 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 14:54:44 mysqld restarted 051214 14:54:44 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 14:54:44 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... 051214 14:54:44 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1298728151. InnoDB: Doing recovery: scanned up to log sequence number 1 1298728815 051214 14:54:44 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 14:54:44 InnoDB: Flushing modified pages from the buffer pool... 051214 14:54:44 InnoDB: Started; log sequence number 1 1298728815 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=116 max_connections=500 threads_connected=68 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 16:21:32 mysqld restarted 051214 16:21:32 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 16:21:32 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... 051214 16:21:32 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1301290879. InnoDB: Doing recovery: scanned up to log sequence number 1 1301291847 051214 16:21:32 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 16:21:32 InnoDB: Flushing modified pages from the buffer pool... 051214 16:21:32 InnoDB: Started; log sequence number 1 1301291847 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=64 max_connections=500 threads_connected=15 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 16:28:46 mysqld restarted 051214 16:28:46 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 16:28:46 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... 051214 16:28:46 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1301498460. InnoDB: Doing recovery: scanned up to log sequence number 1 1301500130 051214 16:28:46 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 16:28:46 InnoDB: Flushing modified pages from the buffer pool... 051214 16:28:46 InnoDB: Started; log sequence number 1 1301500130 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=129 max_connections=500 threads_connected=80 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 17:04:05 mysqld restarted 051214 17:04:06 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:04:06 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... 051214 17:04:06 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1302921970. InnoDB: Doing recovery: scanned up to log sequence number 1 1302930307 051214 17:04:06 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 17:04:06 InnoDB: Flushing modified pages from the buffer pool... 051214 17:04:06 InnoDB: Started; log sequence number 1 1302930307 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=144 max_connections=500 threads_connected=96 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 17:09:23 mysqld restarted 051214 17:09:23 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:09:23 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... 051214 17:09:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1302983771. InnoDB: Doing recovery: scanned up to log sequence number 1 1302987587 051214 17:09:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 17:09:24 InnoDB: Flushing modified pages from the buffer pool... 051214 17:09:24 InnoDB: Started; log sequence number 1 1302987587 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=67 max_connections=500 threads_connected=17 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 17:09:31 mysqld restarted 051214 17:09:31 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:09: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... 051214 17:09:31 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1302987587. InnoDB: Doing recovery: scanned up to log sequence number 1 1302997379 051214 17:09:31 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 051214 17:09:31 InnoDB: Flushing modified pages from the buffer pool... 051214 17:09:31 InnoDB: Started; log sequence number 1 1302997379 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=62 max_connections=500 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 17:21:37 mysqld restarted 051214 17:21:37 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:21:37 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... 051214 17:21:37 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1303336236. InnoDB: Doing recovery: scanned up to log sequence number 1 1303337978 051214 17:21:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 17:21:37 InnoDB: Flushing modified pages from the buffer pool... 051214 17:21:37 InnoDB: Started; log sequence number 1 1303337978 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld got signal 10; 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=1044480 max_used_connections=64 max_connections=500 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 133164 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 051214 17:29:59 mysqld restarted 051214 17:29:59 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:29:59 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... 051214 17:29:59 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1303517733. InnoDB: Doing recovery: scanned up to log sequence number 1 1303528110 051214 17:29:59 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 17:30:00 InnoDB: Flushing modified pages from the buffer pool... 051214 17:30:00 InnoDB: Started; log sequence number 1 1303528110 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 051214 17:36:13 [Note] /usr/local/libexec/mysqld: Normal shutdown 051214 17:36:15 InnoDB: Starting shutdown... 051214 17:36:18 InnoDB: Shutdown completed; log sequence number 1 1303657577 051214 17:36:18 [Note] /usr/local/libexec/mysqld: Shutdown complete 051214 17:36:18 mysqld ended 051214 17:37:09 mysqld started 051214 17:37:09 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:37:09 InnoDB: Started; log sequence number 1 1303657577 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld in free(): warning: modified (chunk-) pointer 051214 17:58:07 mysqld restarted 051214 17:58:07 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 17:58:07 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... 051214 17:58:07 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1304067742. InnoDB: Doing recovery: scanned up to log sequence number 1 1304069450 051214 17:58:08 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 051214 17:58:08 InnoDB: Flushing modified pages from the buffer pool... 051214 17:58:08 InnoDB: Started; log sequence number 1 1304069450 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld in free(): warning: modified (chunk-) pointer Fata051214 18:16:46 mysqld restarted 051214 18:16:46 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 18:16:46 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... 051214 18:16:46 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1304502140. InnoDB: Doing recovery: scanned up to log sequence number 1 1304507120 051214 18:16:47 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 18:16:47 InnoDB: Flushing modified pages from the buffer pool... 051214 18:16:47 InnoDB: Started; log sequence number 1 1304507120 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld in free(): warning: modified (chunk-) pointer 051214 18:21:53 mysqld restarted 051214 18:21:53 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 18:21:53 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... 051214 18:21:53 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1304700665. InnoDB: Doing recovery: scanned up to log sequence number 1 1304702213 051214 18:21:53 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 18:21:53 InnoDB: Flushing modified pages from the buffer pool... 051214 18:21:53 InnoDB: Started; log sequence number 1 1304702213 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld in free(): warning: modified (chunk-) pointer 051214 18:38:05 mysqld restarted 051214 18:38:05 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 18:38:06 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... 051214 18:38:06 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1305432429. InnoDB: Doing recovery: scanned up to log sequence number 1 1305433075 051214 18:38:06 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 051214 18:38:06 InnoDB: Flushing modified pages from the buffer pool... 051214 18:38:06 InnoDB: Started; log sequence number 1 1305433075 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15 mysqld in free(): warning: modified (chunk-) pointer 051214 18:40:22 mysqld restarted 051214 18:40:22 [Warning] Changed limits: max_open_files: 20000 max_connections: 500 table_cache: 9745 051214 18:40:22 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... 051214 18:40:22 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 1305471391. InnoDB: Doing recovery: scanned up to log sequence number 1 1305471791 051214 18:40:23 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 051214 18:40:23 InnoDB: Flushing modified pages from the buffer pool... 051214 18:40:23 InnoDB: Started; log sequence number 1 1305471791 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.15-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.15