Hi Calvin,

I am not sure which table format you use, but somehow I assume you use innodb.

If I remember correctly than Innodb will need all log files. If only one is 
missing than thats it, you get the error described.

- anybody please correct me if I talk rubbish here

Best regards

Nils Valentin
Tokyo/Japan


2003年 6月 3日 火曜日 12:12、Calvin Hill さんは書きました:
> Hello,
>
>     I'm running MySQL Ver 12.18 Distrib 4.0.12 I had replication set up and
> working perfectly between two machines in a round robin fashion. (Serv 1
> updates Serv 2 and Serv 2 updates Serv 1.)
>
>     Recently serv 2 locked up, upon restarting, it automatically began to
> update with the files from serv 1. YEAH so far. Then I noticed that Serv 1
> was not updating from serv 2. I checked all the settings and evertyhing
> seems to be the same, but I'm getting the following in the error log;
>
> 030602 21:03:09  Slave I/O thread: connected to master
> '[EMAIL PROTECTED]:3306',  replication started in log ' serv2-bin.001' at
> position 376
>
> 030602 21:03:09  Error reading packet from server: Could not find first log
> file name in binary log index file (server_errno=1236)
>
> 030602 21:03:09  Got fatal error 1236: 'Could not find first log file name
> in binary log index file' from master when reading data from binary log
>
> 030602 21:03:09  Slave I/O thread exiting, read up to log ' serv2-bin.001',
> position 376
>
>
> And the slave thread quits. I've quit and restarted the mysqld process on
> both servers. I've even reset the master and slave files and re-set the
> servers. Still I get the same error whenever I do a slave start on serv1.
> serv2 is still happily grabbing the changes made to serv1 though.
>
> Any ideas?
>
> Thanks
> Calvin

-- 
================================================
Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
================================================


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

Reply via email to