Can no longer start mysqld (version 5)

Installing, Configuring, Troubleshooting server daemons such as Web and Mail
Post Reply
jwilliam
Posts: 2
Joined: 2009/07/16 20:18:01

Can no longer start mysqld (version 5)

Post by jwilliam » 2009/07/16 20:31:42

I've been running mysql version 5.0.68 on centos 4 for several months now and all has been well, but suddenly the mysql daemon won't start. Here is the output from the log file:

090716 15:07:52 mysqld started
090716 15:07:52 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
090716 15:07:52 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
090716 15:07:53 - 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.

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=0xbfd87878, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81a62b5
0x6af0b7
0x836b820
0x8365e35
0x8364e71
0x826cde2
0x825cdeb
0x81a67c5
0x81aa518
0x772271
0x811fe81
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://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090716 15:07:53 mysqld ended


I ran the stack trace like it said on the mysql site. It made no sense to me... but here it is just in case:


0x81a62b5 handle_segfault + 757
0x6af0b7 (?)
0x836b820 dict_table_add_to_cache + 769
0x8365e35 dict_boot + 910
0x8364e71 innobase_start_or_create_for_mysql + 3516
0x826cde2 _Z13innobase_initv + 838
0x825cdeb _Z7ha_initv + 647
0x81a67c5 handle_segfault + 2053
0x81aa518 main + 1510
0x772271 (?)
0x811fe81 _start + 33


I don't know what else to offer. The server was running fine and then, the other day, it just stopped working. Does anyone have an idea?

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Can no longer start mysqld (version 5)

Post by pschaff » 2009/07/17 10:26:01

Is this mysql-5.0.66a-1.el4_6 from CentOSplus? If so, you should file a [url=http://bugs.centos.org/main_page.php]bug report[/url]. If not, where did you get that version and how was it installed?

Post Reply

Return to “CentOS 4 - Server Support”