mysql 4.0.5a binary crashed with following error messages. What's the problem? :(
021128 11:06:23 Slave I/O thread: connected to master 'austin@atis1:3306', replication started in log 'FIRST' at position 4 021128 17:35:52 Slave: received 0 length packet from server, apparent master shutdown: 021128 17:35:52 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'atis1-bin.036' position 754 021128 17:35:52 Slave I/O thread: error reconnecting to master 'austin@atis1:3306': Error: 'Can't connect to MySQL server on 'atis1' (111)' errno: 2003 retry-time: 60 retries: 86400 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=268431360 read_buffer_size=1044480 sort_buffer_size=1048568 max_used_connections=1 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 = 466539 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x86efad0 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=0xbfe3f2d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x806eedb 0x8268018 0x80ad5a5 0x80ae086 0x80e234a 0x80e2e4a 0x82657cc New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/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 (nil) is invalid pointer thd->thread_id=4 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 4 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid. The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 2 -- Chung Ha-nyung <alita@[neowiz.com|kldp.org]> SayClub <http://www.sayclub.com> NeoWiz <http://www.neowiz.com> --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
