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
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
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
Syntax errors when installing juju-deployer
Hi All, I'm writing tests for the Node.js app charm using the Amulet framework. However, I'm running into some syntax errors when installing juju-deployer, see attached log. It happens both on Ubuntu 12.04 with Python 3.2 and on Mac OS X with Python 3.3. Has anyone come across the same issue? Cheers, Daniele vagrant@vagrant-ubuntu-precise-64:/vagrant/charms/precise/node-app$ ./bin/pip-3.2 install juju-deployer Downloading/unpacking juju-deployer Downloading juju-deployer-0.3.1.tar.gz (70Kb): 70Kb downloaded Running setup.py egg_info for package juju-deployer Requirement already satisfied (use --upgrade to upgrade): jujuclient=0.15 in ./lib/python3.2/site-packages/jujuclient-0.17.1-py3.2.egg (from juju-deployer) Requirement already satisfied (use --upgrade to upgrade): PyYAML==3.10 in ./lib/python3.2/site-packages (from juju-deployer) Requirement already satisfied (use --upgrade to upgrade): websocket-client in ./lib/python3.2/site-packages/websocket_client-0.12.0-py3.2.egg (from jujuclient=0.15-juju-deployer) Installing collected packages: juju-deployer Running setup.py install for juju-deployer File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/action/diff.py, line 154 print yaml_dump(diff) ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/cli.py, line 131 print Tool for declarative management of complex deployments. ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/config.py, line 45 except Exception, e: ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/env/base.py, line 123 except ErrorExit, e: ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/env/go.py, line 48 except socket.error, e: ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/operations.py, line 12 class ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/tests/test_config.py, line 24 [u'openstack-precise-ec2', ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/tests/test_pyenv.py, line 43 except UnitErrors, e: ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/tests/test_utils.py, line 103 self.addCleanup(os.chmod, self.playground, 0700) ^ SyntaxError: invalid token File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/utils.py, line 52 node = yaml.ScalarNode(tag=u'tag:yaml.org,2002:str', value=uni) ^ SyntaxError: invalid syntax File /vagrant/charms/precise/node-app/lib/python3.2/site-packages/deployer/vcs.py, line 31 except subprocess.CalledProcessError, e: ^ SyntaxError: invalid syntax Installing juju-deployer script to /vagrant/charms/precise/node-app/bin Successfully installed juju-deployer Cleaning up... vagrant@vagrant-ubuntu-precise-64:/vagrant/charms/precise/node-app$ -- 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-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
Re: Vagrant boxes with Juju now available
One more thing I noticed while working on a charm. After a debug-hooks session, I modified some files in my local charm repo (/vagrant/charms), destroyed the service that was deployed and re-deploy it from the local repo with modified files. However, the latest changes were not picked up and the charm was still using a previous version of the hooks. The only way I've found for juju to pick up the latest changes is to destroy the environment and bootstrap it again. It looks like juju caches the content of the /vagrant folder at bootstrap (just a wild guess). This happens using both the boxes with Juju built-in or a plain Ubuntu box. Daniele On Thu, Dec 5, 2013 at 11:33 PM, Antonio Rosales antonio.rosa...@canonical.com wrote: On Thu, Dec 5, 2013 at 2:14 PM, Daniele Stroppa daniele.stro...@joyent.com wrote: Thanks Antonio, using a 12.04 box fixed the issue, the shared folder /vagrant is accessible. Great to hear, and thanks again for the feedback and follow up. -Antonio Daniele On Thu, Dec 5, 2013 at 7:08 PM, Antonio Rosales antonio.rosa...@canonical.com wrote: On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa daniele.stro...@joyent.com wrote: Hi Jorge, I've tried the Vagrant boxes and they look great. However, I'm having a small issue. I've spin up a Saucy (amd64) box, boots up fine, I can access the GUI and 'juju status' shows the 'juju-gui' service deployed. If I try to deploy my charm from /vagrant (juju deploy --repository /vagrant/charms local:precise/node-app) it just gets stuck, nothing happens and I need to Ctrl-C to go back to the console. Same happens if I do a simple 'ls /vagrant'. (This works in a plain Ubuntu box with Juju installed). Talking with Ben you may be running into: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1239384 Thus the recommendation is to use a 12.04 vbox image with latest vagrant and current vbox. Let us know if this helps resolve the issue you are seeing, and thanks for the feedback. -thanks, Antonio Any suggestions? My Environment: Mac OS X 10.8.5 VirtualBox 4.2.18 Vagrant 1.3.3 Thanks, Daniele On Tue, Dec 3, 2013 at 6:04 PM, Jorge O. Castro jo...@ubuntu.com wrote: Hi everyone, Ben's been working on providing Vagrant images with Juju built in: http://blog.utlemming.org/2013/12/beta-cross-platform-juju-development.html This is particularly important for those of you on Windows or OSX we share the /vagrant directory, allowing you to quickly hack on your charm locally and deploy to running Ubuntu Cloud instances just as you would to a provider. (Except without the cost!) Please feel free to send feedback to this list! -- 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 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Vagrant boxes with Juju now available
Hi Jorge, I've tried the Vagrant boxes and they look great. However, I'm having a small issue. I've spin up a Saucy (amd64) box, boots up fine, I can access the GUI and 'juju status' shows the 'juju-gui' service deployed. If I try to deploy my charm from /vagrant (juju deploy --repository /vagrant/charms local:precise/node-app) it just gets stuck, nothing happens and I need to Ctrl-C to go back to the console. Same happens if I do a simple 'ls /vagrant'. (This works in a plain Ubuntu box with Juju installed). Any suggestions? My Environment: Mac OS X 10.8.5 VirtualBox 4.2.18 Vagrant 1.3.3 Thanks, Daniele On Tue, Dec 3, 2013 at 6:04 PM, Jorge O. Castro jo...@ubuntu.com wrote: Hi everyone, Ben's been working on providing Vagrant images with Juju built in: http://blog.utlemming.org/2013/12/beta-cross-platform-juju-development.html This is particularly important for those of you on Windows or OSX we share the /vagrant directory, allowing you to quickly hack on your charm locally and deploy to running Ubuntu Cloud instances just as you would to a provider. (Except without the cost!) Please feel free to send feedback to this list! -- 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: Vagrant boxes with Juju now available
Thanks Antonio, using a 12.04 box fixed the issue, the shared folder /vagrant is accessible. Daniele On Thu, Dec 5, 2013 at 7:08 PM, Antonio Rosales antonio.rosa...@canonical.com wrote: On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa daniele.stro...@joyent.com wrote: Hi Jorge, I've tried the Vagrant boxes and they look great. However, I'm having a small issue. I've spin up a Saucy (amd64) box, boots up fine, I can access the GUI and 'juju status' shows the 'juju-gui' service deployed. If I try to deploy my charm from /vagrant (juju deploy --repository /vagrant/charms local:precise/node-app) it just gets stuck, nothing happens and I need to Ctrl-C to go back to the console. Same happens if I do a simple 'ls /vagrant'. (This works in a plain Ubuntu box with Juju installed). Talking with Ben you may be running into: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1239384 Thus the recommendation is to use a 12.04 vbox image with latest vagrant and current vbox. Let us know if this helps resolve the issue you are seeing, and thanks for the feedback. -thanks, Antonio Any suggestions? My Environment: Mac OS X 10.8.5 VirtualBox 4.2.18 Vagrant 1.3.3 Thanks, Daniele On Tue, Dec 3, 2013 at 6:04 PM, Jorge O. Castro jo...@ubuntu.com wrote: Hi everyone, Ben's been working on providing Vagrant images with Juju built in: http://blog.utlemming.org/2013/12/beta-cross-platform-juju-development.html This is particularly important for those of you on Windows or OSX we share the /vagrant directory, allowing you to quickly hack on your charm locally and deploy to running Ubuntu Cloud instances just as you would to a provider. (Except without the cost!) Please feel free to send feedback to this list! -- 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 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
