I dug in logs more and find these - is this a packaging bug made visible by systemd-217 or something else? Machine A) .. systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. ... systemd[1]: Cannot add dependency job for unit cups.path, ignoring: Unit cups.path failed to load: No such file or directory. ... systemd[1]: Cannot add dependency job for unit rpc-idmapd.service, ignoring: Unit rpc-idmapd.service failed to load: No such file or directory. ... systemd[1]: Found ordering cycle on basic.target/start ... systemd[1]: Breaking ordering cycle by deleting job systemd-update-utmp.service/start ... systemd[1]: Job systemd-update-utmp.service/start deleted to break ordering cycle starting with basic.target/start ... systemd[1]: Found ordering cycle on basic.target/start ... systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start ... systemd[1]: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with basic.target/start Machine B (this one failed to start mysqld) .. systemd[1]: Found dependency on NetworkManager-wait-online.service/start .. systemd[1]: Found dependency on basic.target/start .. systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start No.. systemd[1]: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with basic.target/start .. systemd[1]: Stopped Switch Root. ... systemd[1]: Cannot add dependency job for unit rpc-idmapd.service, ignoring: Unit rpc-idmapd.service failed to load: No such file or directory. ... systemd[1]: Found ordering cycle on basic.target/start ... systemd[1]: Found dependency on sysinit.target/start ...systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start ...systemd[1]: Found dependency on systemd-journal-flush.service/start ... systemd[1]: Found dependency on remote-fs.target/start ...systemd[1]: Found dependency on mnt-Name-mirror.mount/start ...systemd[1]: Found dependency on network.target/start On 11/02/2014 08:15 PM, Genes Lists wrote:
On 11/02/2014 08:12 PM, Genes Lists wrote:
On 11/02/2014 08:07 PM, Armin K. wrote:
systemctl status systemd-tmpfiles-setup
Thanks - here's what I get on machine A (the mysql server):
A couple more machines: This one is mail server:
# systemctl status systemd-tmpfiles-setup
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since Sun 2014-11-02 15:49:59 EST; 4h 23min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 426 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS) Main PID: 426 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-tmpfiles-setup.service
And this is a firewall .. .similar issues to one of the other machines:
systemctl status systemd-tmpfiles-setup
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: inactive (dead) Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8)
... systemd[1]: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with basic.target/start