Public bug reported:
I have juju-local deployed on current xenial. This works fine right
after installation (except for bug 1534106), but after a fresh boot
"juju status" hangs. I have two failed units:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● juju-agent-martin-local.service loaded failed failed juju agent for machine-0
● juju-db-martin-local.service loaded failed failed juju state database
Unfortunately they don't do any error logging to the journal, they just exit
with 127:
$ sudo systemctl status -l juju-agent-martin-local.service
● juju-agent-martin-local.service - juju agent for machine-0
Loaded: loaded
(/var/lib/juju/init/juju-agent-martin-local/juju-agent-martin-local.service;
enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Do 2016-01-21 08:51:31 CET; 27min
ago
Main PID: 1017 (code=exited, status=127)
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Main
process exited, code=exited, status=127/n/a
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Unit
entered failed state.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Failed with
result 'exit-code'.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Service
hold-off time over, scheduling restart.
Jan 21 08:51:31 donald systemd[1]: Stopped juju agent for machine-0.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Start
request repeated too quickly.
Jan 21 08:51:31 donald systemd[1]: Failed to start juju agent for machine-0.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Unit
entered failed state.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Failed with
result 'start-limit'.
juju-db-martin-local.service repeatedly fails with exit code 1, but
otherwise it's a similar output.
They can be manually started after booting with sudo systemctl start
'juju-*' though, and then things work. So it looks like they are missing
some dependency?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: juju-core 1.25.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 21 09:16:05 2016
EcryptfsInUse: Yes
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1536522
Title:
juju-local: systemd units fail on boot if /home is not accessible
before logging in
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1536522/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
