Bug #20316 | got signal 4 during startup | ||
---|---|---|---|
Submitted: | 7 Jun 2006 11:53 | Modified: | 12 Jun 2006 2:49 |
Reporter: | Bob Holcomb | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.22 | OS: | Linux (Linux (Gentoo)) |
Assigned to: | CPU Architecture: | Any |
[7 Jun 2006 11:53]
Bob Holcomb
[7 Jun 2006 13:31]
Valeriy Kravchuk
Thank you for the problem report. Please, send the corresponding part of your error log. Is it initial (first time) startup?
[7 Jun 2006 15:19]
Bob Holcomb
mysqld.err log: 060607 7:35:01 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=tiny-bin' to avoid this problem. mysqld got signal 4; 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=258048 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 = 76399 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=0xbff75114, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x814d6af 0x82a2d0f 0x8380184 0x82af68f 0x829984b 0x81d341b 0xb7bca878 0x80ffa41 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.
[8 Jun 2006 8:40]
Heikki Tuuri
The resolved stack trace does not look sensible. Did you use the right mysqld.sym file?
[9 Jun 2006 13:13]
Bob Holcomb
I followed the instructions and generated the sym file from mysqld. I have my glibc built with omit frame pointer. I can rebuild with the frame pointer and put up a new stack trace. Cheers, bob
[11 Jun 2006 8:21]
Valeriy Kravchuk
> I can rebuild with the frame pointer and put up a new stack trace. Please, try to do it and send new resolved stack trace.
[12 Jun 2006 2:49]
Bob Holcomb
Solved: recompiled glibc and mysql with "-O2 -march=i686 -mmmx -msse -mfpmath=sse -pipe" and all was well with the world. I believe that a combination of gcc 4.1, glibc with omit-frame-pointer, and -march=c3-2 may have been a culprit.