| 2023-01-12 13:38:51 |
George Shuklin |
description |
I found that pure-baremetal installation (no lxc) on Debian creates circular systemd dependency.
Symptoms:
After reboot one of the following entries in journal:
sysinit.target: Found ordering cycle on local-fs.target/start
sysinit.target: Found dependency on var-www-repo.mount/start
sysinit.target: Found dependency on network-online.target/start
sysinit.target: Found dependency on network.target/start
sysinit.target: Found dependency on openvswitch-switch.service/start
sysinit.target: Found dependency on sysinit.target/start
sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start
openvswitch-switch.service: Found ordering cycle on basic.target/start
openvswitch-switch.service: Found dependency on sockets.target/start
openvswitch-switch.service: Found dependency on mariadbcheck.socket/start
openvswitch-switch.service: Found dependency on network.target/start
openvswitch-switch.service: Found dependency on openvswitch-switch.service/start
openvswitch-switch.service: Job sockets.target/start deleted to break ordering cycle starting with openvswitch-switch.service/start
network-online.target: Job networking.service/start deleted to break ordering cycle starting with network-online.target/start
openvswitch-switch.service: Found ordering cycle on ovs-vswitchd.service/start
openvswitch-switch.service: Found dependency on ovsdb-server.service/start
openvswitch-switch.service: Found dependency on local-fs.target/start
openvswitch-switch.service: Found dependency on var-www-repo.mount/start
openvswitch-switch.service: Found dependency on network-online.target/start
openvswitch-switch.service: Found dependency on network.target/start
openvswitch-switch.service: Found dependency on openvswitch-switch.service/start
Due to circular nature systemd can't identify root source of the problem, and bans random unit (including networking.service, which renders server non-responsive or openvswitch-switch.service which breaks all neutron networking).
After extensive bisection I identify units causing circular dependencies:
* var-www-repo.mount
* mariadbcheck.socket
* mariadbcheck@.service
All of them has dependency "After = network-online.target" or "After=network.target". Removal of that dependency do not affect functionality (f.e. mariadbcheck.socket has reverse dependency on sockets.target), and it's removal solves circular dependency problem.
Proposed fix:
* Remove "After=network.target" from mariadbcheck.socket
* Remove "After = network-online.target" from var-www-repo.mount and mariadbcheck@.service |
I found that pure-baremetal installation (no lxc) on Debian creates circular systemd dependency.
Symptoms:
After reboot one of the following entries in journal:
sysinit.target: Found ordering cycle on local-fs.target/start
sysinit.target: Found dependency on var-www-repo.mount/start
sysinit.target: Found dependency on network-online.target/start
sysinit.target: Found dependency on network.target/start
sysinit.target: Found dependency on openvswitch-switch.service/start
sysinit.target: Found dependency on sysinit.target/start
sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start
openvswitch-switch.service: Found ordering cycle on basic.target/start
openvswitch-switch.service: Found dependency on sockets.target/start
openvswitch-switch.service: Found dependency on mariadbcheck.socket/start
openvswitch-switch.service: Found dependency on network.target/start
openvswitch-switch.service: Found dependency on openvswitch-switch.service/start
openvswitch-switch.service: Job sockets.target/start deleted to break ordering cycle starting with openvswitch-switch.service/start
network-online.target: Job networking.service/start deleted to break ordering cycle starting with network-online.target/start
openvswitch-switch.service: Found ordering cycle on ovs-vswitchd.service/start
openvswitch-switch.service: Found dependency on ovsdb-server.service/start
openvswitch-switch.service: Found dependency on local-fs.target/start
openvswitch-switch.service: Found dependency on var-www-repo.mount/start
openvswitch-switch.service: Found dependency on network-online.target/start
openvswitch-switch.service: Found dependency on network.target/start
openvswitch-switch.service: Found dependency on openvswitch-switch.service/start
Due to circular nature systemd can't identify root source of the problem, and bans random unit (including networking.service, which renders server non-responsive or openvswitch-switch.service which breaks all neutron networking).
After extensive bisection I've identified units causing circular dependencies:
* var-www-repo.mount
* mariadbcheck.socket
* mariadbcheck@.service
All of them has dependency "After = network-online.target" or "After=network.target". Removal of that dependency do not affect functionality (f.e. mariadbcheck.socket has reverse dependency on sockets.target), and it's removal solves circular dependency problem.
Proposed fix:
* Remove "After=network.target" from mariadbcheck.socket
* Remove "After = network-online.target" from var-www-repo.mount and mariadbcheck@.service |
|
