This fails to install:
Setting up ldirectord (1:4.2.0-1ubuntu1) ...
Job for ldirectord.service failed because the control process exited with error code.
See "systemctl status ldirectord.service" and "journalctl -xe" for details.
invoke-rc.d: initscript ldirectord, action "start" failed.
● ldirectord.service - Monitor and administer real servers in a LVS cluster of load balanced virtual servers
Loaded: loaded (/lib/systemd/system/ldirectord.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-05-08 12:20:10 UTC; 42ms ago
Docs: man:ldirectord(8)
Process: 779 ExecStart=/usr/sbin/ldirectord start (code=exited, status=0/SUCCESS)
Process: 783 ExecStartPost=/usr/bin/touch /var/lock/subsys/ldirectord (code=exited, status=1/FAILURE)
Process: 785 ExecStopPost=/bin/rm -f /var/lock/subsys/ldirectord (code=exited, status=0/SUCCESS)
Main PID: 781
Tasks: 1 (limit: 4915)
Memory: 14.1M
CGroup: /system.slice/ldirectord.service
└─781 /usr/bin/perl -w /usr/sbin/ldirectord start
May 08 12:18:39 autopkgtest-lxd-einqza systemd[1]: Starting Monitor and administer real servers in a LVS cluster of load balanced virtual servers...
May 08 12:18:39 autopkgtest-lxd-einqza systemd[1]: ldirectord.service: Supervising process 781 which is not our child. We'll most likely not notice when it exits.
May 08 12:18:40 autopkgtest-lxd-einqza touch[783]: /usr/bin/touch: cannot touch '/var/lock/subsys/ldirectord': No such file or directory
May 08 12:18:40 autopkgtest-lxd-einqza systemd[1]: ldirectord.service: Control process exited, code=exited, status=1/FAILURE
May 08 12:20:10 autopkgtest-lxd-einqza systemd[1]: ldirectord.service: State 'stop-post' timed out. Terminating.
May 08 12:20:10 autopkgtest-lxd-einqza systemd[1]: ldirectord.service: Failed with result 'exit-code'.
May 08 12:20:10 autopkgtest-lxd-einqza systemd[1]: Failed to start Monitor and administer real servers in a LVS cluster of load balanced virtual servers.
Of particular interest might be this line:
touch[783]: /usr/bin/touch: cannot touch '/var/lock/subsys/ldirectord': No such file or directory
This runs in LXD, maybe a pathing or apparmor issue?
I tried the same on a real armhf device and it works right away.
(Thanks waveform to provide armhf raspi)
In autopkgtest like /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- disco-ci- train-ppa- service- 3717/disco/ armhf/r/ resource- agents/ 20190508_ 124516_ 2b20c@/ log.gz /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- disco-ci- train-ppa- service- 3717/disco/ armhf/r/ resource- agents/ 20190507_ 202519_ be056@/ log.gz /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- disco-ci- train-ppa- service- 3717/disco/ armhf/r/ resource- agents/ 20190508_ 083654_ 2b20c@/ log.gz
https:/
https:/
https:/
This fails to install: system/ ldirectord. service; disabled; vendor preset: enabled) /usr/sbin/ ldirectord start (code=exited, status=0/SUCCESS) /usr/bin/ touch /var/lock/ subsys/ ldirectord (code=exited, status=1/FAILURE) /bin/rm -f /var/lock/ subsys/ ldirectord (code=exited, status=0/SUCCESS) slice/ldirector d.service ldirectord start
Setting up ldirectord (1:4.2.0-1ubuntu1) ...
Job for ldirectord.service failed because the control process exited with error code.
See "systemctl status ldirectord.service" and "journalctl -xe" for details.
invoke-rc.d: initscript ldirectord, action "start" failed.
● ldirectord.service - Monitor and administer real servers in a LVS cluster of load balanced virtual servers
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Wed 2019-05-08 12:20:10 UTC; 42ms ago
Docs: man:ldirectord(8)
Process: 779 ExecStart=
Process: 783 ExecStartPost=
Process: 785 ExecStopPost=
Main PID: 781
Tasks: 1 (limit: 4915)
Memory: 14.1M
CGroup: /system.
└─781 /usr/bin/perl -w /usr/sbin/
May 08 12:18:39 autopkgtest- lxd-einqza systemd[1]: Starting Monitor and administer real servers in a LVS cluster of load balanced virtual servers... lxd-einqza systemd[1]: ldirectord.service: Supervising process 781 which is not our child. We'll most likely not notice when it exits. lxd-einqza touch[783]: /usr/bin/touch: cannot touch '/var/lock/ subsys/ ldirectord' : No such file or directory lxd-einqza systemd[1]: ldirectord.service: Control process exited, code=exited, status=1/FAILURE lxd-einqza systemd[1]: ldirectord.service: State 'stop-post' timed out. Terminating. lxd-einqza systemd[1]: ldirectord.service: Failed with result 'exit-code'. lxd-einqza systemd[1]: Failed to start Monitor and administer real servers in a LVS cluster of load balanced virtual servers.
May 08 12:18:39 autopkgtest-
May 08 12:18:40 autopkgtest-
May 08 12:18:40 autopkgtest-
May 08 12:20:10 autopkgtest-
May 08 12:20:10 autopkgtest-
May 08 12:20:10 autopkgtest-
Of particular interest might be this line: subsys/ ldirectord' : No such file or directory
touch[783]: /usr/bin/touch: cannot touch '/var/lock/
This runs in LXD, maybe a pathing or apparmor issue?
I tried the same on a real armhf device and it works right away.
(Thanks waveform to provide armhf raspi)