Re: Replication failes after long server halt

On 7/6/06, pollox wrote:
> Hi,
>
> A master and a slave server are running on Debian sarge with mysql
> 4.0.24 in our setup.
> Replication worked fine for one year.
> For some reason we had to stop the slave debian server for 6 weeks.
> After restarting the slave the mysql after that period replication
> doesn't work any longer.
> start slave; does not solve the roblem.
>
> this is a: show slave status;
>
> +--------------+-------------+-------------+---------------+ -----------------+---------------------+-------------------- +---------------+-----------------------+------------------+ -------------------+-----------------+---------------------+ ------------+------------+--------------+------------------- --+-----------------+
> | Master_Host | Master_User | Master_Port | Connect_retry |
> Master_Log_File | Read_Master_Log_Pos | Relay_Log_File |
> Relay_Log_Pos | Relay_Master_Log_File | Slave_IO_Running |
> Slave_SQL_Running | Replicate_do_db | Replicate_ignore_db | Last_errno
> | Last_error | Skip_counter | Exec_master_log_pos | Relay_log_space |
> +--------------+-------------+-------------+---------------+ -----------------+---------------------+-------------------- +---------------+-----------------------+------------------+ -------------------+-----------------+---------------------+ ------------+------------+--------------+------------------- --+-----------------+
> | 212.123.9.72 | db_repl | 3306 | 60 |
> mysql-bin.413 | 3632 | crux-relay-bin.002 | 4
> | mysql-bin.413 | No | Yes |
> dns_database | | 0 | | 0
> | 3632 | 4 |
> +--------------+-------------+-------------+---------------+ -----------------+---------------------+-------------------- +---------------+-----------------------+------------------+ -------------------+-----------------+---------------------+ ------------+------------+--------------+------------------- --+-----------------+
>
> When we do a 'load data from master;' the data is replicated from the
> master but only once.
>
> What is wrong with our config?
> Thanks,
> P.

You probably lost some info because of binlog rotation/delete, anyway,
if you can't run the slave, chances are that IF replication starts, it
will have a lot of inconsistency, its not common to let a slave be
down for such a long time. My advice would be to start over with a
snapshot of the database and reset the binlogs, so you'll be sure that
replication is consistent.


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org