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
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
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
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
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
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
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
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
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
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
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,
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
12 matches
Mail list logo