MySQL Bugs: #14390: Error log.

Bug #14390	Error log.
Submitted:	27 Oct 2005 11:53	Modified:	28 Nov 2005 9:09
Reporter:	Bogdan Tudosie	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.0.18	OS:	Linux (SuSE Linux Enterprise Server.)
Assigned to:		CPU Architecture:	Any

Description:
The mysql server/service refuses to start at system startup, also during manual start. I have produced a part of the error log which I believe would hint more to the error.
I am no developer but I do believe the fragment of error log i have picked would be helpful.
Error log fragment:

051026 14:11:30 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=16777216 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 = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8433638 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... Bogus stack limit or frame pointer, fp=0xbffbcae4, stack_bottom=0x58575655, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x54535251 is invalid pointer thd->thread_id=3 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. 051026 14:11:30 mysqld ended

How to repeat:
I dont know if there would be a way into explaining how to repeat it. MySQL server just receive signal 11 from the system and just dies during either service or manual server startup.

Thank you for a problem report. Please, describe your hardware, provide the error log for the last several days/server starts, without any formatting and describe your latest actions at the OS level (configuration changes, problems etc.). 

The df -k command results may be useful too.

You 4.0.18 is old enough, by the way. Do you have any plans to upgrade, to 4.0.26, for example?

Server Hardware:
IBM eServer XSeries 236 Server, 2xIntel Xeon 64bit 3.2 GHZ CPUs, 2 GB of RAM, Adaptec HostRAID AIC 7902 SCSI Controller, two SCSI hard drives 73.4 GB each set up as RAID 1 array. I am replying to this bug from home and I dont have the server nearby but the problem originated only today 2005.10.27.

I would submit also df -k results but as i said i dont have the server anywhere close and no way to access it via Internet so far. I do plan to upgrade of course once our work internet connection starts working.

Cheers,
Bogdan

OK. So, please, provide the additional information (error log, df -k, last administrative actions, complete my.cnf will be useful too) when you'll be able to get it, and reopen this report.

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".