When Kamailio message parser produces this kind of syslog message:
024-11-11T21:16:40.757364+02:00 box /usr/bin/sip-proxy[181398]: ERROR: <core>
[core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg:
message=<#026#003#001#006\340#001>
fail2ban complains:
Consider setting logencoding to appropriate encoding for this jail.
Continuing to process line ignoring invalid characters:
b'2024-11-11T21:06:15.347318+02:00 box /usr/bin/sip-proxy[181398]: ERROR:
<core> [core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg:
message=<#026#003#001#006\xc0#001>\n': 1 Time(s)
Error decoding line from '/var/log/syslog' with 'UTF-8'.: 1 Time(s)
Unable to retrieve Watch object associated to <_RawEvent cookie=0 mask=0x2
name='' wd=13 >: 3 Time(s)
Would it be possible to somehow ensure that Kamailio syslog messages
only contain valid UTF-8 characters?
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
