Master: mysqld 3.23.58 on FreeBSD 4.10-R
Runs two masters via mysqld_multi
Rotation #1:
10x mysqld 4.0.22 on FreeBSD 4.9-R, 4.10-R
1x mysqld 4.1.8a on FreeBSD 4.10-R
Rotation #2
2x mysqld 4.0.22 on FreeBSD 4.9-R
We have had the following happen twice in the past two weeks: The server
the master runs on crashes and reboots; both master servers start up fine
again by itself with an incrementing binlog position. For both rotations,
all slaves running 4.0.22 reported running fine (both replication threads)
but binlog position was not incrementing. No errors were reported in any
of the error logs. The fix both times was to issue "SLAVE STOP ; SLAVE
START ;". The 4.1 slave has been unaffected in both instances.
Is this a known bug?
Thanks!
Atle
-
Flying Crocodile Inc, Unix Systems Administrator
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
