| Bug #12369 | mysqld restarted | ||
|---|---|---|---|
| Submitted: | 4 Aug 2005 9:51 | Modified: | 7 Sep 2005 11:20 |
| Reporter: | joonghun park | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 4.1.8a | OS: | Linux (RedHat Linux ES release 4) |
| Assigned to: | CPU Architecture: | Any | |
[4 Aug 2005 9:51]
joonghun park
[5 Aug 2005 7:32]
joonghun park
I have two replication slave. sometimes mysql slave is restarted automatically. especialy when i trid to backup( mysqldump) maybe i thinks that this problem is os version.. i just want to know why I have error log from hostname.error ----------------------------------------------------------------------------- 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=402653184 read_buffer_size=2093056 max_used_connections=2 max_connections=300 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1620813 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a85508 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=0xbe1ff3f8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80bd0de 0x8368fbc 0x8e8ec8 0x8d7c4f 0x8d7d0d 0x7849c225 0x7849d304 0x839f548 0x839f3a6 0x80c3064 0x80da6e6 0x83638f9 0x839d49a 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. Reso lved 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=12 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. Number of processes running now: 0 050804 17:20:09 mysqld restarted 050804 17:20:09 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050804 17:20:09 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 1 3975298020. InnoDB: Doing recovery: scanned up to log sequence number 1 3975359773 050804 17:20:09 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 3 7 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 8 1 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 504930146, file name ***-bin.000004 InnoDB: Last MySQL binlog file position 0 3798, file name ./***-bin.000037 050804 17:20:10 InnoDB: Flushing modified pages from the buffer pool... 050804 17:20:11 InnoDB: Started; log sequence number 1 3975359773 /home/test/env/mysql/libexec/mysqld: ready for connections. Version: '4.1.8a-log' socket: '/home/test/env/mysql/tmp/mysql.sock' port: 3306 Source distribution 050804 17:20:11 [Note] Slave SQL thread initialized, starting replication in log '***-bin.000004' at position 504930146, relay lo g './***-relay-bin.000038' position: 743312 050804 17:20:11 [Note] Slave I/O thread: connected to master 'repl@***:3306', replication started in log '***-bin.000 004' at position 504930146 How to repeat: ./mysqldump --opt --database db_name > db_name.sql
[7 Aug 2005 11:20]
Aleksey Kishkin
Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://www.mysql.com/doc/en/Making_trace_files.html Once you have generated a backtrace, please submit it to this bug report and change the status back to 'Open'. Thank you for helping us make our products better.
[7 Sep 2005 23:00]
Bugs System
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".
