On 07/09/13 15:48, sguazt wrote: > > > > On Tue, Jul 9, 2013 at 8:51 AM, Cristian Sava <cs...@central.ucv.ro > <mailto:cs...@central.ucv.ro>> wrote: > > On Tue, 2013-07-09 at 09:48 +0300, Cristian Sava wrote: > > On installs where iface reported by "route" command is not the same with > > ifcfg-iface (pxpy instead of enpxsy or ethx) fail2ban will not start. > > Does not matter if biosdevname=0 or net.ifnames=0 on the kernel line. > > Tested this on real hardware and on VirualBox too. > > > > >From /var/log/messages: > > fail2ban-client[2804]: ERROR Directory /var/run/fail2ban exists but > not accessible for writing > > > > Fail2ban is ok on any other install. > I forgot to add that is about F19 installs. > > C.Sava > > > Hello, > > Similar problem here on a F19 x86_64. > > $ systemctl status fail2ban > > fail2ban.service - Fail2ban Service > Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled) > Active: failed (Result: start-limit) since Tue 2013-07-09 08:59:40 CEST; > 45min ago > Process: 1024 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, > status=255) > > Jul 09 08:59:40 wildcat systemd[1]: fail2ban.service: control process exited, > code=exited status=255 > Jul 09 08:59:40 wildcat systemd[1]: Failed to start Fail2ban Service. > Jul 09 08:59:40 wildcat systemd[1]: Unit fail2ban.service entered failed > state. > Jul 09 08:59:40 wildcat systemd[1]: fail2ban.service holdoff time over, > scheduling restart. > Jul 09 08:59:40 wildcat systemd[1]: Stopping Fail2ban Service... > Jul 09 08:59:40 wildcat systemd[1]: Starting Fail2ban Service... > Jul 09 08:59:40 wildcat systemd[1]: fail2ban.service start request repeated > too quickly, refusing to start. > Jul 09 08:59:40 wildcat systemd[1]: Failed to start Fail2ban Service. > Jul 09 08:59:40 wildcat systemd[1]: Unit fail2ban.service entered failed > state. > > $ less /var/log/messages > Jul 9 08:59:39 localhost fail2ban-client[1024]: ERROR Directory > /var/run/fail2ban exists but not accessible for writing > Jul 9 08:59:40 localhost systemd[1]: fail2ban.service: control process > exited, code=exited status=255 > Jul 9 08:59:40 localhost systemd[1]: Failed to start Fail2ban Service. > Jul 9 08:59:40 localhost systemd[1]: Unit fail2ban.service entered failed > state. > ... > Jul 9 08:59:40 localhost systemd[1]: fail2ban.service holdoff time over, > scheduling restart. > Jul 9 08:59:40 localhost systemd[1]: Stopping Fail2ban Service... > Jul 9 08:59:40 localhost systemd[1]: Starting Fail2ban Service... > Jul 9 08:59:40 localhost systemd[1]: fail2ban.service start request repeated > too quickly, refusing to start. > Jul 9 08:59:40 localhost systemd[1]: Failed to start Fail2ban Service. > Jul 9 08:59:40 localhost systemd[1]: Unit fail2ban.service entered failed > state. >
Have you checked /var/log/audit/audit.log for AVC (selinux) entries? -- The only thing worse than a poorly asked question is a cryptic answer. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
