Re: MySQL charm: hook failed: config-changed
Which cloud were you running this against? On Feb 3, 2014 5:23 PM, Daniele Stroppa daniele.stro...@joyent.com wrote: Hi All, while running test for the Node.js charm I ran into an issue with the MySQL charm, see attached log. It looks like it's a permissions issue. I'm running on Ubuntu 12.04 with juju 1.16.4.1 and MySQL charm from cs:precise/mysql-32 Anyone has seen this before? Thanks, Daniele -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: MySQL charm: hook failed: config-changed
Thanks Marco! Abs, Sebas. 2014-02-04 19:07 GMT-02:00 Marco Ceppi ma...@ceppi.net: Hi Daniele, I'm digging further in to the issue. I can replicate the error on local provider and az2 of HP cloud, but ec2 and az1/az3 of HP cloud are unaffected. I'll try to have a patch out tomorrow, if not tonight, addressing the issue. Thanks, Marco On Feb 4, 2014 10:04 PM, Daniele Stroppa daniele.stro...@joyent.com wrote: Mark, I tried again giving 2G and 4G to the local provider, but no luck. Daniele On Tue, Feb 4, 2014 at 8:13 PM, Mark Shuttleworth m...@ubuntu.comwrote: Hi Daniele, I think the question is whether you have enough memory - can you give it more with the local provider? Mark On 04/02/14 15:55, Daniele Stroppa wrote: Maarten, Curtis, I tried to deploy mysql on the local provider with as little as 256M of memory, but I still get the same error. Daniele On Tue, Feb 4, 2014 at 12:22 PM, Curtis Hovey-Canonical cur...@canonical.com wrote: On Tue, Feb 4, 2014 at 12:29 PM, Maarten Ectors maarten.ect...@canonical.com wrote: In the past I had an issue with the MySQL charm whereby it had some parameter set to 4GB and I did not have enough memory. I don't remember the exact parameter but it is in the /etc/mysql/my.cnf. By reducing it to a smaller number that fits. If this problem still exists then let me know and we will file a bug... The error is ambiguous, something went wrong after mysql installed. This does however match what we saw when mysql didn't get enough memory. When I create deploy mysql on azure and ec2, i do juju bootstrap --contraints mem=2G mysql For hp I give it 4G juju bootstrap --contraints mem=4G mysql -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: MySQL charm: hook failed: config-changed
Hi Daniele,
i'm trying to deploy wordpress with mysql inside Vagrant (
https://juju.ubuntu.com/docs/config-vagrant.html) and doesn't matter what I
do like downloading each images of ubuntu versions, mysql always give that
error, even lowering the dataset-size :(
@Marco, whats your thoughts about this? I'm starting with Ubuntu Juju and
this is blocking my charms development :( like the Drupal charm.
Some help? :)
Thanks!!!,
Sebas.
2014-02-10 13:42 GMT-02:00 Sebastian sebas5...@gmail.com:
Oh! I see, thank you Daniele!
Abs,
Sebas.
2014-02-10 13:36 GMT-02:00 Daniele Stroppa daniele.stro...@joyent.com:
Hi Sebastian,
I believe Marco is looking into this.
In the meantime, a workaround that works for me is to set the
dataset-size to a fixed (low) value, e.g.:
juju deploy mysql
juju set mysql dataset-size='512M'
Cheers,
Daniele
On Mon, Feb 10, 2014 at 3:03 PM, Sebastian sebas5...@gmail.com wrote:
Hi! I'm with the same issue with juju-local and the mysql charm, maybe
is because the version of the Ubuntu is Trusty.
I tried a lot of things, like creating swap into the container, and
lowering the innodb_buffer_pool_size, but it seems that nothing is
working, so mysql isn't starting.
Some help would be great!
Cheers!,
Sebas.
2014-02-06 12:39 GMT-02:00 Marco Ceppi marco.ce...@canonical.com:
Hi Daniele,
That's expected behavior with Amulet, as it caches the charm locally to
do some verification against the charms in the deployment. So it deploys
from local: rather than the charm store.
As for the dataset-size, if 80% isn't a sane value, I'll try various
other default values to make sure it deploys consistently and everytime on
all cloud providers. I'm in the process of writing tests for the MySQL
charm so we'll have better exposure of this issue sooner.
Thanks,
Marco Ceppi
On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa
daniele.stro...@joyent.com wrote:
David,
I missed that requirements, I was using the 3.5 kernel. I've updated
to the raring kernel, and deploying mysql using 'juju deploy' with no
additional configuration still give the same issue. Setting the
innodb_buffer_pool_size as mentioned yesterday works fine.
@Marco: One thing I've noticed is that when deploying mysql with juju
deploy the charm being deployed is 'cs:precise/mysql-33', while when
running the test the charm is 'local:precise/mysql-310' (in the .py file I
do specify 'd.add('mysql', charm='cs:precise/mysql-33')'). Is this normal?
Daniele
On Wed, Feb 5, 2014 at 8:05 PM, David Cheney
david.che...@canonical.com wrote:
You said earlier that you were using the local provider. Have you
applied the raring kernel update to this machine ? This is required if
you
want to use LXC on Precise.
On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa
daniele.stro...@joyent.com wrote:
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
david.che...@canonical.com 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
jo...@ubuntu.comwrote:
On Tue, Feb 4, 2014 at 11:10 PM, David Cheney
david.che...@canonical.com 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 mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: MySQL charm: hook failed: config-changed
Hi Sebastian,
I believe Marco is looking into this.
In the meantime, a workaround that works for me is to set the dataset-size
to a fixed (low) value, e.g.:
juju deploy mysql
juju set mysql dataset-size='512M'
Cheers,
Daniele
On Mon, Feb 10, 2014 at 3:03 PM, Sebastian sebas5...@gmail.com wrote:
Hi! I'm with the same issue with juju-local and the mysql charm, maybe is
because the version of the Ubuntu is Trusty.
I tried a lot of things, like creating swap into the container, and
lowering the innodb_buffer_pool_size, but it seems that nothing is
working, so mysql isn't starting.
Some help would be great!
Cheers!,
Sebas.
2014-02-06 12:39 GMT-02:00 Marco Ceppi marco.ce...@canonical.com:
Hi Daniele,
That's expected behavior with Amulet, as it caches the charm locally to
do some verification against the charms in the deployment. So it deploys
from local: rather than the charm store.
As for the dataset-size, if 80% isn't a sane value, I'll try various
other default values to make sure it deploys consistently and everytime on
all cloud providers. I'm in the process of writing tests for the MySQL
charm so we'll have better exposure of this issue sooner.
Thanks,
Marco Ceppi
On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa
daniele.stro...@joyent.com wrote:
David,
I missed that requirements, I was using the 3.5 kernel. I've updated to
the raring kernel, and deploying mysql using 'juju deploy' with no
additional configuration still give the same issue. Setting the
innodb_buffer_pool_size as mentioned yesterday works fine.
@Marco: One thing I've noticed is that when deploying mysql with juju
deploy the charm being deployed is 'cs:precise/mysql-33', while when
running the test the charm is 'local:precise/mysql-310' (in the .py file I
do specify 'd.add('mysql', charm='cs:precise/mysql-33')'). Is this normal?
Daniele
On Wed, Feb 5, 2014 at 8:05 PM, David Cheney david.che...@canonical.com
wrote:
You said earlier that you were using the local provider. Have you
applied the raring kernel update to this machine ? This is required if you
want to use LXC on Precise.
On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa
daniele.stro...@joyent.com wrote:
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
david.che...@canonical.com 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 jo...@ubuntu.comwrote:
On Tue, Feb 4, 2014 at 11:10 PM, David Cheney
david.che...@canonical.com 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 mailing list
j...@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
Hi Daniele,
That's expected behavior with Amulet, as it caches the charm locally to do
some verification against the charms in the deployment. So it deploys from
local: rather than the charm store.
As for the dataset-size, if 80% isn't a sane value, I'll try various other
default values to make sure it deploys consistently and everytime on all
cloud providers. I'm in the process of writing tests for the MySQL charm so
we'll have better exposure of this issue sooner.
Thanks,
Marco Ceppi
On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa
daniele.stro...@joyent.comwrote:
David,
I missed that requirements, I was using the 3.5 kernel. I've updated to
the raring kernel, and deploying mysql using 'juju deploy' with no
additional configuration still give the same issue. Setting the
innodb_buffer_pool_size as mentioned yesterday works fine.
@Marco: One thing I've noticed is that when deploying mysql with juju
deploy the charm being deployed is 'cs:precise/mysql-33', while when
running the test the charm is 'local:precise/mysql-310' (in the .py file I
do specify 'd.add('mysql', charm='cs:precise/mysql-33')'). Is this normal?
Daniele
On Wed, Feb 5, 2014 at 8:05 PM, David Cheney
david.che...@canonical.comwrote:
You said earlier that you were using the local provider. Have you applied
the raring kernel update to this machine ? This is required if you want to
use LXC on Precise.
On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa
daniele.stro...@joyent.com wrote:
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 david.che...@canonical.com
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 jo...@ubuntu.comwrote:
On Tue, Feb 4, 2014 at 11:10 PM, David Cheney
david.che...@canonical.com 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
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
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 david.che...@canonical.comwrote: 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 jo...@ubuntu.com wrote: On Tue, Feb 4, 2014 at 11:10 PM, David Cheney david.che...@canonical.com 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 Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
You said earlier that you were using the local provider. Have you applied the raring kernel update to this machine ? This is required if you want to use LXC on Precise. On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa daniele.stro...@joyent.comwrote: 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 david.che...@canonical.comwrote: 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 jo...@ubuntu.com wrote: On Tue, Feb 4, 2014 at 11:10 PM, David Cheney david.che...@canonical.com 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 Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
I don't think this is related to the amount of memory provided, especially as Daniele is using the local provider. 2014-02-03 16:07:23 INFO juju.worker.uniter context.go:255 HOOK Unable to open /sys/kernel/security/apparmor/.replace - Permission denied 2014-02-03 16:07:23 INFO juju.worker.uniter context.go:255 HOOK apparmor_parser: Unable to replace /usr/sbin/mysqld. Permission denied; attempted to load a profile while confined? Looks like an apparmor issue to me. On Wed, Feb 5, 2014 at 8:04 AM, Daniele Stroppa daniele.stro...@joyent.comwrote: Mark, I tried again giving 2G and 4G to the local provider, but no luck. Daniele On Tue, Feb 4, 2014 at 8:13 PM, Mark Shuttleworth m...@ubuntu.com wrote: Hi Daniele, I think the question is whether you have enough memory - can you give it more with the local provider? Mark On 04/02/14 15:55, Daniele Stroppa wrote: Maarten, Curtis, I tried to deploy mysql on the local provider with as little as 256M of memory, but I still get the same error. Daniele On Tue, Feb 4, 2014 at 12:22 PM, Curtis Hovey-Canonical cur...@canonical.com wrote: On Tue, Feb 4, 2014 at 12:29 PM, Maarten Ectors maarten.ect...@canonical.com wrote: In the past I had an issue with the MySQL charm whereby it had some parameter set to 4GB and I did not have enough memory. I don't remember the exact parameter but it is in the /etc/mysql/my.cnf. By reducing it to a smaller number that fits. If this problem still exists then let me know and we will file a bug... The error is ambiguous, something went wrong after mysql installed. This does however match what we saw when mysql didn't get enough memory. When I create deploy mysql on azure and ec2, i do juju bootstrap --contraints mem=2G mysql For hp I give it 4G juju bootstrap --contraints mem=4G mysql -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju mailing list j...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
MySQL charm: hook failed: config-changed
Hi All, while running test for the Node.js charm I ran into an issue with the MySQL charm, see attached log. It looks like it's a permissions issue. I'm running on Ubuntu 12.04 with juju 1.16.4.1 and MySQL charm from cs:precise/mysql-32 Anyone has seen this before? Thanks, Daniele unit-mysql-0.log Description: Binary data -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
MySQL charm: hook failed: config-changed
Hi All, while running test for the Node.js charm I ran into an issue with the MySQL charm, see attached log. It looks like it's a permissions issue. I'm running on Ubuntu 12.04 with juju 1.16.4.1 and MySQL charm from cs:precise/mysql-32 Anyone has seen this before? Thanks, Daniele unit-mysql-0.log Description: Binary data -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
Danielle, I'm observing this behavior on my local provider, but its not exhibiting the same behavior in my cloud environments. I'm still debugging the issue as the mysql daemon starts on the host when run manually but not via the upstart script. I'll ping back as this unfolds. All the best, Charles On Mon, Feb 3, 2014 at 11:23 AM, Daniele Stroppa daniele.stro...@joyent.com wrote: Hi All, while running test for the Node.js charm I ran into an issue with the MySQL charm, see attached log. It looks like it's a permissions issue. I'm running on Ubuntu 12.04 with juju 1.16.4.1 and MySQL charm from cs:precise/mysql-32 Anyone has seen this before? Thanks, Daniele -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: MySQL charm: hook failed: config-changed
I'm using the local provider On Mon, Feb 3, 2014 at 6:15 PM, Marco Ceppi ma...@ceppi.net wrote: Which cloud were you running this against? On Feb 3, 2014 5:23 PM, Daniele Stroppa daniele.stro...@joyent.com wrote: Hi All, while running test for the Node.js charm I ran into an issue with the MySQL charm, see attached log. It looks like it's a permissions issue. I'm running on Ubuntu 12.04 with juju 1.16.4.1 and MySQL charm from cs:precise/mysql-32 Anyone has seen this before? Thanks, Daniele -- Juju mailing list j...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
