local provider "machine0" agent fails to start up on wily if "/var/lib" is not on the "/" partition.

[Martin Hilton]

For historical reasons my /var/lib directory is in its own partition. This seems to be causing systemd to fail to be able to start the agent and db jobs.

Nov 09 18:18:22 goldfish systemd[1]: juju-agent-mhilton-local.service: Cannot add dependency job, ignoring: Unit juju-agent-mhilton-local.service failed to load: No such file or direct
Nov 09 18:18:22 goldfish systemd[1]: juju-db-mhilton-local.service: Cannot add dependency job, ignoring: Unit juju-db-mhilton-local.service failed to load: No such file or directory.

Crucially this dependency tree is generated before /var/lib is mounted. I'm not entirely sure that having /var/lib in its own partition is completely supported, but I'm pretty sure having /var in its own partition is and I believe you'd get the same problem with that too.

[Cheryl Jennings (cherylj)]

I suspect that this is because juju uses systemctl link to link the service files, rather than copying them over to /etc/systemd/system.

You can manually copy the files over, and hopefully that will work around this error.

[Cheryl Jennings (cherylj)]

... forgot to mention that the service files that are linked reside in /var/lib/juju/init/

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.