On Sat, May 16, Andrei Borzenkov wrote:
В Fri, 15 May 2015 11:44:26 -0300 Cristian Rodríguez <crrodriguez@opensuse.org> пишет:
On Fri, May 15, 2015 at 8:12 AM, Olaf Hering <olaf@aepfle.de> wrote:
How do I find how what is causing these cycles?
root@optiplex:~ # journalctl -b | grep delete Mai 15 13:00:17 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with wicked.service/start Mai 15 13:00:17 optiplex systemd[1]: Job xenstored_ro.socket/start deleted to break ordering cycle starting with sockets.target/start Mai 15 13:00:17 optiplex systemd[1]: Job xenstored.socket/start deleted to break ordering cycle starting with sockets.target/start
There is currently no tool to inmediately analyze this, you have to
systemd should actually print the whole dependency chain before this message and also tell on which unit it hit the loop. Was it not the case here?
Yes, it shows this: root@optiplex:~ # journalctl -b | grep -B20 dele Mai 20 11:31:25 optiplex systemd-journal[158]: Journal stopped Mai 20 11:31:30 optiplex systemd-journal[477]: Runtime journal is using 8.0M (max allowed 394.3M, trying to leave 591.5M free of 3.8G available → current limit 394.3M). Mai 20 11:31:30 optiplex systemd-journal[477]: Permanent journal is using 412.7M (max allowed 2.9G, trying to leave 4.0G free of 20.2G available → current limit 2.9G). Mai 20 11:31:32 optiplex systemd-journal[477]: Time spent on flushing to /var is 1.786427s for 856 entries. Mai 20 11:31:32 optiplex systemd-journald[158]: Received SIGTERM from PID 1 (systemd). Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/rpmconfigcheck.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/after.local.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/local.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/raw.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/cifs.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/ebtables.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/xfs.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/esound.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/pppoe.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/halt.local.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/nfs.service with real service Mai 20 11:31:32 optiplex systemd-sysv-generator[440]: Overwriting existing symlink /run/systemd/generator.late/nfsserver.service with real service Mai 20 11:31:32 optiplex systemd[1]: Found dependency on NetworkManager-wait-online.service/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on NetworkManager.service/verify-active Mai 20 11:31:32 optiplex systemd[1]: Found dependency on YaST2-Second-Stage.service/start Mai 20 11:31:32 optiplex systemd[1]: Breaking ordering cycle by deleting job xinetd.service/start Mai 20 11:31:32 optiplex systemd[1]: Job xinetd.service/start deleted to break ordering cycle starting with YaST2-Second-Stage.service/start Mai 20 11:31:32 optiplex systemd[1]: Found ordering cycle on xenstored_ro.socket/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on proc-xen.mount/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on xen-dom0-modules.service/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on basic.target/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on sockets.target/start Mai 20 11:31:32 optiplex systemd[1]: Found dependency on xenstored_ro.socket/start Mai 20 11:31:32 optiplex systemd[1]: Breaking ordering cycle by deleting job proc-xen.mount/start Mai 20 11:31:32 optiplex systemd[1]: Job proc-xen.mount/start deleted to break ordering cycle starting with xenstored_ro.socket/start So what is wrong with xenstored_ro.socket? Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org