slave stopped replicating with uncommon errors in the log

[Dan Edwards]

Hi, I have a master -> slave setup that's been working for years. Then 
yesterday I shutdown the slave with a "shutdown -r now", added some more 
ram, booted it back up. Then a few minutes later data stopped being 
inserted/updated into tables. The slave process was still running, and 
the Read_Master_Log_Pos var in "show slave status" was incrementing away 
like everything was just fine. So I looked in the log file and found this:

030911 18:01:51  /usr/sbin/mysqld: Normal shutdown

030911 18:01:51  Slave I/O thread exiting, read up to log 'db-bin.012', 
position 829896886
030911 18:07:57  mysqld started
030911 18:07:58  InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.12-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
030911 18:07:58  Slave I/O thread: connected to master 
'[EMAIL PROTECTED]:3306',  replication started in log 'db-bin.012' at 
position 829896886
030911 18:16:17  Error in Log_event::read_log_event(): 'read error', 
data_len=149,event_type=2
030911 18:16:17  Error reading relay log event: slave SQL thread aborted 
because of I/O error
030911 18:16:17  Could not parse log event entry, check the master for 
binlog corruption
This may also be a network problem, or just a bug in the master or slave 
code.
030911 18:16:17  Error running query, slave SQL thread aborted. Fix the 
problem, and restart the slave SQL thread with "SLAVE START". We stopped 
at log 'db-bin.012' position 829892665

I've searched google for these errors and can't find any solutions. My 
specific question is it says "check the master for binlog corruption" so 
I did a "mysqlbinlog -j 829892665 db-bin.012" on the master and it works 
fine. So no obvious corruption there. Is there anything else to check 
that could be fixed?

I think at the very least there is a pretty obvious bug here that "show 
slave status" doesn't indicate any problems, but no data is being 
inserted/updated into tables.

I'll be taking down the master tonight to get a snapshot to restore the 
slave, resetting the binlogs. If I should save anything for the sake of 
helping track down the above bug let me know before then.

Thanks for any help!
Dan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]