Did you look in the error log for the slave to find out the reason it can 
not contact the master?

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 3/15/04, 1:39:44 PM, Daniel Gibby <[EMAIL PROTECTED]> wrote 
regarding hard boot killed replication execution:


> My master server was hard booted and now my slave can't execute the
> replicated binary sql logs.

> mysql> show slave status\G
> *************************** 1. row ***************************
>           Master_Host: post.somehost.com
>           Master_User: replicator
>           Master_Port: 3306
>         Connect_retry: 60
>       Master_Log_File: post-bin.118
>   Read_Master_Log_Pos: 651380657
>        Relay_Log_File: backups-relay-bin.025
>         Relay_Log_Pos: 4
> Relay_Master_Log_File: post-bin.111
>      Slave_IO_Running: No
>     Slave_SQL_Running: No
>       Replicate_do_db:
>   Replicate_ignore_db:
>            Last_errno: 0
>            Last_error:
>          Skip_counter: 1
>   Exec_master_log_pos: 462778298
>       Relay_log_space: 5987610630
> 1 row in set (0.00 sec)

> I can execute slave start and the IO will keep on running. (I think I
> had to execute some command to accomplish this, but it was a couple of
> weeks ago, and I don't remember what the command was.)
> mysql> slave start;
> Query OK, 0 rows affected (0.00 sec)

> mysql> show slave status\G
> *************************** 1. row ***************************
>           Master_Host: post.somehost
>         Connect_retry: 60
>       Master_Log_File: post-bin.118
>   Read_Master_Log_Pos: 651817308
>        Relay_Log_File: backups-relay-bin.025
>         Relay_Log_Pos: 4
> Relay_Master_Log_File: post-bin.111
>      Slave_IO_Running: Yes
>     Slave_SQL_Running: No
>       Replicate_do_db:
>   Replicate_ignore_db:
>            Last_errno: 0
>            Last_error:
>          Skip_counter: 1
>   Exec_master_log_pos: 462778298
>       Relay_log_space: 5988047320
> 1 row in set (0.00 sec)

> As you can see, my relay logs are starting to take up a _lot_ of space
> and I really need to start executing them or I'll never catch up.
> This is the contents of my directory where the logs are:
> -rw-rw----    1 mysqld   mysqld         79 Oct  7 23:10 backups-bin.001
> -rw-rw----    1 mysqld   mysqld         79 Oct 10 08:47 backups-bin.002
> etc....
> -rw-rw----    1 mysqld   mysqld       3035 Feb  9 14:18 backups-bin.023
> -rw-rw----    1 mysqld   mysqld        573 Mar  8 18:41 backups-bin.024
> -rw-rw----    1 mysqld   mysqld         79 Mar  9 10:39 backups-bin.025
> -rw-rw----    1 mysqld   mysqld        450 Mar  9 10:39 backups-bin.index
> -rw-rw----    1 mysqld   mysqld   611349208 Mar  9 07:42
> backups-relay-bin.024
> -rw-rw----    1 mysqld   mysqld   1073741983 Mar 10 08:52
> backups-relay-bin.025
> etc...
> -rw-rw----    1 mysqld   mysqld   1073742041 Mar 15 11:12
> backups-relay-bin.029
> -rw-rw----    1 mysqld   mysqld   19673092 Mar 15 11:34
> backups-relay-bin.030
> -rw-rw----    1 mysqld   mysqld        168 Mar 15 11:12
> backups-relay-bin.index
> -rw-rw----    1 mysqld   root       315954 Mar 15 11:31
> backups.somehost.com.err
> -rw-rw----    1 mysqld   mysqld          5 Mar  9 10:39
> backups.somehost.com.pid
> -rw-rw----    1 mysqld   mysqld   10485624 Mar  1 22:32 log.0000000055
> etc...
> -rw-rw----    1 mysqld   mysqld    9005000 Mar 15 11:14 log.0000000063
> drwx------    2 mysqld   mysqld      16384 Aug 18  2003 lost+found
> -rw-rw----    1 mysqld   mysqld         81 Mar 15 11:34 master.info
> -rw-r--r--    1 mysqld   mysqld       5023 Mar  9 10:39 my.cnf
> drwx------    2 mysqld   mysqld       4096 Nov 18 06:52 mysql
> -rw-rw----    1 mysqld   mysqld         59 Mar  9 11:13 relay-log.info
> and the directories for my databases.

> I used mysqlbinlog to check what the last part of the
> backups-relay-bin.024 contents were and queried and saw that it really
> has completed it's statements. Looking at the head of the
> backups-relay-bin.025 reveals that its queries haven't been executed. So
> I think I need to somehow change the server to start executing at 025,
> right?
> When I execute CHANGE MASTER TO RELAY_LOG_FILE='backups-relay-bin.025'
> RELAY_LOG_POS=4; I get this:
> ERROR 1105: Failed initializing relay log position: Could not find
> target log during relay log initialization

> What does that mean? I can't find documenation on it anywhere.

> Am I going about recovering this correctly? HELP!

> Thanks,
> Daniel Gibby

> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    
http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to