Sasha,

Running the latest binary I just built, I had a single core dump and
auto-restart early this morning.  Here's the backtrace:

---snip---

Core was generated by `mysqld'.
Program terminated with signal 6, Abort trap.
Reading symbols from /usr/lib/libz.so.2...done.
Reading symbols from /usr/lib/libcrypt.so.2...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libc_r.so.4...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0  0x2839d330 in kill () from /usr/lib/libc_r.so.4
(gdb) bt
#0  0x2839d330 in kill () from /usr/lib/libc_r.so.4
#1  0x283e9ab1 in abort () from /usr/lib/libc_r.so.4
#2  0x283c377d in __assert () from /usr/lib/libc_r.so.4
#3  0x80f75c8 in next_event (rli=0x8305e2c) at slave.cc:2376
#4  0x80f52da in exec_relay_log_event (thd=0x203b5818, rli=0x8305e2c)
    at slave.cc:1533
#5  0x80f646d in handle_slave_sql (arg=0x8305ae0) at slave.cc:1887
#6  0x2837403b in _thread_start () from /usr/lib/libc_r.so.4
#7  0x0 in ?? ()

---snip---

And the relevant bits from the log, with an assert failure just before
the restart:

---snip---

020309  3:02:21  next log './db3-relay-bin.007' is not active
020309  3:14:59  Error in Log_event::read_log_event(): 'read error', 
data_len=283,event_type=2
020309  3:14:59  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=247)
assertion "((cur_log)->pos_in_file + (uint) (*(cur_log)->current_pos - 
(cur_log)->request_pos)) == rli->relay_log_pos + rli->pending" failed: file 
"slave.cc", line 2376
020309 03:15:20  mysqld restarted
Warning: One can only use the --user switch if running as root
/home/mysql-4-bk/libexec/mysqld: ready for connections
020309  3:15:22  Error in accept: Software caused connection abort
020309  3:15:22  Slave I/O thread initialized
020309  3:15:22  Slave SQL thread initialized, starting replication in log 
'binary-log.048' at position 535046117,relay log: 
name='./db3-relay-bin.007',pos='42811130'
020309  3:15:22  Error in Log_event::read_log_event(): 'read error', 
data_len=283,event_type=2
020309  3:15:22  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=247)
020309  3:15:23  next log './db3-relay-bin.008' is not active
020309  3:15:23  next log './db3-relay-bin.009' is not active
020309  3:15:23  next log './db3-relay-bin.010' is not active
020309  3:15:23  next log './db3-relay-bin.011' is not active
020309  3:15:23  next log './db3-relay-bin.012' is not active
020309  3:15:23  next log './db3-relay-bin.013' is not active
020309  3:15:23  next log './db3-relay-bin.014' is not active
020309  3:15:23  next log './db3-relay-bin.015' is not active
020309  3:15:23  next log './db3-relay-bin.016' is not active
020309  3:15:23  next log './db3-relay-bin.017' is not active
020309  3:15:23  next log './db3-relay-bin.018' is not active
020309  3:15:23  next log './db3-relay-bin.019' is not active
020309  3:15:23  next log './db3-relay-bin.020' is not active
020309  3:15:23  next log './db3-relay-bin.021' is not active
020309  3:15:23  next log './db3-relay-bin.022' is not active
020309  3:15:23  next log './db3-relay-bin.023' is not active
020309  3:15:23  next log './db3-relay-bin.024' is not active
020309  3:15:23  next log './db3-relay-bin.025' is not active
020309  3:15:23  next log './db3-relay-bin.026' is not active
020309  3:15:23  next log './db3-relay-bin.027' is not active
020309  3:15:23  next log './db3-relay-bin.028' is not active
020309  3:15:23  next log './db3-relay-bin.029' is not active
020309  3:15:23  next log './db3-relay-bin.030' is not active
020309  3:15:23  next log './db3-relay-bin.031' is not active
020309  3:15:23  next log './db3-relay-bin.032' is not active
020309  3:15:23  next log './db3-relay-bin.033' is not active
020309  3:15:23  next log './db3-relay-bin.034' is not active
020309  3:15:23  next log './db3-relay-bin.035' is not active
020309  3:15:23  next log './db3-relay-bin.036' is not active
020309  3:15:23  next log './db3-relay-bin.037' is not active
020309  3:15:23  next log './db3-relay-bin.038' is not active
020309  3:15:23  next log './db3-relay-bin.039' is not active
020309  3:15:23  next log './db3-relay-bin.040' is not active
020309  3:15:23  next log './db3-relay-bin.041' is not active
020309  3:15:23  next log './db3-relay-bin.042' is not active
020309  3:15:23  next log './db3-relay-bin.043' is not active
020309  3:15:23  next log './db3-relay-bin.044' is not active
020309  3:15:23  next log './db3-relay-bin.045' is not active
020309  3:15:23  next log './db3-relay-bin.046' is not active
020309  3:15:23  next log './db3-relay-bin.047' is not active
020309  3:15:23  next log './db3-relay-bin.048' is not active
020309  3:15:23  next log './db3-relay-bin.049' is not active
020309  3:15:23  next log './db3-relay-bin.050' is not active
020309  3:15:23  next log './db3-relay-bin.051' is not active
020309  3:15:23  next log './db3-relay-bin.052' is not active
020309  3:15:23  next log './db3-relay-bin.053' is not active
020309  3:15:23  next log './db3-relay-bin.054' is not active
020309  3:15:23  next log './db3-relay-bin.055' is not active
020309  3:15:23  next log './db3-relay-bin.056' is not active
020309  3:15:23  next log './db3-relay-bin.057' is not active
020309  3:15:23  next log './db3-relay-bin.058' is not active
020309  3:15:23  next log './db3-relay-bin.059' is not active
020309  3:15:23  next log './db3-relay-bin.060' is not active
020309  3:15:23  next log './db3-relay-bin.061' is not active
020309  3:15:23  next log './db3-relay-bin.062' is not active
020309  3:15:23  next log './db3-relay-bin.063' is not active
020309  3:15:23  next log './db3-relay-bin.064' is not active
020309  3:15:23  next log './db3-relay-bin.065' is not active
020309  3:15:23  next log './db3-relay-bin.066' is not active
020309  3:15:23  next log './db3-relay-bin.067' is not active
020309  3:15:23  next log './db3-relay-bin.068' is not active
020309  3:15:23  next log './db3-relay-bin.069' is not active
020309  3:15:23  next log './db3-relay-bin.070' is not active
020309  3:15:23  next log './db3-relay-bin.071' is not active
020309  3:15:23  next log './db3-relay-bin.072' is not active
020309  3:15:23  next log './db3-relay-bin.073' is not active
020309  3:15:23  next log './db3-relay-bin.074' is not active
020309  3:15:23  next log './db3-relay-bin.075' is not active
020309  3:15:23  next log './db3-relay-bin.076' is not active
020309  3:15:23  next log './db3-relay-bin.077' is not active
020309  3:15:23  next log './db3-relay-bin.078' is not active
020309  3:15:23  next log './db3-relay-bin.079' is not active
020309  3:15:23  next log './db3-relay-bin.080' is not active
020309  3:15:23  next log './db3-relay-bin.081' is not active
020309  3:15:23  next log './db3-relay-bin.082' is not active
020309  3:15:23  next log './db3-relay-bin.083' is not active
020309  3:15:23  next log './db3-relay-bin.084' is not active
020309  3:15:23  next log './db3-relay-bin.085' is not active
020309  3:15:23  next log './db3-relay-bin.086' is not active
020309  3:15:23  next log './db3-relay-bin.087' is not active
020309  3:15:23  next log './db3-relay-bin.088' is not active
020309  3:15:23  next log './db3-relay-bin.089' is not active
020309  3:15:23  next log './db3-relay-bin.090' is not active
020309  3:15:23  next log './db3-relay-bin.091' is not active
020309  3:15:23  next log './db3-relay-bin.092' is not active
020309  3:15:23  next log './db3-relay-bin.093' is not active
020309  3:15:23  next log './db3-relay-bin.094' is not active
020309  3:15:23  next log './db3-relay-bin.095' is not active
020309  3:15:23  next log './db3-relay-bin.096' is not active
020309  3:15:23  next log './db3-relay-bin.097' is not active
020309  3:15:23  next log './db3-relay-bin.098' is not active
020309  3:15:23  next log './db3-relay-bin.099' is not active
020309  3:15:23  next log './db3-relay-bin.100' is not active
020309  3:15:23  next log './db3-relay-bin.101' is not active
020309  3:15:23  next log './db3-relay-bin.102' is not active
020309  3:15:23  next log './db3-relay-bin.103' is not active
020309  3:15:23  next log './db3-relay-bin.104' is not active
020309  3:15:23  next log './db3-relay-bin.105' is not active
020309  3:15:23  next log './db3-relay-bin.106' is not active
020309  3:15:23  next log './db3-relay-bin.107' is not active
020309  3:15:23  next log './db3-relay-bin.108' is not active
020309  3:15:23  next log './db3-relay-bin.109' is not active
020309  3:15:23  next log './db3-relay-bin.110' is not active
020309  3:15:23  next log './db3-relay-bin.111' is not active
020309  3:15:23  next log './db3-relay-bin.112' is not active
020309  3:15:23  next log './db3-relay-bin.113' is not active
020309  3:15:23  next log './db3-relay-bin.114' is not active
020309  3:15:23  next log './db3-relay-bin.115' is not active
020309  3:15:23  next log './db3-relay-bin.116' is not active
020309  3:15:23  next log './db3-relay-bin.117' is not active
020309  3:15:23  next log './db3-relay-bin.118' is not active
020309  3:15:23  next log './db3-relay-bin.119' is not active
020309  3:15:23  next log './db3-relay-bin.120' is not active
020309  3:15:23  next log './db3-relay-bin.121' is not active
020309  3:15:23  next log './db3-relay-bin.122' is not active
020309  3:15:23  next log './db3-relay-bin.123' is not active
020309  3:15:23  next log './db3-relay-bin.124' is not active
020309  3:15:23  next log './db3-relay-bin.125' is not active
020309  3:15:23  next log './db3-relay-bin.126' is not active
020309  3:15:23  next log './db3-relay-bin.127' is not active
020309  3:15:23  next log './db3-relay-bin.128' is not active
020309  3:15:23  next log './db3-relay-bin.129' is not active
020309  3:15:23  next log './db3-relay-bin.130' is not active
020309  3:15:23  next log './db3-relay-bin.131' is not active
020309  3:15:23  next log './db3-relay-bin.132' is not active
020309  3:15:23  next log './db3-relay-bin.133' is not active
020309  3:15:27  Slave I/O thread: connected to master 
'[EMAIL PROTECTED]:3306',  replication started in log 'binary-log.050' at 
position 23906110

---snip---

I believe that most of those relay files were produced during the
previous "core dump, restart, core dump" cycle that you fixed.  If
memory serves, they were all 4 bytes in length.

Let me know if you need any more data from me.

Thanks!

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 30 days, processed 1,024,434,500 queries (393/sec. avg)

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

Reply via email to