Hi Michael, Marek,
2018-06-22 22:48 GMT+02:00 Marek Zarychta :
> Patch compiles fine and I can confirm, that it resolves the issue.
Thanks for testing to both of you. Really appreciated.
I've just committed this patch as r335565. As it is a bit more
intrusive than the previous patch I wrote, let
On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote:
> Hi Marek,
>
> [ +glebius ]
>
> Thanks for reporting this!
>
> 2018-06-22 18:54 GMT+02:00 Michael Grimm :
> >> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST:
> >> %LINEPROTO-5-UPDOWN: Line protocol on Interface F
On 22. Jun 2018, at 22:28, Ed Schouten wrote:
> 2018-06-22 22:06 GMT+02:00 Michael Grimm :
>> After applying your patch:
>>Jun 22 21:22:01 HOSTNAME [31033]: NOTICE [JAILNAME]
>> Unban x.x.x.x
>>
>> Watch: 'fail2ban.actions' -the service- is missing.
>
> That's likely due to the fact t
Hi Michael,
2018-06-22 22:06 GMT+02:00 Michael Grimm :
> After applying your patch:
> Jun 22 21:22:01 HOSTNAME [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 me
Hi Ed,
On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote:
E> > Ah, yes! Haven't thought about running syslogd in debugging mode:
E> >
E> > Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]:
INFO […]
E>
E> This is interesting. As fail2ban uses Python's logging fr
On 22. Jun 2018, at 21:26, Michael Grimm wrote:
> On 22. Jun 2018, at 21:11, Ed Schouten wrote:
>> Michael, Marek, could you please give this patch a try? Thanks!
>
> Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd with the
> re-compiled one, and:
>
> Thank you! Your patch
On 22. Jun 2018, at 21:11, Ed Schouten wrote:
> Gleb, what are your thoughts on the attached patch? It alters syslogd
> to let the 'legacy' RFC 3164 parser also accept messages without a
> timestamp. The time on the syslogd server will be used instead.
>
> Michael, Marek, could you please give t
Hi Marek,
[ +glebius ]
Thanks for reporting this!
2018-06-22 18:54 GMT+02:00 Michael Grimm :
>> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST:
>> %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17,
>> changed state to down
>
> Ah, yes! Haven't thought about ru
On Fri, Jun 22, 2018 at 08:13:59PM +0200, Kurt Jaeger wrote:
> > I have rolled back to r334835. The issue has gone. Should a PR be
> > created about this regression ?
>
> Yes, please.
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229236
--
Marek Zarychta
signature.asc
Description: PGP s
Hi!
> >> Could you please give any advice or workaround for this issue?
> > I switched to a workaround for the time being which you might use as well
> > in a similar way:
> >
> > #) configure fail2ban to use /var/log/faillog
> > #) run something like that in the background:
> >
> > nohup tai
W dniu 2018.06.22 o 19:14, Michael Grimm pisze:
> On 22. Jun 2018, at 17:59, Marek Zarychta
> wrote:
>
>> Could you please give any advice or workaround for this issue?
> I switched to a workaround for the time being which you might use as well in
> a similar way:
>
> #) configure fail2ban to
On 22. Jun 2018, at 17:59, Marek Zarychta wrote:
> Could you please give any advice or workaround for this issue?
I switched to a workaround for the time being which you might use as well in a
similar way:
#) configure fail2ban to use /var/log/faillog
#) run something like that in the backgrou
Marek Zarychta wrote:
> On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote:
>> Hi,
>>
>> this is 11.2-STABLE (r335532), and I am referring to the recent MFC of
>> syslogd modifications [1].
>>
>> Because I cannot judge whether fail2ban lacks support for the renewed
>> syslogd or s
On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote:
> Hi,
>
> this is 11.2-STABLE (r335532), and I am referring to the recent MFC of
> syslogd modifications [1].
>
> Because I cannot judge whether fail2ban lacks support for the renewed syslogd
> or syslogd has an issue in receiving
Hi,
this is 11.2-STABLE (r335532), and I am referring to the recent MFC of syslogd
modifications [1].
Because I cannot judge whether fail2ban lacks support for the renewed syslogd
or syslogd has an issue in receiving fail2ban messages I do crosspost this mail
to ports and stable.
I do have f
15 matches
Mail list logo
