September 2024 - syslog-ng - lists.balabit.hu

fatal error is syslog-ng 4.8 from copr when reading pipe sources.
by Evan Rempel 04 Oct '24

04 Oct '24

I upgraded syslog-ng today from 4.6 to 4.8 and my disk drive almost immediately filled due to the local error from syslog-ng 2024-09-20T11:59:38.760-07:00 hostname syslog.err syslog-ng[600690]: Error invoking seek on file; filename='/var/log/syslog.pipes/mailstats2', error='Illegal seek (29)' This logged repeatedly until the disk filled up. My source definition for that pipe is source mailstats2 { pipe("/var/log/syslog.pipes/mailstats2" log_iw_size(900000) log_fetch_limit(500) flags(no-parse) ); }; Any insight would be useful. -- Evan

2 2

Suppress UTF-8 BOM in incoming network messages
by Jeremy Utley 25 Sep '24

25 Sep '24

I'm trying to use Syslog-NG to receive logs from our anti-virus web console (ESET Protect). I've got the logs coming in successfully, but they seem to be adding a UTF-8 BOM as part of the message: [2024-09-23T19:03:36.709950] Incoming log entry; input='<15>1 2024-09-23T19:03:36.455Z b35f2351-8f78-4414-b964-415939a7b0fb ERAServer 43 - - <feff>{"event_type" : "Audit_Event","ipv4" : "172.17.0.11","ipv6" : "","hostname" : "b35f2351-8f78-4414-b964-415939a7b0fb","source_uuid" : "b35f2351-8f78-4414-b964-415939a7b0fb","os_name" : "","occured" : "23-Sep-2024 19:03:36","group_name" : "","group_description" : "","severity" : "Information","domain" : "Mapped account","action" : "Logout","target" : "35396c68-5017-4ea9-b268-d209f8040de9","detail" : "Logging out mapped account \'Jeremy Utley\'.","user" : "Jeremy Utley","result" : "Success"}', msg='0x7f6020022150', rcptid='0' Because I only care about the JSON data being provided, I'm setting the "flags(no-parse)" option in my network source, and a rewrite filter to remove the initial data as follows: source s_network { network( port(6514) transport("tls") flags(no-parse) tls( key-file("/etc/syslog-ng/certs/syslog.key") cert-file("/etc/syslog-ng/certs/syslog.crt") peer-verify(optional-untrusted) ) ); }; rewrite r_trimjson { subst("^(.*)- - ", "", value("MESSAGE")); }; destination d_json { file("/var/log/json_data.log" template("${MESSAGE}\n")); }; But I can't seem to eliminate the BOM from the output, and that is messing with JSON parsing, since that is added to the beginning of every line (but the first) in my json_data.log file. I tried adding "\xfe\xff" to the rewrite in an attempt to eliminate it, but that didn't work - the rewrite does not even match at that point. Anyone have any suggestions on how I can deal with this? Thanks! Jeremy Utley

2 1

tls problems when chaning the server certificate syslog-ng-4.6.0
by Evan Rempel 13 Sep '24

13 Sep '24

I have a syslog server running syslog-ng-4.6.0 (from the copr repo). I am not seeing any TLS issues in the logs using the existing ca.d certificate and the current server tls certificate. The current tls certificate will expire soon, and the CA used to sign the server certificate can no longer be used. I have created a new server certificate, signed with a new Root CA. This new Root CA has been successfully added to the ca.d folder and is running without error with the current server certificate. When I replace the server certificate with the new one and restart syslog-ng, I start getting a lot of errors in the logs. SSL error while reading stream; tls_error='error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca' The new server certificate validates $openssl verify tls/server.crt tls/server.crt: OK The CA used to sign the certificate is in the ca.d folder with the correct hash. I have to assume that the error is actually revering to the server certificate, but it could be referring to a client certificate. The error goes away when I switch the server certificate back. The only things that changes for this error is using the new server certificate. How do I track this down? Are there any other suggestions on what might have gone wrong? -- Evan

2 2

rewrite in syslog-ng
by Wilson, Jonathan L 12 Sep '24

12 Sep '24

Running OSE version 3.38.1 and having difficulty with a rewrite rule. The logs that I'm trying to modify look like: 2024-09-12T06:39:31-05:00 hostname kernel: [*09/12/2024 11:39:31.9055] bwar: [7649:I:CN_ML] ... What I am trying to do is remove the extra timestamp in square brackets (the first field in square brackets above.) My rewrite rule looks like: rewrite r_bracketed_ts { subst( '^[.+]\s', '', type(pcre), value("MESSAGE")); }; It is invoked from this log statement: log { source(s_BSD_UDP_514); filter(f_something); rewrite(r_bracketed_ts); destination(d_something); flags(final,flow-control); }; The problem is that the rewrite appears to do nothing; log entries come out unmodified. Am I missing something? Thank you - Jon Wilson

2 1

The syslog-ng Insider 2024-09: documentation; TRANSPORT macro; rolling RPMs
by Peter Czanik (pczanik) 11 Sep '24

11 Sep '24

Dear syslog-ng users, This is the 123rd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS You can also contribute to the syslog-ng OSE documentation ---------------------------------------------------------- The up-to-date syslog-ng Administration Guide received a new look and easier navigation, as well as better search experience. Best of all, you can now also easily contribute to the syslog-ng documentation. https://www.syslog-ng.com/community/b/blog/posts/you-can-also-contribute-to… The $TRANSPORT macro of syslog-ng --------------------------------- Do you want to know how your log messages arrived to syslog-ng? The new $TRANSPORT macro provides you with part of the answer. It shows you the protocol variant for network sources, or the kind of local source used. https://www.syslog-ng.com/community/b/blog/posts/the-transport-macro-of-sys… Rolling RPM platforms added to the syslog-ng package build system ----------------------------------------------------- Syslog-ng uses a container-based system to generate the official source tgz and to build ready-to-use packages for various Linux distributions. Recently, we added support for some rolling RPM Linux distributions, allowing us to spot breaking changes before a stable release of the OS would become available. https://www.syslog-ng.com/community/b/blog/posts/rolling-rpm-platforms-adde… WEBINARS * You can browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0