Summary: | net-analyzer/fail2ban-0.8.3: stale socket not cleared, fails to start after unclean shutdown | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adam Shea <adshea> |
Component: | [OLD] Server | Assignee: | Gentoo Netmon project <netmon> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.fail2ban.org/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Adam Shea
2009-02-21 08:23:31 UTC
Still the same with 0.8.4. I did a strace with the fail2ban-client to see why it's taking so long before it finally fails starting, as it delays startup of the computer for about 30 seconds. It seems it is trying to connect on the stale socket, I counted 302 tries. Also I found that the message about the socket fail2ban-client finally gives at the end when it's called directly, isn't logged in the fail2ban log. Such message would be very useful there. I always have the same problem after I upgrade fail2ban. After awhile of snooping around I realize I just need to configure fail2ban to start even if a socket exists: In /etc/conf.d/fail2ban add -x to FAIL2BAN_OPTIONS 0.8.3 is no longer on tree But 0.8.4 is. Is there a fix for the issues in my previous comment? |