Description of problem: fail2ban refuse to start when booting my computer, in syslog I can find: ERROR Could not start server. Maybe an old socket file is still present. Try to remove /var/run/fail2ban/fail2ban.sock. If you used fail2ban-client to start the server, adding the -x option will do it But the problem is that /var/run/fail2ban directory is missing. If I do: sudo mkdir /var/run/fail2ban sudo systemctl restart fail2ban.service fail2ban is happy and start but at the next reboot, the directory is missing again. I verified the installation with rpm -vV fail2ban and see that the /var/run/fail2ban is listed but flagged as missing.
Some pointers for Remco: you probably need similar %post part: https://bugs.mageia.org/attachment.cgi?id=2865&action=diff example of tmpfiles conf: http://svnweb.mageia.org/packages/cauldron/munin/current/SOURCES/munin.tmpfiles?revision=283661&view=markup More info on the topic: https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
CC: (none) => sander.lepik
Status: NEW => ASSIGNEDAssignee: bugsquad => remco
@Stéphane, thank you for your report. @Sander, thank you for the pointers. I've just submitted fail2ban-0.8.7.1-2, which I believe resolves this issue. Feel free to reopen this report if this problem persists.
Status: ASSIGNED => RESOLVEDHardware: i586 => AllResolution: (none) => FIXED
Hi, just after upgrading the package, fail2ban started succesfully (I didnt created the /var/run/fail2ban directory when the computer started the morning). but after restarting the computer, I had to mkdir /var/run/fail2ban to get fail2ban started again.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Hi Stéphane, sorry for having messed up the first time around. Please try again with the fail2ban-0.8.7.1-3 package. I hope this works for you as it does on my own machine.
I believe this is now fixed. Reopen in case you disagree.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED