https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c3
Donovan Cameron
Donovan,thank you for your report.Did you start fail2ban manually?Please try to start it manually,inspect if fail2ban works okay.So we can decide whether it's a systemd bug or not.
If I start manually with 'sudo systemctl start fail2ban.service' it fails. So I restart the PC to see if systemd can start it. It fails. What's strange is that at this point, as root (su -), 'fail2ban-client status' says it is running but 'systemctl status fail2ban.service' says failed. So then I remove the two files /var/run/fail2ban/fail2ban.{pid,socket}. I restart after removing those, and systemd starts fail2ban successfully and seems to start successfully in subsequent reboots. (Randomly, it will fail to start on startup!) If fail2ban is running successfully via systemd and I stop if manually with 'systemctl stop fail2ban.service' it stops, but I can't start it manually again until I remove those two files earlier and restart. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.