List:Replication« Previous MessageNext Message »
From:Artem Koltsov Date:January 26 2005 3:23pm
Subject:RE: error in 4.1.9 replication
View as plain text  
Hello Andrea,

I have 4.1.8 master(Solaris 8)/slave(Win2k) production replication, and slave generates
the same messages at shutdown. I would not worry about them because they look logical
during shutdown, and if I restart a slave it starts without errors and reads master log
at the position when it went down.

Regards,

Artem

> -----Original Message-----
> From: Andrea VILLARDINO [mailto:a.villardino@stripped]
> Sent: Wednesday, January 26, 2005 5:58 AM
> To: replication@stripped
> Subject: error in 4.1.9 replication
> 
> 
> Hi all,
> 
> I have succeeded in implementing MySql Replication between 
> two servers(Sun
> Solaris 8) installed with the 4.1.9 version. The error log reported:
> 
>  
> 
> 050126 09:49:45  mysqld started
> 
> 050126  9:49:46  InnoDB: Started; log sequence number 0 196390890
> 
> /usr/local/mysql-standard-4.1.9-sun-solaris2.8-sparc/bin/mysql
> d: ready for
> connections.
> 
> Version: '4.1.9-standard-log'  socket: '/tmp/mysql.sock'  port: 3306
> Official MySQL-standard binary
> 
> 050126  9:53:53 [Note] Slave SQL thread initialized, starting 
> replication in
> log 'binary.000001' at position 79, relay log
> '/usr/local/mysql/log/relay/relay-bin.000001' position: 4
> 
> 050126  9:53:53 [Note] Slave I/O thread: connected to master
> 'repl@stripped:3306',  replication started in log
> 'binary.000001' at position 79
> 
>  
> 
> I tried some operations as to update a row in the master, or 
> flush logs and
> so on and it seemed to work very well, but when I tried to 
> stop the slave,
> while there was no activitity on the master, with a 
> "mysqladmin -u user
> -ppassword shutdown", I got the following message in the error log:
> 
>  
> 
> 050126 10:04:19 [Note]
> /usr/local/mysql-standard-4.1.9-sun-solaris2.8-sparc/bin/mysql
> d: Normal
> shutdown
> 
>  
> 
> 050126 10:04:19 [ERROR] Slave I/O thread killed while reading event
> 
> 050126 10:04:19 [ERROR] Slave I/O thread exiting, read up to log
> 'binary.000002', position 124
> 
> 050126 10:04:19 [ERROR] Error reading relay log event: slave 
> SQL thread was
> killed
> 
> 050126 10:04:19  InnoDB: Starting shutdown...
> 
> 050126 10:04:21  InnoDB: Shutdown completed; log sequence 
> number 0 196392252
> 
> 050126 10:04:21 [Note]
> /usr/local/mysql-standard-4.1.9-sun-solaris2.8-sparc/bin/mysql
> d: Shutdown
> complete
> 
>  
> 
> 050126 10:04:21  mysqld ended
> 
>  
> 
> I have repeated it and I got always the same error, even with 
> a "stop slave"
> command from mysql prompt.
> 
> Although the errors, when I restart the slave, it seems to 
> connect in the
> right way to the master.
> 
> Have you any idea? Have I to take care of those errors or I 
> can ignore them
> and putting 4.1.9 replication in the production evironmet?
> 
>  
> 
> Thank You In Advance,
> 
> Andrea
> 
> 
 
Attention:
Any views expressed in this message are those of the individual sender, except where the
message states otherwise and the sender is authorized to state them to be the views of
any such entity. The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain confidential and/or
privileged material.  If you received this in error, please contact the sender and delete
the material from any system and destroy any copies.
Thread
error in 4.1.9 replicationAndrea VILLARDINO26 Jan
  • Re: error in 4.1.9 replicationLars Thalmann26 Jan
  • Re: Apache log errorsDarshan Jadav26 Feb
RE: error in 4.1.9 replicationArtem Koltsov26 Jan