Mga5 beta 1 dual dvd build 2 with default 64bit installation. DATE: Mon Oct 27 21:53:54 CET 2014 Shorewall fails to start, shorewall6 is ok. The journal (attached) shows systemd[1]: Job shorewall.service/start deleted to break ordering cycle starting with mandi.service/start. Not noticed i586 install from the same dual dvd. Reproducible: Steps to Reproduce:
Whiteboard: (none) => 5beta1CC: (none) => ennael1
Created attachment 5549 [details] journal-mga5dual32b2.txt
Oops wrong log.
Regrettably I didn't save the 64bit log before moving on. Performed a 64bit installation from classic dvd and shorewall is ok but performed another 64bit installation from the dualdvd and although the error has changed, shorewall again failed to start.. Another app is currently holding xtables lock. Perhaps you want to use -w option. Error:Cannot to create Mangle chain fooX1373 Unit shorewall.service entered failed state
Created attachment 5550 [details] journal-5b1dual64b2.txt Journal from 2nd dual dvd 64bit install.
Attachment 5549 is obsolete: 0 => 1
Ironically on a 32bit kde install from i586 classic dvd.. systemd: Found ordering cycle on network-up.service/start systemd: Breaking ordering cycle by deleting job mandi.service/start systemd:Job mandi.service/start deleted to break ordering cycle starting with network-up.service/start
Oct 28 16:21:35 localhost shorewall[1287]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? Oct 28 16:21:36 localhost shorewall6[1288]: Compiling /usr/share/shorewall6/action.Reject for chain Reject... Oct 28 16:21:36 localhost shorewall6[1288]: Creating ip6tables-restore input... Oct 28 16:21:36 localhost shorewall6[1288]: Shorewall configuration compiled to /var/lib/shorewall6/.start Oct 28 16:21:37 localhost shorewall[1287]: ERROR: Cannot Create Mangle chain fooX1373 Oct 28 16:21:37 localhost logger[1698]: ERROR:Shorewall start failed Oct 28 16:21:37 localhost systemd[1]: shorewall.service: main process exited, code=exited, status=255/n/a Oct 28 16:21:37 localhost systemd[1]: Failed to start Shorewall IPv4 firewall. Oct 28 16:21:37 localhost systemd[1]: Unit shorewall.service entered failed state.
CC: (none) => alien, cooker, lmenut, luigiwalser, mageia, mageia, n54, olav, pterjan, thierry.vignaud, tmbKeywords: (none) => Triaged
(In reply to claire robinson from comment #5) > Ironically on a 32bit kde install from i586 classic dvd.. > > systemd: Found ordering cycle on network-up.service/start > systemd: Breaking ordering cycle by deleting job mandi.service/start > systemd:Job mandi.service/start deleted to break ordering cycle starting > with network-up.service/start same with 5beta2 dual iso 32bits XFCE install so shorewall service is inactive/dead
CC: (none) => marja11Whiteboard: 5beta1 => 5beta2Summary: 5beta1: Shorewall not started - systemd[1]: Job shorewall.service/start deleted to break ordering cycle starting with mandi.service/start. => 5beta2: Shorewall not started - systemd[1]: Job shorewall.service/start deleted to break ordering cycle starting with mandi.service/start.
I have similar problem on the same beta 1 x86_64 version. pro 17 19:52:06 server2 systemd[1]: Found ordering cycle on network.target/start pro 17 19:52:06 server2 systemd[1]: Breaking ordering cycle by deleting job network-up.service/start pro 17 19:52:06 server2 systemd[1]: Job network-up.service/start deleted to break ordering cycle starting with network.target/start Consequently system does not wait to start network (network-up service) and some network daemons (radvd, dhcp, dhcpd6) fails. How can I find reason of cycle break?
CC: (none) => waclaw66
I find the way to debug systemd - kernel command: systemd.log_level=debug Results are interrenting... pro 17 20:49:48 server2 systemd[1]: Trying to enqueue job graphical.target/start/isolate pro 17 20:49:48 server2 systemd[1]: Found ordering cycle on network.target/start pro 17 20:49:48 server2 systemd[1]: Found dependency on network-up.service/start pro 17 20:49:48 server2 systemd[1]: Found dependency on mandi.service/start pro 17 20:49:48 server2 systemd[1]: Found dependency on shorewall.service/start pro 17 20:49:48 server2 systemd[1]: Found dependency on network.target/start pro 17 20:49:48 server2 systemd[1]: Breaking ordering cycle by deleting job network-up.service/start pro 17 20:49:48 server2 systemd[1]: Job network-up.service/start deleted to break ordering cycle starting with network.target/start How can I fix it?
@coling: how to find cyclic dependencies for systemd?
Is shorewall-ipv6 installed? Nothing requires shorewall-ipv6, but in my tests shorewall service does not start without shorewall-ipv6 pkg.
CC: (none) => loginov_alex
Created attachment 5809 [details] shorewall.txt Valid after install from 5beta2 livedvd gnome 32 (so probably all). Shorewall fails, shorewall6 starts, although there is no ipv6 connection. Attaching.. # journalctl -b | grep -i shorewall > /home/user/shorewall.txt
Blocks: (none) => 14069
Hardware: x86_64 => All
Priority: Normal => release_blocker
Assignee: bugsquad => mageia
Target Milestone: --- => Mageia 5
Mageia5 beta3 live dvd 32bit kde : in boot.log : "Ordering cycle found, skipping Shorewall IPv4 firewall" and shorewall don't start.
CC: (none) => marcounet
OK, so writing a native systemd unit for mandi seemed to solve this OK. I also wrote one for the virtualbox guest addons as this was all in the same loop for me. More native units = finer grained control. I'll update both packages shortly.
commit 2b9752e8b64e8e3a556e0b2fc78f122578a5c9e1 Author: Colin Guthrie <colin@...> Date: Wed Feb 25 10:56:07 2015 +0000 Replace init script with systemd unit (mga#14401) --- Commit Link: http://gitweb.mageia.org/software/mandi/commit/?id=2b9752e8b64e8e3a556e0b2fc78f122578a5c9e1
Should be fixed in latest mandi and virtualbox packages once they hit the mirrors.
Thanks Col. We should start testing RC isos before long, so can test it then.
Fixed in Mageia 5 RC - round 1.
Status: NEW => RESOLVEDCC: (none) => remiResolution: (none) => FIXED
Fixed with the new mandi !