Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
Roger
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler roger@gwch.net wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
What release/version?
Hello,
Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux
Fail2ban: fail2ban.noarch 0.9.7-2.fc26
...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,542 fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,540 fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service...
Thanks!
Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler roger@gwch.net wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Hi,
Mine works fine:
● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2017-06-27 23:46:09 CEST; 2 months 4 days ago Docs: man:fail2ban(1) Process: 698 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 977 (fail2ban-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/fail2ban.service └─977 /usr/bin/python3 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
Jun 27 23:45:50 servername systemd[1]: Starting Fail2Ban Service... Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,491 fail2ban.server [924]: INFO Starting Fail2ban v0.9.7 Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,508 fail2ban.server [924]: INFO Starting in daemon mode Jun 27 23:46:09 servername systemd[1]: Started Fail2Ban Service.
Same kernel.
However I have only one jail. How many jails do you have? Does it start if you reduce the number of jails? Have you seen this: https://github.com/fail2ban/fail2ban/issues/969 Unfortunately the bug is still open...
Daniel
Am 31.08.2017 um 07:55 schrieb Roger Grosswiler:
Hello,
Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux
Fail2ban: fail2ban.noarch 0.9.7-2.fc26
...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,542 fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,540 fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service...
Thanks!
Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler <roger@gwch.net mailto:roger@gwch.net> wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org mailto:arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org mailto:arm-leave@lists.fedoraproject.org
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
hi,
thanks, yes i saw the bug, even if its quite old. i didnt find where to change that number.
i have 7 jails, none of them is starting, just one main thread, which does not seem to be a jail.
the service is running as yours does. but there is no jail at all, i think, as i get no mail notification about any jail.
i use mail notification, do you?
Am 31. August 2017 21:05:50 MESZ schrieb Daniel Laczi daniell1@t-online.de:
Hi,
Mine works fine:
● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2017-06-27 23:46:09 CEST; 2 months 4 days ago Docs: man:fail2ban(1) Process: 698 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 977 (fail2ban-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/fail2ban.service └─977 /usr/bin/python3 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
Jun 27 23:45:50 servername systemd[1]: Starting Fail2Ban Service... Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,491 fail2ban.server [924]: INFO Starting Fail2ban v0.9.7 Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,508 fail2ban.server [924]: INFO Starting in daemon mode Jun 27 23:46:09 servername systemd[1]: Started Fail2Ban Service.
Same kernel.
However I have only one jail. How many jails do you have? Does it start if you reduce the number of jails? Have you seen this: https://github.com/fail2ban/fail2ban/issues/969 Unfortunately the bug is still open...
Daniel
Am 31.08.2017 um 07:55 schrieb Roger Grosswiler:
Hello,
Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux
Fail2ban: fail2ban.noarch 0.9.7-2.fc26
...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31
07:53:51,542
fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31
07:53:51,540
fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service...
Thanks!
Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler <roger@gwch.net mailto:roger@gwch.net> wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says,
it
cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org mailto:arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org mailto:arm-leave@lists.fedoraproject.org
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Hi,
I don't use mail notification, but the jail creation is being logged and I've tested it.
Have you tried reducing the number of jails? I'd try it with only one jail and do a real test (eg. enter the password for a fake account or whatever applies).
Daniel
On 31 August 2017 21:50:48 GMT+02:00, Roger Grosswiler roger@gwch.net wrote:
hi,
thanks, yes i saw the bug, even if its quite old. i didnt find where to change that number.
i have 7 jails, none of them is starting, just one main thread, which does not seem to be a jail.
the service is running as yours does. but there is no jail at all, i think, as i get no mail notification about any jail.
i use mail notification, do you?
Am 31. August 2017 21:05:50 MESZ schrieb Daniel Laczi daniell1@t-online.de:
Hi,
Mine works fine:
● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2017-06-27 23:46:09 CEST; 2 months 4 days ago Docs: man:fail2ban(1) Process: 698 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 977 (fail2ban-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/fail2ban.service └─977 /usr/bin/python3 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x
-b
Jun 27 23:45:50 servername systemd[1]: Starting Fail2Ban Service... Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,491 fail2ban.server [924]: INFO Starting Fail2ban v0.9.7 Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,508 fail2ban.server [924]: INFO Starting in daemon mode Jun 27 23:46:09 servername systemd[1]: Started Fail2Ban Service.
Same kernel.
However I have only one jail. How many jails do you have? Does it
start
if you reduce the number of jails? Have you seen this: https://github.com/fail2ban/fail2ban/issues/969 Unfortunately the bug is still open...
Daniel
Am 31.08.2017 um 07:55 schrieb Roger Grosswiler:
Hello,
Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux
Fail2ban: fail2ban.noarch 0.9.7-2.fc26
...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31
07:53:51,542
fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31
07:53:51,540
fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service...
Thanks!
Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler <roger@gwch.net mailto:roger@gwch.net> wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says,
it
cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org mailto:arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org mailto:arm-leave@lists.fedoraproject.org
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
El jue, 31-08-2017 a las 21:50 +0200, Roger Grosswiler escribió:
hi,
thanks, yes i saw the bug, even if its quite old. i didnt find where to change that number.
i have 7 jails, none of them is starting, just one main thread, which does not seem to be a jail.
the service is running as yours does. but there is no jail at all, i think, as i get no mail notification about any jail.
i use mail notification, do you?
I do get mail notifcations and my jail/s work.
my /etc/fail2ban/jail.local looks like the following
[DEFAULT] findtime = 86400 bantime = 86400 banaction = firewallcmd-ipset backend = systemd sender = <actual email> destemail = <actual email> action = %(action_mwl)s
[sshd] enabled = true
I also have a few other jails enabled where appropriate. I have the following packages installed
fail2ban-systemd-0.9.7-2.fc26.noarch fail2ban-server-0.9.7-2.fc26.noarch fail2ban-firewalld-0.9.7-2.fc26.noarch fail2ban-sendmail-0.9.7-2.fc26.noarch
Dennis
Am 31. August 2017 21:05:50 MESZ schrieb Daniel Laczi <daniell1@t- online.de>:
Hi, Mine works fine: ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2017-06-27 23:46:09 CEST; 2 months 4 days ago Docs: man:fail2ban(1) Process: 698 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 977 (fail2ban-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/fail2ban.service └─977 /usr/bin/python3 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
Jun 27 23:45:50 servername systemd[1]: Starting Fail2Ban Service... Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,491 fail2ban.server [924]: INFO Starting Fail2ban v0.9.7 Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,508 fail2ban.server [924]: INFO Starting in daemon mode Jun 27 23:46:09 servername systemd[1]: Started Fail2Ban Service. Same kernel. However I have only one jail. How many jails do you have? Does it start if you reduce the number of jails? Have you seen this: https: //github.com/fail2ban/fail2ban/issues/969 Unfortunately the bug is still open... Am 31.08.2017 um 07:55 schrieb Roger Grosswiler:
Hello, Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux Fail2ban: fail2ban.noarch 0.9.7-2.fc26 ...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,542 fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,540 fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service... Thanks! Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler <roger@gwch.n et> wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.o rg
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
So! This is not nice! I had 12 jails working before. I rewrote my private jail.config, didn't help. Changed it in default jail.conf (should'nt), enabled 2 jails - working. huh? Reworte again my private config in jail.d with 2 jails, working. Based on try and error, i confiirm for me, that 7 jails are working flawlessy, from the eight on, it gives back the error-message. Can anybody confirm this? Clear bug for me! Roger Am Freitag, den 01.09.2017, 09:11 -0500 schrieb Dennis Gilmore:
El jue, 31-08-2017 a las 21:50 +0200, Roger Grosswiler escribió:
hi,
thanks, yes i saw the bug, even if its quite old. i didnt find where to change that number.
i have 7 jails, none of them is starting, just one main thread, which does not seem to be a jail.
the service is running as yours does. but there is no jail at all, i think, as i get no mail notification about any jail.
i use mail notification, do you?
I do get mail notifcations and my jail/s work.
my /etc/fail2ban/jail.local looks like the following
[DEFAULT] findtime = 86400 bantime = 86400 banaction = firewallcmd-ipset backend = systemd sender = <actual email> destemail = <actual email> action = %(action_mwl)s
[sshd] enabled = true
I also have a few other jails enabled where appropriate. I have the following packages installed
fail2ban-systemd-0.9.7-2.fc26.noarch fail2ban-server-0.9.7-2.fc26.noarch fail2ban-firewalld-0.9.7-2.fc26.noarch fail2ban-sendmail-0.9.7-2.fc26.noarch
Dennis
Am 31. August 2017 21:05:50 MESZ schrieb Daniel Laczi <daniell1@t- online.de>:
Hi, Mine works fine: ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2017-06-27 23:46:09 CEST; 2 months 4 days ago Docs: man:fail2ban(1) Process: 698 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 977 (fail2ban-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/fail2ban.service └─977 /usr/bin/python3 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
Jun 27 23:45:50 servername systemd[1]: Starting Fail2Ban Service... Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,491 fail2ban.server [924]: INFO Starting Fail2ban v0.9.7 Jun 27 23:46:06 servername fail2ban-client[698]: 2017-06-27 23:46:06,508 fail2ban.server [924]: INFO Starting in daemon mode Jun 27 23:46:09 servername systemd[1]: Started Fail2Ban Service. Same kernel. However I have only one jail. How many jails do you have? Does it start if you reduce the number of jails? Have you seen this: https: //github.com/fail2ban/fail2ban/issues/969 Unfortunately the bug is still open... Am 31.08.2017 um 07:55 schrieb Roger Grosswiler:
Hello, Release: Linux stbarth 4.12.8-300.fc26.armv7hl #1 SMP Thu Aug 17 18:39:25 UTC 2017 armv7l armv7l armv7l GNU/Linux Fail2ban: fail2ban.noarch 0.9.7-2.fc26 ...and some logs...
Aug 31 07:53:55 stbarth systemd[1]: Started Fail2Ban Service. Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:55 stbarth fail2ban-client[2887]: ERROR NOK: ("can't start new thread",) Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,542 fail2ban.server [2888]: INFO Starting in daemon mode Aug 31 07:53:51 stbarth fail2ban-client[2887]: 2017-08-31 07:53:51,540 fail2ban.server [2888]: INFO Starting Fail2ban v0.9.7 Aug 31 07:53:48 stbarth systemd[1]: Starting Fail2Ban Service... Thanks! Roger
Am 2017-08-30 16:17, schrieb Peter Robinson:
On Wed, Aug 30, 2017 at 3:12 PM, Roger Grosswiler <roger@gwch .n et> wrote:
Hi,
is someone else experiencing problems? with fail2ban and systemd?
Mine doesn't start the jails, client itself is running. Log says, it cannot create a separate child per jail.
What release/version? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject .o rg
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.o rg
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
On Fri, Sep 1, 2017 at 4:37 PM, Roger Grosswiler roger@gwch.net wrote:
So! This is not nice!
I had 12 jails working before. I rewrote my private jail.config, didn't help. Changed it in default jail.conf (should'nt), enabled 2 jails - working. huh?
Reworte again my private config in jail.d with 2 jails, working. Based on try and error, i confiirm for me, that 7 jails are working flawlessy, from the eight on, it gives back the error-message. Can anybody confirm this?
Clear bug for me!
Sounds like it, I'd report the bug in bugzilla as the maintainer might not be on this list:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=26&...