Public bug reported:
After upgrading to jaunty I have problem with replication system in
mysql. After every system reboot I have to issue RESET SLAVE; START
SLAVE; command to continue this to work. The reason for that is fact
that relays log have higher index number than number stored in mysqld-
relay-bin.index. These two command simply reset that. What is even more
interesting /etc/init.d/mysql restart doesn't generate mentioned
problem.
Description: Ubuntu jaunty (development branch)
Release: 9.04
mysql-server-5.0 5.1.30really5.0.75-0ubuntu10
** Affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
After upgrading to jaunty I have problem with replication system in
mysql. After every system reboot I have to issue RESET SLAVE; START
SLAVE; command to continue this to work. The reason for that is fact
that relays log have higher index number than number stored in mysqld-
relay-bin.index. These two command simply reset that. What is even more
- interesting /etc/init.d/mysql restart works ok.
+ interesting /etc/init.d/mysql restart doesn't generate mentioned
+ problem.
Description: Ubuntu jaunty (development branch)
Release: 9.04
mysql-server-5.0 5.1.30really5.0.75-0ubuntu10
--
Error during mysql slave replication
https://bugs.launchpad.net/bugs/358652
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
