We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Tags added: apparmor
--
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
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
Ubuntu-server-bugs mailing list
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
apparmor profile in hardy inhibits replication slave
https://bugs.launchpad.net/bugs/307773
You received this bug notification
The apparmor profile should be put in complain mode when upgrading from
gutsy to hardy. As mentioned by andreas, the location of the relay log
files have changed between gutsy and hardy.
Could you post your mysql configuratioon file? Did you set the location
of the relay files manually?
--
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
