mysqld got signal 10; How to fix? =(

P

PGP

Verified User
Joined
Nov 7, 2006
Messages
31
Location
Russia
MySQL Server restrting all the time. =(
How can i fix it?
Here it is log from /home/mysql/hostname.err

OS - FreeBSD 6.0
MySQL - 5.0.27 standard
Code: 
070125 17:44:29 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=72
max_connections=250
threads_connected=22
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 17:46:36  mysqld restarted
070125 17:46: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...
070125 17:46:38  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 17:46:38  InnoDB: Started; log sequence number 0 6056542
070125 17:46:38 [Note] Recovering after a crash using mysql-bin
070125 17:46:38 [Note] Starting crash recovery...
070125 17:46:38 [Note] Crash recovery finished.
070125 17:46:38 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=70
max_connections=250
threads_connected=22
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 19:23:55  mysqld restarted
070125 19:23: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...
070125 19:23:57  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 19:23:57  InnoDB: Started; log sequence number 0 6056542
070125 19:23:57 [Note] Recovering after a crash using mysql-bin
070125 19:23:58 [Note] Starting crash recovery...
070125 19:23:58 [Note] Crash recovery finished.
070125 19:23:58 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=79
max_connections=250
threads_connected=31
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 19:45:17  mysqld restarted
070125 19:45: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...
070125 19:45:19  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 19:45:19  InnoDB: Started; log sequence number 0 6056542
070125 19:45:19 [Note] Recovering after a crash using mysql-bin
070125 19:45:19 [Note] Starting crash recovery...
070125 19:45:19 [Note] Crash recovery finished.
070125 19:45:19 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=53
max_connections=250
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 20:17:09  mysqld restarted
070125 20:17: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...
070125 20:17:10  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 20:17:10  InnoDB: Started; log sequence number 0 6056542
070125 20:17:10 [Note] Recovering after a crash using mysql-bin
070125 20:17:10 [Note] Starting crash recovery...
070125 20:17:10 [Note] Crash recovery finished.
070125 20:17:10 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=69
max_connections=250
threads_connected=21
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 20:27:41  mysqld restarted
070125 20:27: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...
070125 20:27:42  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 20:27:42  InnoDB: Started; log sequence number 0 6056542
070125 20:27:42 [Note] Recovering after a crash using mysql-bin
070125 20:27:42 [Note] Starting crash recovery...
070125 20:27:42 [Note] Crash recovery finished.
070125 20:27:43 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=72
max_connections=250
threads_connected=26
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 20:48:28  mysqld restarted
070125 20:48: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...
070125 20:48:30  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 20:48:31  InnoDB: Started; log sequence number 0 6056542
070125 20:48:31 [Note] Recovering after a crash using mysql-bin
070125 20:48:31 [Note] Starting crash recovery...
070125 20:48:31 [Note] Crash recovery finished.
070125 20:48:31 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=59
max_connections=250
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 20:58:52  mysqld restarted
070125 20:58: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...
070125 20:58:52  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 20:58:52  InnoDB: Started; log sequence number 0 6056542
070125 20:58:52 [Note] Recovering after a crash using mysql-bin
070125 20:58:52 [Note] Starting crash recovery...
070125 20:58:52 [Note] Crash recovery finished.
070125 20:58:52 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=78
max_connections=250
threads_connected=30
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 21:09:15  mysqld restarted
070125 21:09: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...
070125 21:09:17  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 21:09:17  InnoDB: Started; log sequence number 0 6056542
070125 21:09:17 [Note] Recovering after a crash using mysql-bin
070125 21:09:17 [Note] Starting crash recovery...
070125 21:09:17 [Note] Crash recovery finished.
070125 21:09:18 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=106
max_connections=250
threads_connected=50
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 21:19:54  mysqld restarted
070125 21:19: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...
070125 21:19:58  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 21:19:59  InnoDB: Started; log sequence number 0 6056542
070125 21:19:59 [Note] Recovering after a crash using mysql-bin
070125 21:19:59 [Note] Starting crash recovery...
070125 21:19:59 [Note] Crash recovery finished.
070125 21:20:00 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
070125 21:25:44 [ERROR] Got error 134 when reading table './mixei_index/post'
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=88
max_connections=250
threads_connected=42
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 21:30:21  mysqld restarted
070125 21:30: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...
070125 21:30:25  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 21:30:25  InnoDB: Started; log sequence number 0 6056542
070125 21:30:25 [Note] Recovering after a crash using mysql-bin
070125 21:30:25 [Note] Starting crash recovery...
070125 21:30:25 [Note] Crash recovery finished.
070125 21:30:26 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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=85
max_connections=250
threads_connected=26
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 783382 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

070125 21:40:28  mysqld restarted
070125 21:40: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...
070125 21:40:30  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6056542.
InnoDB: Doing recovery: scanned up to log sequence number 0 6056542
InnoDB: Last MySQL binlog file position 0 108016930, file name ./mysql-bin.000137
070125 21:40:30  InnoDB: Started; log sequence number 0 6056542
070125 21:40:30 [Note] Recovering after a crash using mysql-bin
070125 21:40:30 [Note] Starting crash recovery...
070125 21:40:30 [Note] Crash recovery finished.
070125 21:40:31 [Note] /usr/local/mysql-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
 
If you got it once, restart MySQL and ignore it.

If you get it more than once, then reinstall/update MySQL. Just how you do it depends on your distribution and how it got installed in the first place.

Jeff
 
That is the problem, that it happens not once. But all the time... MySQL permanently restarting... Its can be seen from the log. And PHP scripts alerting with the error "MySQL server has gone away" =(

I have already reinstalled MySQL. It was in first time installed by DA. Version was 5.0.22, then i installed 5.1.12-beta. Problem still exists... Then i installed this 5.0.27-standard. And the problem again not disapeared =((

I read at the FreeBSD.org that on the 6.0 version could be better to use MySQL server with LinuxThreads. But i dont now how to check with which threads MySQL currently running. And how i have to install it with threads i need?

Because i had not install new versions. I just got already compilied distributions of MySQL from mysql.com for my OS, and then put it in appropriate places... Such as /usr/local/mysql and so on...
 
I don't know anymore, except to ask on a MySQL forum. Is your server running FreeBSD? If so, I'd ask on one of their forums as well.

Let me know, if you're running FreeBSD, what version you're running, and I'll move the thread to that sub-forum, where it may get more attention.

Jeff
 
You must log in or register to reply here.
Back
Top