David, I'm using juju 1.16.4.1 on Ubuntu 12.04. If I just deploy mysql with no config changes, the issue still exists. However, if I decrease the size of the innodb_buffer_pool_size setting (using "juju set mysql dataset-size='512M'") as stated in https://bugs.launchpad.net/juju-core/+bug/1236994 it works fine.
Daniele On Wed, Feb 5, 2014 at 9:30 AM, David Cheney <[email protected]>wrote: > https://bugs.launchpad.net/juju-core/+bug/1236994 is a dup of > https://bugs.launchpad.net/juju-core/+bug/1247299, both of which are > claimed to be resolved. > > Daniele, if this is still a problem with the latest development release of > Juju please reopen one of these or open a new issue as soon as possible. > > > On Wed, Feb 5, 2014 at 8:25 PM, Jorge O. Castro <[email protected]> wrote: > >> On Tue, Feb 4, 2014 at 11:10 PM, David Cheney >> <[email protected]> wrote: >> > Looks like an apparmor issue to me. >> >> We've had this problem in the past with MySQL/apparmor/local provider: >> >> https://bugs.launchpad.net/juju-core/+bug/1236994 >> https://bugs.launchpad.net/juju-core/+bug/1247299 >> >> >> >> -- >> Jorge Castro >> Canonical Ltd. >> http://juju.ubuntu.com/ - Automate your Cloud Infrastructure >> > >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
