| Bug #64254 | Mysql 5.5.19 hit a bug | ||
|---|---|---|---|
| Submitted: | 7 Feb 2012 20:56 | Modified: | 20 Apr 2012 16:39 |
| Reporter: | Flavian C | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
| Version: | 5.5.19 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[7 Feb 2012 20:56]
Flavian C
[7 Feb 2012 20:57]
Flavian C
------------------------------------------------------------------------------ when i saw the .err file this was the report mysqld got signal 6 ; 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=33554432 read_buffer_size=2097152 max_used_connections=1 max_threads=200 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6998246 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7796bf0 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... stack_bottom = 0x7f077d05d858 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c2729] /usr/sbin/mysqld(handle_segfault+0x3c2)[0x518652] /lib64/libpthread.so.0(+0xf5d0)[0x7f085a36b5d0] /lib64/libc.so.6(gsignal+0x35)[0x7f0859590945] /lib64/libc.so.6(abort+0x181)[0x7f0859591f21] /lib64/libc.so.6(+0x6f8ef)[0x7f08595cd8ef] /lib64/libc.so.6(+0x75018)[0x7f08595d3018] /lib64/libc.so.6(cfree+0x6c)[0x7f08595d7f6c] /usr/sbin/mysqld(_ZN15Query_log_eventD0Ev+0x28)[0x73e558] /usr/sbin/mysqld[0x53523c] /usr/sbin/mysqld(handle_slave_sql+0xada)[0x53777a] /lib64/libpthread.so.0(+0x75f0)[0x7f085a3635f0] /lib64/libc.so.6(clone+0x6d)[0x7f085963284d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query ((nil)): is an invalid pointer Connection ID (thread ID): 10 Status: NOT_KILLED
[8 Feb 2012 4:48]
Valeriy Kravchuk
Please, send the output of: uname -a free from your system.
[8 Feb 2012 6:48]
Flavian C
product1-slave:~ # uname -a
Linux product1-slave 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux
product1-slave:~ # free
total used free shared buffers cached
Mem: 5659556 1421668 4237888 0 36876 539780
-/+ buffers/cache: 845012 4814544
Swap: 9181108 0 9181108
[8 Feb 2012 18:07]
Flavian C
any update????
[10 Feb 2012 15:22]
Flavian C
any progress on the bug...?????
[28 Feb 2012 13:52]
Valeriy Kravchuk
No progress, yet, as it is unclear how to repeat this and I suspect hardware failure more than anything else. Please, upload the entire error log from problematic slave, compressed. Do you still have master's binary log that slave was working with at the moment?
[14 Mar 2012 12:23]
Flavian C
Nope i dont have the binlog file... its deleted every 3days.
[20 Mar 2012 16:39]
Sveta Smirnova
Thank you for the feedback. Looks like we need to wait when issue happens next time. If it does, please: - check for hardware failure (RAM and the disk where MySQL files are located) If hardware is OK: - keep, then send it to us, error log file from slave - keep, then send it to us, master's binary log file which was replicated at the time when issue happened
[21 Apr 2012 1: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".
