[opensuse] 'systemctl start fail2ban.service' fails but process running with a different PID
Hello, I have just experienced this behavior on a fresh default installation of openSUSE 12.2. nemesis:/usr/local/etc # ps aux | grep fail2ban root 3353 0.1 0.3 265372 6768 ? Sl 08:58 0:00 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock root 3366 0.0 0.0 32432 852 pts/1 S+ 08:59 0:00 grep --color=auto fail2ban nemesis:/usr/local/etc # ps aux | grep fail2ban root 3353 0.0 0.3 265372 6768 ? Sl 08:58 0:00 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock root 3387 0.0 0.0 35688 852 pts/1 S+ 09:05 0:00 grep --color=auto fail2ban nemesis:/usr/local/etc # systemctl stop postfix.service nemesis:/usr/local/etc # ps aux | grep fail2ban root 3353 0.0 0.3 265372 6768 ? Sl 08:58 0:00 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock root 3391 0.0 0.0 21176 856 pts/1 S+ 09:05 0:00 grep --color=auto fail2ban nemesis:/usr/local/etc # nemesis:/usr/local/etc # kill 3353 nemesis:/usr/local/etc # ps aux | grep fail2ban root 3402 0.0 0.0 29036 852 pts/1 S+ 09:06 0:00 grep --color=auto fail2ban nemesis:/usr/local/etc # systemctl start fail2ban.service Job failed. See system journal and 'systemctl status' for details. nemesis:/usr/local/etc # systemctl status fail2ban.service fail2ban.service - LSB: Bans IPs with too many authentication failures Loaded: loaded (/etc/init.d/fail2ban) Active: failed (Result: exit-code) since Tue, 02 Oct 2012 09:06:40 -0400; 6s ago Process: 3059 ExecStop=/etc/init.d/fail2ban stop (code=exited, status=0/SUCCESS) Process: 3405 ExecStart=/etc/init.d/fail2ban start (code=exited, status=7/NOTRUNNING) CGroup: name=systemd:/system/fail2ban.service └ 3415 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock nemesis:/usr/local/etc # ps aux | grep fail2ban root 3415 0.4 0.4 264784 8776 ? Sl 09:06 0:00 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock root 3428 0.0 0.0 25728 852 pts/1 S+ 09:07 0:00 grep --color=auto fail2ban Weird. I wanted to ask the community if this is a common behavior before I submit a bug ticket. Thank you. Best Regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* General Mail <general@bombshellz.net> [10-02-12 09:09]:
/var/run/fail2ban/fail2ban.sock root 3428 0.0 0.0 25728 852 pts/1 S+ 09:07 0:00 grep --color=auto fail2ban
Weird. I wanted to ask the community if this is a common behavior before I submit a bug ticket. Thank you.
iianm, fail2ban is not starting because it thinks there is another instance, fail2ban.sock. Either delete the socket first or: fail2ban-client start -x fail2ban-client --help *many* **nux pgms have "--help" avilable -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/02/2012 03:17 PM, Patrick Shanahan wrote:
* General Mail <general@bombshellz.net> [10-02-12 09:09]:
/var/run/fail2ban/fail2ban.sock root 3428 0.0 0.0 25728 852 pts/1 S+ 09:07 0:00 grep --color=auto fail2ban
Weird. I wanted to ask the community if this is a common behavior before I submit a bug ticket. Thank you.
iianm, fail2ban is not starting because it thinks there is another instance, fail2ban.sock. Either delete the socket first or: fail2ban-client start -x
Nevertheless the init script should be able to take care of that by itself. If that is not the case I would say needs a ticket. Togan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
General Mail -
Patrick Shanahan -
Togan Muftuoglu