MySQL Bugs: #58516: MYSQL Crashes

Bug #58516	MYSQL Crashes
Submitted:	26 Nov 2010 12:33	Modified:	30 Dec 2010 6:45
Reporter:	Javier Vega	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.0.77	OS:	Linux (Centos 5.5)
Assigned to:		CPU Architecture:	Any

Description:
MySQL server crashes from time to time. In a production server its the second time it crashes.

The log shows the following information:
101126 10:10:03 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=22
max_connections=100
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225787 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aaab007f720
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x46180fb0, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0x46180fb0, stack_bottom=0x46180000, thread_stack=262144, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x1eefc170 = SELECT `EXPEDIENTES_CONTACTOS`.`ID`, `EXPEDIENTES_CONTACTOS`.`EXPEDIENTE`, `EXPEDIENTES_CONTACTOS`.`NOMBRE`, `EXPEDIENTES_CONTACTOS`.`COMENTARIOS`, `EXPEDIENTES_CONTACTOS`.`TELEFON
O1`, `EXPEDIENTES_CONTACTOS`.`TELEFONO2`, `EXPEDIENTES_CONTACTOS`.`TELEFONO3`, (1) AS `mail`, (1) AS `sms`, (1) AS `call`, (1) AS `add`, (1) AS `del`, `PROYECTOS`.`TITULO` AS `PROYECTO`, `PROYECTOS_AGENTES`.
`AGENTE` FROM `EXPEDIENTES_CONTACTOS`
LEFT JOIN `PROYECTOS` ON EXPEDIENTES_CONTACTOS.PROYECTO = PROYECTOS.ID
LEFT JOIN `PROYECTOS_AGENTES` ON EXPEDIENTES_CONTACTOS.PROYECTO = PROYECTOS_AGENTES.PROYECTO WHERE ((EXPEDIENTES_CONTACTOS.EXPEDIENTE = 0 AND EXPEDIENTES_CONTACTOS.AGENTE = 67 ) OR (EXPEDIENTES_CONTACTOS.CL
IENTE = 31 AND PROYECTOS.ESTADO = 1 AND PROYECTOS_AGENTES.AGENTE = 67 )) ORDER BY ID asc LIMIT 20
thd->thread_id=3092
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
101126 10:10:03 mysqld restarted
101126 10:10:03 InnoDB: Started; log sequence number 0 43655
101126 10:10:03 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
101126 10:10:52 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=26
max_connections=100
threads_connected=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225787 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aaab005e540
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x4602bfb0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2aaab00a7580 is invalid pointer
thd->thread_id=2405
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
101126 10:10:52 mysqld restarted

How to repeat:
I do not know

Please, check if the same crash ever happens with a newer version, 5.0.91. If it is, please, send the results of EXPLAIN for the crashing SELECT statement.

Where can I find 5.0.91 rpm's for CentOS 5.0 X86_64?
I couldn't find it in standard repositories.

Thank you for the feedback.

You can get it from http://dev.mysql.com/downloads. Please use either RedHat RPMs or Generic Linux binaries.

Sorry but in http://dev.mysql.com/downloads there is not any RPM (or I could not find it) for Centos 5.5 or RedHat 5 or Generic Linux for the architecture x86_64. There is only for X86 (it is suposed to be 32 bits).

Please, could you tellme the exact URL to download the RPM?

Try this one, http://downloads.mysql.com/archives/mysql-5.0/MySQL-server-community-5.0.91-1.rhel5.x86_64...

Ok, I have the RPM, but how can I install it?

If I use rmp -i it says:
error: Failed dependencies:
        MySQL conflicts with mysql-5.0.77-4.el5_5.4.x86_64
        MySQL conflicts with mysql-5.0.77-4.el5_5.4.i386
        MySQL-server conflicts with mysql-server-5.0.77-4.el5_5.4.x86_64

And if I try to remove that packages, it says:

[root@www backup]# rpm -e mysql-5.0.77-4.el5_5.4.x86_64
error: Failed dependencies:
        libmysqlclient.so.15()(64bit) is needed by (installed) perl-DBD-MySQL-3.0007-2.el5.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) php-mysql-5.1.6-27.el5.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) mysql-server-5.0.77-4.el5_5.4.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) mysql-devel-5.0.77-4.el5_5.4.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) dovecot-1.2.14-1_112.el5.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) postfix-2.3.3-2.1.centos.mysql_pgsql.x86_64
        libmysqlclient.so.15()(64bit) is needed by (installed) pure-ftpd-1.0.21-15.el5.kb.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) perl-DBD-MySQL-3.0007-2.el5.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) php-mysql-5.1.6-27.el5.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) mysql-server-5.0.77-4.el5_5.4.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) dovecot-1.2.14-1_112.el5.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) postfix-2.3.3-2.1.centos.mysql_pgsql.x86_64
        libmysqlclient.so.15(libmysqlclient_15)(64bit) is needed by (installed) pure-ftpd-1.0.21-15.el5.kb.x86_64
        libmysqlclient_r.so.15()(64bit) is needed by (installed) mysql-server-5.0.77-4.el5_5.4.x86_64
        libmysqlclient_r.so.15()(64bit) is needed by (installed) mysql-devel-5.0.77-4.el5_5.4.x86_64
        libmysqlclient_r.so.15(libmysqlclient_15)(64bit) is needed by (installed) mysql-server-5.0.77-4.el5_5.4.x86_64

We have to be sure that databases are not removed and all the data are maintained. Remember, it is a production server.

I already installed mysql 5.1.50 from utterramblings repository.

I am going to monitor is mysql continues crashing.

Thanks for all.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

After installing 5.1.50, no crashes has been detected.