mysql charm blows up on out of memory error
Bug #1294334 reported by
Brian Wawok
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql (Juju Charms Collection) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I was following the juju tutorial for a mysql / wordpress relationship.
I am deploying to a local environment on a machine with 24GB of ram.
Mysql would not start, the start hook exploded. Did some troubleshooting, and saw my innodb_
I have no idea how this param is set, but assume it is set to 75% of available ram or something.. that is fine on a cloud VM, but pretty bad on a local instance. Maybe cap it at 4GB unless a config is passed in?
Changed in mysql (Juju Charms Collection): | |
status: | Triaged → Confirmed |
importance: | High → Undecided |
To post a comment you must log in.
The exact error I saw in my juju log was:
2014-03-18 19:32:27 INFO juju.worker.uniter uniter.go:348 running "start" hook 2014-03-18 19:32:27 INFO juju.worker.uniter context.go:255 HOOK mysql stop/waiting 2014-03-18 19:32:30 INFO juju.worker.uniter context.go:255 HOOK start: Job failed to start 2014-03-18 19:32:30 ERROR juju.worker.uniter uniter.go:350 hook failed: exit status 1