RE: Slave replication problem

2004-09-06 Thread Andrew Braithwaite
did you get an answer to your problem yet?  If not I may be able to help..
 
Andrew



From: Jeff McKeon [mailto:[EMAIL PROTECTED]
Sent: Fri 03/09/2004 15:29
To: [EMAIL PROTECTED]
Subject: Slave replication problem



Hello all,

We had a power outage this morning and before we could shut down our
main MySQL server, power to it was lost.  Bad UPS battery. Long
story.

We replicate this server to two others.  On one I get the following
error...



Jeff McKeon
IT Manager*** 1. row ***
  Master_Host: 10.32.1.10
  Master_User: repl
  Master_Port: 3306
Connect_retry: 60
  Master_Log_File: DB01TC07927-bin.022
  Read_Master_Log_Pos: 2223919
   Relay_Log_File: DB02TC07927-relay-bin.286
Relay_Log_Pos: 16361931
Relay_Master_Log_File: DB01TC07927-bin.021
 Slave_IO_Running: Yes
Slave_SQL_Running: No
  Replicate_do_db:
  Replicate_ignore_db:
   Last_errno: 0
   Last_error: Could not parse relay log event entry. The
possible reasons are: the master's binary log is corrupted (you can
check this by running 'mysqlbinlog' on the binary log), the slave's
relay log is corrupted (you can check this by running 'mysqlbinlog' on
the relay log), a network problem, or a bug in the master's or slave's
MySQL code. If you want to check the master's binary log or slave's
relay log, you will be able to know their names by issuing 'SHOW SLAVE
STATUS' on this slave.
 Skip_counter: 0
  Exec_master_log_pos: 85068331
  Relay_log_space: 18604700
1 row in set (0.00 sec)


On the other I'm getting...

*** 1. row ***
  Master_Host: 10.32.1.10
  Master_User: repl
  Master_Port: 3306
Connect_retry: 60
  Master_Log_File: DB01TC07927-bin.021
  Read_Master_Log_Pos: 85079027
   Relay_Log_File: mis02tc07927-relay-bin.106
Relay_Log_Pos: 4
Relay_Master_Log_File: DB01TC07927-bin.021
 Slave_IO_Running: No
Slave_SQL_Running: Yes
  Replicate_do_db:
  Replicate_ignore_db:
   Last_errno: 0
   Last_error:
 Skip_counter: 0
  Exec_master_log_pos: 85079027
  Relay_log_space: 4
1 row in set (0.00 sec)


>From the server.err log I have:

040903 14:00:01  Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306',  replication started in log
'DB01TC07927-bin.021' at position 85079027
040903 14:00:01  Error reading packet from server: Client requested
master to start replication from impossible position (server_errno=1236)
040903 14:00:01  Got fatal error 1236: 'Client requested master to start
replication from impossible position' from master when reading data from
binary log
040903 14:00:01  Slave I/O thread exiting, read up to log
'DB01TC07927-bin.021', position 85079027

How do I fix these problems?

Thanks,

Jeff

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





Slave replication problem

2004-09-03 Thread Jeff McKeon
Hello all,

We had a power outage this morning and before we could shut down our
main MySQL server, power to it was lost.  Bad UPS battery. Long
story.

We replicate this server to two others.  On one I get the following
error...



Jeff McKeon
IT Manager*** 1. row ***
  Master_Host: 10.32.1.10
  Master_User: repl
  Master_Port: 3306
Connect_retry: 60
  Master_Log_File: DB01TC07927-bin.022
  Read_Master_Log_Pos: 2223919
   Relay_Log_File: DB02TC07927-relay-bin.286
Relay_Log_Pos: 16361931
Relay_Master_Log_File: DB01TC07927-bin.021
 Slave_IO_Running: Yes
Slave_SQL_Running: No
  Replicate_do_db:
  Replicate_ignore_db:
   Last_errno: 0
   Last_error: Could not parse relay log event entry. The
possible reasons are: the master's binary log is corrupted (you can
check this by running 'mysqlbinlog' on the binary log), the slave's
relay log is corrupted (you can check this by running 'mysqlbinlog' on
the relay log), a network problem, or a bug in the master's or slave's
MySQL code. If you want to check the master's binary log or slave's
relay log, you will be able to know their names by issuing 'SHOW SLAVE
STATUS' on this slave.
 Skip_counter: 0
  Exec_master_log_pos: 85068331
  Relay_log_space: 18604700
1 row in set (0.00 sec)


On the other I'm getting...

*** 1. row ***
  Master_Host: 10.32.1.10
  Master_User: repl
  Master_Port: 3306
Connect_retry: 60
  Master_Log_File: DB01TC07927-bin.021
  Read_Master_Log_Pos: 85079027
   Relay_Log_File: mis02tc07927-relay-bin.106
Relay_Log_Pos: 4
Relay_Master_Log_File: DB01TC07927-bin.021
 Slave_IO_Running: No
Slave_SQL_Running: Yes
  Replicate_do_db:
  Replicate_ignore_db:
   Last_errno: 0
   Last_error:
 Skip_counter: 0
  Exec_master_log_pos: 85079027
  Relay_log_space: 4
1 row in set (0.00 sec)


>From the server.err log I have:

040903 14:00:01  Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306',  replication started in log
'DB01TC07927-bin.021' at position 85079027
040903 14:00:01  Error reading packet from server: Client requested
master to start replication from impossible position (server_errno=1236)
040903 14:00:01  Got fatal error 1236: 'Client requested master to start
replication from impossible position' from master when reading data from
binary log
040903 14:00:01  Slave I/O thread exiting, read up to log
'DB01TC07927-bin.021', position 85079027

How do I fix these problems?

Thanks,

Jeff

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