Jujud rewrites /etc/init/juju-db.conf constantly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Tim Penhey | ||
1.20 |
Fix Released
|
High
|
Tim Penhey |
Bug Description
Have noticed constant restarts of mongodb in syslog. It appears that jujud is touching /etc/init/
type=PATH msg=audit(
type=SYSCALL msg=audit(
type=CWD msg=audit(
type=PATH msg=audit(
type=SYSCALL msg=audit(
type=CWD msg=audit(
type=PATH msg=audit(
type=SYSCALL msg=audit(
type=CWD msg=audit(
type=PATH msg=audit(
(this is with sudo auditctl -w /etc/init/
What caused me to be interested in this is that I tried to change the juju-db.conf and my changes were immediately overwritten by something. It appears that something is jujud itself.
How can I stop jujud from overwriting my /etc/init/
tags: | added: mongodb performance |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
assignee: | nobody → Tim Penhey (thumper) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
jujud is crashing and restarting. Every time it restarts it does:
2014-07-29 18:08:46 INFO juju.mongo mongo.go:169 Ensuring mongo server is running; data directory /var/lib/juju; port 37017 Dpkg::Options: :=--force- confold --option= Dpkg::options: :=--force- unsafe- io --assume-yes --quiet install juju-mongodb] localhost: 17070/" : websocket.Dial wss://localhost :17070/ : dial tcp 127.0.0.1:17070: connection refused localhost: 17070/" juju/bin/ mongod --version: "db version v2.4.9\nTue Jul 29 18:08:47.314 git version: nogitversion\n" 0.1:37017" ]; entity "machine-0"
2014-07-29 18:08:46 INFO juju.mongo mongo.go:317 installing juju-mongodb
2014-07-29 18:08:46 INFO juju.utils.apt apt.go:128 Running: [apt-get --option=
2014-07-29 18:08:46 INFO juju.state.api apiclient.go:250 error dialing "wss://
2014-07-29 18:08:46 ERROR juju.worker runner.go:218 exited "api": unable to connect to "wss://
2014-07-29 18:08:46 INFO juju.worker runner.go:252 restarting "api" in 3s
2014-07-29 18:08:47 DEBUG juju.mongo mongo.go:260 using mongod: /usr/lib/
2014-07-29 18:08:47 INFO juju.state open.go:47 opening state, mongo addresses: ["127.0.
2014-07-29 18:08:47 DEBUG juju.state open.go:52 dialing mongo
2014-07-29 18:08:47 DEBUG juju.mongo open.go:87 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused
2014-07-29 18:08:47 DEBUG juju.mongo open.go:87 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused
2014-07-29 18:08:48 INFO juju.mongo open.go:95 dialled mongo successfully
I thought that might be rewriting the Upstart juju-db.conf but it doesn't seem that it should:
sudo apt-get --option= Dpkg::Options: :=--force- confold --option= Dpkg::options: :=--force- unsafe- io --assume-yes --quiet install juju-mongodb
Reading package lists...
Building dependency tree...
Reading state information...
juju-mongodb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
In other words, apt doesn't reinstall it if it's there already.