There is a bug here somewhere, just not the obvious one :)
Actually apparmor handles mysql replication without any trouble on a
fresh hardy install.
The problem arises from the fact that the default relay-log changes from
gutsy to hardy. In gutsy it is /var/run/mysqld-relay-bin.* while hardy
uses /var/run/mysqld-relay-bin.*.
By the way, how did you manage to upgrade your mysql-slave from gutsy to
hardy without breaking (except the apparmor part) its replication? I
used do-release-upgrade and it somehow managed to sabotage my relay-
bin:s in different ways, depending on whatever I kept a relay-log= in
my my.cnf or not.
If you don't object I'll mark this bug as invalid, as it really isn't a
problem with the apparmor profiles in Hardy. Instead I believe we should
create a new bug, dealing with the issues of upgrading a mysql-slave
from Gutsy to Hardy.
** Changed in: mysql-dfsg-5.0 (Ubuntu)
Status: New => Incomplete
--
apparmor profile in hardy inhibits replication slave
https://bugs.launchpad.net/bugs/307773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
