В 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?
a) read the unit files mentioned in the message (that indeed needs a bit a improvement) b) use systemd-analyze plot/dot to see a dependency graph.
In the firsr case..The Yast-Second-stage service (that shouldn't even be enabled after the installation was complete, but for some reason is) Wants to start Before network.service (wicked) but AFTER xinetd which must be started after network..
The second case I do not know, as I do not have XEN installed. .
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org