Am 16.05.2015 um 07:59 schrieb Andrei Borzenkov:
В 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?
You're right: Mai 14 07:23:14 linux-yb52 systemd-sysv-generator[678]: Overwriting existing symlink /run/systemd/generator.late/raw.service with real service Mai 14 07:23:14 linux-yb52 systemd[1]: Found dependency on YaST2-Second-Stage.service/start Mai 14 07:23:14 linux-yb52 systemd[1]: Found dependency on xinetd.service/start Mai 14 07:23:14 linux-yb52 systemd[1]: Breaking ordering cycle by deleting job network.target/start Mai 14 07:23:14 linux-yb52 systemd[1]: Job network.target/start deleted to break ordering cycle starting with xinetd.service/start Mai 14 07:23:14 linux-yb52 systemd[1]: Stopped Switch Root. Disabling YaST2-Second-Stage.service broke the cycle for me. Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org