Re: Client requested master to start replication from impossible position

2005-05-03 Thread Gleb Paharenko
Hello.



If the value of Read_Master_Log_Pos has a normal value, and slave

asked weird position, this could be some internal bug. Now I see

only a single way, but it could be difficult: if you have

--log-slave-updates, use slave binary logs to find the last executed

statement and it's position in master logs, and CHANGE MASTER to that

position.





Fagyal Csongor [EMAIL PROTECTED] wrote:

 Hi list,

 

 This night my slave stopped replicating the master (I am using 4.1.11 to 

 replicate 4.1.9). Whenever I say start slave, The error log of the 

 slave says:

 

 050430 10:27:12 [Note] Slave I/O thread: connected to master 

 '[EMAIL PROTECTED]:3306',  replication started in log 

 'www-bin.03' at position 429178917

 050430 10:27:12 [ERROR] Error reading packet from server: Client 

 requested master to start replication from impossible position 

 (server_errno=1236)

 050430 10:27:12 [ERROR] Got fatal error 1236: 'Client requested master 

 to start replication from impossible position' from master when reading 

 data from binary log

 050430 10:27:12 [ERROR] Slave I/O thread exiting, read up to log 

 'www-bin.03', position 429178917

 

 The interesting thing is that for the master:

 -rw-rw   1 mysql  mysql  1073741913 Apr 26 21:52 www-bin.01

 -rw-rw   1 mysql  mysql  1073742497 Apr 29 01:37 www-bin.02

 -rw-rw   1 mysql  mysql   429153165 Apr 29 20:20 www-bin.03

 -rw-rw   1 mysql  mysql   169507064 Apr 30 11:01 www-bin.04

 

 Looks like the master really has no position 429178917 as the length 

 of www-bin.03 is smaller, 429153165 (if I understand this correctly).

 

 Is there a way to restart replication other than copying everything from 

 the slave to the master again??

 

 Thanks,

 - Csongor

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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



Client requested master to start replication from impossible position

2005-04-30 Thread Fagyal Csongor
Hi list,
This night my slave stopped replicating the master (I am using 4.1.11 to 
replicate 4.1.9). Whenever I say start slave, The error log of the 
slave says:

050430 10:27:12 [Note] Slave I/O thread: connected to master 
'[EMAIL PROTECTED]:3306',  replication started in log 
'www-bin.03' at position 429178917
050430 10:27:12 [ERROR] Error reading packet from server: Client 
requested master to start replication from impossible position 
(server_errno=1236)
050430 10:27:12 [ERROR] Got fatal error 1236: 'Client requested master 
to start replication from impossible position' from master when reading 
data from binary log
050430 10:27:12 [ERROR] Slave I/O thread exiting, read up to log 
'www-bin.03', position 429178917

The interesting thing is that for the master:
-rw-rw   1 mysql  mysql  1073741913 Apr 26 21:52 www-bin.01
-rw-rw   1 mysql  mysql  1073742497 Apr 29 01:37 www-bin.02
-rw-rw   1 mysql  mysql   429153165 Apr 29 20:20 www-bin.03
-rw-rw   1 mysql  mysql   169507064 Apr 30 11:01 www-bin.04
Looks like the master really has no position 429178917 as the length 
of www-bin.03 is smaller, 429153165 (if I understand this correctly).

Is there a way to restart replication other than copying everything from 
the slave to the master again??

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