I have also encountered this problem when upgrading master and slave from
3.23.31 to 32.23.32. The upgrade of the master went fine, and both servers
remained in sync throughout the process. However, when I upgraded the
slave and restarted, it gave the same error that it could not find first
log. T
On Tuesday 23 January 2001 07:28, Jean-Luc Fontaine wrote:
>On Tuesday 23 January 2001 15:13, you wrote:
>> >Just tried a 3.23.32 slave (on Linux, all rpms from www.mysql.com) against
>> > a
>>
>> 3.23.30 server:
>> >010123 09:38:05 mysqld started
>>
>> /usr/sbin/mysqld: ready for connections
>>
>Just tried a 3.23.32 slave (on Linux, all rpms from www.mysql.com) against a
3.23.30 server:
>010123 09:38:05 mysqld started
/usr/sbin/mysqld: ready for connections
>010123 9:38:05 Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'jfontain-bin.008
' at positi
Just tried a 3.23.32 slave (on Linux, all rpms from www.mysql.com) against a
3.23.30 server:
010123 09:38:05 mysqld started
/usr/sbin/mysqld: ready for connections
010123 9:38:05 Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'jfontain-bin.008
' at position
