It may be easier to tear down and re-deploy. In that case:
$ juju destroy-service mysql
(monitor juju status for the service to be removed)
$ juju deploy mysql
$ juju set mysql dataset-size='256M'
At that point, mysql should install successfully.
--
Adam Israel
On January 29, 2015 at 12:01:09 P
Hi Adam,
Thanks for your reply, I treid the commands you sent me now I am getting
this:
unit-mysql-0: 2015-01-29 16:58:13 INFO start stop: Unknown instance:
unit-mysql-0: 2015-01-29 16:58:15 INFO start start: Job failed to start
unit-mysql-0: 2015-01-29 16:58:15 ERROR juju.worker.uniter uniter.go
Hi Saurabh,
That’s a known issue with the Mysql charm, under the local provider (documented
under Caveats in the README).
To fix the issue once the mysql charm is in an error state:
$ juju set mysql dataset-size='256M'
$ juju resolved mysql/0 —retry
--
Adam Israel
On January 29, 2015 at 11:35
Hi,
I was deploying mysql on my local juju environment but it is failing at
config changed hook.
At first I thought it might be some error so I deployed it 3 times and
it failed to start all the three times.
Any pointer on this will be helpful.
here is the log snippet:
==
