[Bug 790557] New: Fail2ban fails to start during boot
https://bugzilla.novell.com/show_bug.cgi?id=790557 https://bugzilla.novell.com/show_bug.cgi?id=790557#c0 Summary: Fail2ban fails to start during boot Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: 64bit OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sault.don@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Fail2ban is enabled via 'systemctl enable fail2ban.service' and attempted to start but 'systemctl status fail2ban.service' says the service is failed. As my regular user, 'fail2ban-client status' says server is not running, but as root 'fail2ban-client status' says it is running. Reproducible: Always Steps to Reproduce: 1. Enable fail2ban via 'sudo systemctl enable fail2ban.service' 2. Restart PC 3. Check status of fail2ban with 'systemctl status fail2ban.service' 4. Check status of fail2ban as root with 'fail2ban-client status' 5. Start service via 'sudo systemctl start fail2ban.service' 6. Remove /var/run/fail2ban/fail2ban.{pid,sock} and start fail2ban service with 'systemctl start fail2ban.service' 7. Remove /var/run/fail2ban/fail2ban.{pid,sock} and restart PC Actual Results: 1. Enabling the service works and activates fail2ban for startup in runlevels 4 and 5 2. Restarting PC is fine... 3. Outputs: fail2ban.service - LSB: Bans IPs with too many authentication failures Loaded: loaded (/etc/init.d/fail2ban) Active: failed (Result: exit-code) since Tue, 20 Nov 2012 10:32:49 -0700; 3s ago Process: 22104 ExecStart=/etc/init.d/fail2ban start (code=exited, status=7/NOTRUNNING) CGroup: name=systemd:/system/fail2ban.service 4. As root, outputs (as regular user, server is not running!): Status |- Number of jail: 0 `- Jail list: 5. Fails to start service... 6. Fails to start service... 7. Fail2ban service starts randomly during boot! Expected Results: Fail2ban service should start every time during boot when enabled with systemctl. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c1
--- Comment #1 from Donovan Cameron
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c2
Jiaying ren
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.
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c
Jiaying ren
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c4
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c5
--- Comment #5 from Donovan Cameron
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c6
--- Comment #6 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c7
Donovan Cameron
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c8
--- Comment #8 from Johannes Weberhofer
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c9
--- Comment #9 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c10
--- Comment #10 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c11
Johannes Weberhofer
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c
Johannes Weberhofer
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c12
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c13
Christophe de Rivière
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c14
Sebastian Krahmer
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c15
--- Comment #15 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c16
--- Comment #16 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=790557
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com