On 11 January 2017 at 11:38, Thufir Hawat <hawat.thu...@gmail.com> wrote: > I'm on Ubuntu 16.04 running on AWS EC2 and thought that fail2ban was > running, but: > > > > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# systemctl status fail2ban.service > ● fail2ban.service - Fail2Ban Service > Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor > preset: enabled) > Active: inactive (dead) (Result: exit-code) since Wed 2017-01-11 11:29:08 > UTC; 1min 52s ago > Docs: man:fail2ban(1) > Process: 8804 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, > status=255) > > Jan 11 11:29:08 fqdn.long systemd[1]: fail2ban.service: Control process > exited, code=exited status=255 > Jan 11 11:29:08 fqdn.long systemd[1]: Failed to start Fail2Ban Service. > Jan 11 11:29:08 fqdn.long systemd[1]: fail2ban.service: Unit entered failed > state. > Jan 11 11:29:08 fqdn.long systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > Jan 11 11:29:08 fqdn.long systemd[1]: fail2ban.service: Service hold-off > time over, scheduling restart. > Jan 11 11:29:08 fqdn.long systemd[1]: Stopped Fail2Ban Service. > Jan 11 11:29:08 fqdn.long systemd[1]: fail2ban.service: Start request > repeated too quickly. > Jan 11 11:29:08 fqdn.long systemd[1]: Failed to start Fail2Ban Service. > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# systemctl start fail2ban.service > Job for fail2ban.service failed because the control process exited with > error code. See "systemctl status fail2ban.service" and "journalctl -xe" for > details. > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# journalctl -xe > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Service hold-off > time over, scheduling restart. > Jan 11 11:31:18 fqdn.long systemd[1]: Stopped Fail2Ban Service. > -- Subject: Unit fail2ban.service has finished shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit fail2ban.service has finished shutting down. > Jan 11 11:31:18 fqdn.long systemd[1]: Starting Fail2Ban Service... > -- Subject: Unit fail2ban.service has begun start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit fail2ban.service has begun starting up. > Jan 11 11:31:18 fqdn.long fail2ban-client[8834]: ERROR Failed > fqdn.subdomaining configuration: While reading from '/etc/fail2ban/jail.co > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Control process > exited, code=exited status=255 > Jan 11 11:31:18 fqdn.long systemd[1]: Failed to start Fail2Ban Service. > -- Subject: Unit fail2ban.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit fail2ban.service has failed. > -- > -- The result is failed. > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Unit entered failed > state. > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Service hold-off > time over, scheduling restart. > Jan 11 11:31:18 fqdn.long systemd[1]: Stopped Fail2Ban Service. > -- Subject: Unit fail2ban.service has finished shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit fail2ban.service has finished shutting down. > Jan 11 11:31:18 fqdn.long systemd[1]: fail2ban.service: Start request > repeated too quickly. > Jan 11 11:31:18 fqdn.long systemd[1]: Failed to start Fail2Ban Service. > -- Subject: Unit fail2ban.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit fail2ban.service has failed. > -- > -- The result is failed. > root@fqdn.subdomain:/var/log# > root@fqdn.subdomain:/var/log# > > > > I'm not understanding nor seeing what the problem actually is. Is there an > error code I don't see? >
The problem seems to be indicated here: Jan 11 11:31:18 fqdn.long fail2ban-client[8834]: ERROR Failed fqdn.subdomaining configuration: While reading from '/etc/fail2ban/jail.co Looks like a truncated log line, but presumably there is some misconfiguration in your jail.conf (btw, it is better not to make any changes in jail.conf but instead use jail.local). ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
