Description:
After the MySQL-client-standard-5.0.21-1.sles9.xxxx.rpm is installed, after restarting the box, and every time there after, the mysql server daemon does not start.
Once the box has finished booting, logging in a rcmysql start will sucessfully start the daemon.
One of the errors I have seen is:
060529 09:36:14 mysqld started
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=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
This crash occured while the server was calling initgroups(). This is
often due to the use of a mysqld that is statically linked against glibc
and configured to use LDAP in /etc/nsswitch.conf. You will need to either
upgrade to a version of glibc that does not have this problem (2.3.4 or
later when used with nscd), disable LDAP in your nsswitch.conf, or use a
mysqld that is not statically linked.
060529 09:36:15 mysqld ended
060529 09:49:38 mysqld started
060529 9:49:38 InnoDB: Started; log sequence number 0 43655
060529 9:49:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.21-standard' socket: '/var/lib/mysql/mysql.sock' port:
3306 MySQL Community Edition - Standard (GPL)
^^^ from a x86-64 HP Proliant server
---------------------
060529 10:39:26 mysqld started
mysqld: socket_wrapper.cpp:114: uint yaSSL::Socket::send(const byte*, unsigned int, int) const: Assertion `socket_ != INVALID_SOCKET' failed.
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xbfffe98c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8183f80
0xffffe420
(nil)
0x400c8c03
0x84038a1
0x83f8961
0x840327d
0x83ed313
0x4020f2d9
0x4020f5b8
0x401cfa7c
0x401d1671
0x401c87b1
0x401c8ca6
0x4012dcaf
0x4012deea
0x8185faf
0x818699f
0x400bd210
0x80fcf21
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
This crash occured while the server was calling initgroups(). This is
often due to the use of a mysqld that is statically linked against glibc
and configured to use LDAP in /etc/nsswitch.conf. You will need to either
upgrade to a version of glibc that does not have this problem (2.3.4 or
later when used with nscd), disable LDAP in your nsswitch.conf, or use a
mysqld that is not statically linked.
060529 10:39:29 mysqld ended
^^^^^From x86 in vmware
How to repeat:
Start / Restart the box.
Suggested fix:
No Idea
