[Pkg-systemd-maintainers] Bug#734951: systemd: somehow starts LSB stuff in the wrong order

[Uoti Urpala]

Christoph Anton Mitterer wrote:
> Now since I switched to systemd, it tries to start fail2ban before iptables-persistent,
> thus the rules are missing and thus starting fail2ban fails.

Is there any reason to believe that there actually is an issue with
"wrong order"? I don't see any in the given log files, and assume this
is false.

Note that the log contains a warning about an ordering cycle, which
might cause problems (though I don't know why they would be specific to
fail2ban). That cycle is caused by setserial, which has a bad
"chkconfig:" header in its init script (which Debian-specific tools
probably don't parse, but which more cross-distro systemd code does).
Try removing setserial and see if that has any effect.

My guess is that there is some event which causes fail2ban.service to be
stopped after the job has been queued but before it actually starts, but
the log does not contain enough detail to tell what this might be. Try
booting with "systemd.log_level=debug" on kernel command line and check
the "journalctl -b" output from that.