py-fail2ban turned silent after syslogd rollout (r335059, stable/11)
Michael Grimm
trashcan at ellael.org
Fri Jun 22 20:43:31 UTC 2018
On 22. Jun 2018, at 22:28, Ed Schouten <ed at nuxi.nl> wrote:
> 2018-06-22 22:06 GMT+02:00 Michael Grimm <trashcan at ellael.org>:
>> After applying your patch:
>> Jun 22 21:22:01 HOSTNAME <daemon.notice> [31033]: NOTICE [JAILNAME] Unban x.x.x.x
>>
>> Watch: 'fail2ban.actions' -the service- is missing.
>
> That's likely due to the fact that it now interprets the first word in
> the message as the remote hostname, which gets discarded.
>
> Attached is a somewhat refined patch that only tries to parse the
> hostname in remote messages if they are preceded by a timestamp. If
> the timestamp is missing, it assumes the entire payload is the
> message. Can you give this one a try? Thanks!
Great, you fixed it again in very short time, and I really do appreciate this!
Now with patch v2:
Jun 22 22:39:59 HOSTNAME <daemon.notice> fail2ban.actions [72605]: NOTICE [JAILNAME] Restore Ban x.x.x.x
Thank you very, very much,
Michael
More information about the freebsd-ports
mailing list