- syslog-ng - lists.balabit.hu

syslog-ng-3.31.2
by Laszlo Budai 18 Mar '21

18 Mar '21

Hi, syslog-ng 3.31.2[1] packages are available from OBS repositories[2, 3, 4]. List of supported OSs: * Debian 8.0 * Debian 9.0 * Debian 10.0 * Raspbian 9.0 * Raspbian 10.0 * Ubuntu 14.04 * Ubuntu 16.04 * Ubuntu 18.04 * Ubuntu 18.10 * Ubuntu 19.04 * Ubuntu 19.10 * Ubuntu 20.04 * Ubuntu 20.10 Install ------- example: Debian 9.0 1. get release key wget -qO - http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/Deb… | sudo apt-key add - 2. add repo to APT sources eg.: /etc/apt/sources.list.d/syslog-ng-obs.list deb http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/Deb… ./ Then `apt-get update` and `apt-geat install syslog-ng-core` Links -------- [1] https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.31.2 [2] https://build.opensuse.org/package/show/home:laszlo_budai:syslog-ng/syslog-… [3] https://build.opensuse.org/package/show/home:laszlo_budai:syslog-ng/syslog-… [4] https://build.opensuse.org/package/show/home:laszlo_budai:syslog-ng/syslog-… regards, Laszlo Budai

1 0

syslog-ng-3.31.2
by Peter Kokai (pkokai) 18 Mar '21

18 Mar '21

3.31.2 ====== ## Bugfixes * `syslog-parser()`: fix a potential crash in case parsing the message fails and tags are already applied to the message. ## Packaging * `python2`: Direct `python2` support is dropped, we no longer test it in our CI. No `python2` related source codes were removed as for now, but we do not guarantee that it will work in the future. ([#3603](https://github.com/syslog-ng/syslog-ng/pull/3603)) ## Credits syslog-ng is developed as a community project, and as such it relies on volunteers, to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. We would like to thank the following people for their contribution: Andras Mitzki, Antal Nemes, Attila Szakacs, Balazs Scheidler, Gabor Nagy, Laszlo Budai, Laszlo Szemere, László Várady, Norbert Takacs, Peter Kokai, Ryan Faircloth, Zoltan Pallagi

1 0

Docker syslog-ng TLS issue
by Steven La 17 Mar '21

17 Mar '21

I created a CA cert following the instructions here: https://support.oneidentity.com/fr-fr/technical-documents/syslog-ng-open-so… And the serverkey.pem is not encrypted, but syslog-ng is asking for a password when it starts up for the serverkey.pem. Any help would be appreciate Head of the server.key -----BEGIN PRIVATE KEY----- MIIEvAI.... syslog error: [2021-03-17T19:56:03.552322] Error setting up TLS session context; tls_error='system library:fopen:Permission denied', location='/etc/syslog-ng/syslog-ng.conf:21:2' [2021-03-17T19:56:03.552355] Error setting up TLS context; keyfile='/etc/ssl/certs/cert.d/serverkey.pem' [2021-03-17T19:56:03.552407] Waiting for password; keyfile='/etc/ssl/certs/cert.d/serverkey.pem' syslog-ng config: @version: 3.29 @include "scl.conf" source s_local { internal(); }; source s_network { default-network-drivers( # NOTE: TLS support # # the default-network-drivers() source driver opens the TLS # enabled ports as well, however without an actual key/cert # pair they will not operate and syslog-ng would display a # warning at startup. # tls(key-file("/etc/ssl/certs/cert.d/serverkey.pem") cert-file("/etc/ssl/certs/cert.d/servercert.pem") ca_dir("/etc/ssl/certs/ca.d")) peer_verify(optional-untrusted) ); }; destination d_local { file("/var/log/messages"); file("/var/log/messages-kv.log" template("$ISODATE $HOST $(format-welf --scope all-nv-pairs)\n") frac-digits(3)); }; log { source(s_local); source(s_network); destination(d_local); }; docker run command: sudo docker run -d --privileged -it -v "/data/syslog-ng/config/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf" -v "/data/syslog-ng/logs:/var/log" -v "/data/syslog-ng/certs:/etc/ssl/certs" -p 514:514/udp -p 601:601 -p 6514:6514 --name syslog-ng2 balabit/syslog-ng:latest -edv Thanks, Steven -- Steven La 408-503-0289 steven.la(a)datastax.com <Steven.La(a)datastax.com> | datastax.com

2 2

syslog-ng-ctl reload and disbuffer clear
by Pal, Laszlo 17 Mar '21

17 Mar '21

Hi, We are using several instances of syslog-ng OSE to send logs to SIEM. Of course, I'm using diskbuffer and throttle to limit the number of logs sent and keep my licensing happy :) However, every time when I change the config and reload syslog-ng it seems all the logs in the disk buffer is sent in once, so there is some event drop in SIEM Is there any way to avoid this? Here is my relevant part of the config destination d_siem { network( "xxx.xxx.xxx.xxx" port(514) suppress(5) throttle(500) frac_digits(0) log_fifo_size(500000) time_zone("Europe/Budapest") persist-name("siem_standard") transport(tcp) disk-buffer( mem-buf-length(2000) disk-buf-size(50000000000) reliable(no) dir("/data/syslog-ng/diskbuffer") ) ); }; Thanks Laszlo

1 0

GSoC interest
by Ηλίας Κυράννας 17 Mar '21

17 Mar '21

Hello all, I am a PhD student and I would like to participate in the GSoC this year. I have nearly three years of professional experience using syslog in the IoT and security context. I am familiar with Kafka and I find the “Add EOS support to kafka-c destination driver” very interesting. I didn’t find any issue related to this feature. If this is ok I could open one on GitHub to discuss and contribute so that I can work on my proposal. I could also engage in the MacOS project as I have previous experience with C in MacOS. Any hint would be appreciated. Best regards, Ilias Kyrannas

2 1

Insider 2021-03: Kafka; Windows; Bastille;
by Peter Czanik (pczanik) 11 Mar '21

11 Mar '21

Dear syslog-ng users, This is the 89th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Consuming logs from a Kafka topic --------------------------------- There is no official Kafka source in syslog-ng, but because this question comes up often enough, I created one. It is just a temporary workaround using the program() source, but it works. It involves Java and installing Kafka manually, but it was fast and reliabe in my tests: ingesting 50,000–100,000 messages a second on my laptop in a resource-constrained virtual machine. https://www.syslog-ng.com/community/b/blog/posts/consuming-logs-from-a-kafk… Collecting logs from Windows ---------------------------- Normally I cover free and open-source software in the syslog-ng blog. But recently quite a few members of the community reached out to me and asked about collecting logs from Windows. So, I prepared a quick overview of the topic. The good news is, that syslog-ng supports collecting logs from Windows in multiple ways. The not so good news is that Windows support is only available in the commercial version of syslog-ng. There are multiple ways for collecting log messages from Windows. You can either install syslog-ng agents on Windows hosts, or you can use the Windows Event Collector (WEC) component of syslog-ng PE. https://www.syslog-ng.com/community/b/blog/posts/collecting-logs-from-windo… Running syslog-ng in Bastille ----------------------------- Bastille is a container management system for FreeBSD, similar to Docker or Podman on Linux. The historical name of containers on FreeBSD is jail, and they appeared a lot earlier than containers on Linux. Managing jails was not always easy. When I started to use this technology in production in 2001, nothing was automated. Using Bastille, you can easily create, configure, or update jails at scale. It has a template system to install applications in containers and there is a template also for syslog-ng. From this blog, you can learn how to get started with Bastille and how to create and run a syslog-ng jail using the freshly released 0.8 version of Bastille. https://www.syslog-ng.com/community/b/blog/posts/running-syslog-ng-in-basti… Syslog-ng OSE 3.31.1 released ----------------------------- Version 3.31.1 of syslog-ng OSE was released with the Fortigate parser, many parsing-related enhancements, silent Telegram messages, and more. For a complete list of changes, check https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-3.31.1 WEBINARS * Scale log collection from Windows endpoints with WEC clustering in syslog-ng https://www.syslog-ng.com/event/scale-log-collection-from-windows-endpoints… * 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

Syslog-ng segfault at version 3.8.1
by Sam Kappen 08 Mar '21

08 Mar '21

Hi All, We have an issue from a customer who uses syslog-ng version 3.8.1 on the 3.10.108 kernel(Hardware: freescale-p2020ds-3.10-1.4). Customer observed a segmentation fault after syslog-ng being stuck for more than one hour. There are no reproducible steps available, the issue is seen as random. As per the backtrace segfault happened from "malloc_consolidate" which looks an odd behaviour.On checking the frame it looks mchunkptr "p" has the value 0x2 which caused this crash, but not been able to find out what is the root cause for this. Has there been any known issue with syslog-ng? Any idea if this issue is fixed in version 3.16.1. Any help or pointers would be appreciated. Attached the back trace. Back trace snippet: Program terminated with signal 11, Segmentation fault. #0 malloc_consolidate (av=av@entry=0xffc738c <main_arena>) at malloc.c:4070 4070 malloc.c: No such file or directory. (gdb) bt #0 malloc_consolidate (av=av@entry=0xffc738c <main_arena>) at malloc.c:4070 #1 0x0fec5cb4 in _int_malloc (av=av@entry=0xffc738c <main_arena>, bytes=bytes@entry=556) at malloc.c:3374 #2 0x0fec6f64 in __GI___libc_malloc (bytes=556) at malloc.c:2874 #3 0x0f90d58c in standard_malloc (n_bytes=<optimized out>) at gmem.c:85 #4 0x0f90d9f0 in g_malloc (n_bytes=n_bytes@entry=556) at gmem.c:159 #5 0x0f7be00c in log_msg_alloc (payload_size=256) at lib/logmsg/logmsg.c:1084 #6 log_msg_new_empty () at lib/logmsg/logmsg.c:1150 #7 0x0f7be088 in log_msg_new_local () at lib/logmsg/logmsg.c:1160 #8 0x0f7be194 in log_msg_new_mark () at lib/logmsg/logmsg.c:1260 #9 0x0f7713e8 in afinter_source_mark (s=0x10863690) at lib/afinter.c:142 #10 0x0f7c4c74 in iv_run_timers (st=st@entry=0x10284d30) at iv_timer.c:149 #11 0x0f7c72bc in iv_main () at iv_main_posix.c:107 #12 0x0f78b990 in main_loop_run () at lib/mainloop.c:497 #13 0x10001260 in main (argc=1, argv=0xbfbe7724) at syslog-ng/main.c:270 (gdb) Regards, Sam

1 0

syslog-ng-3.31.1
by Peter Kokai (pkokai) 08 Mar '21

08 Mar '21

3.31.1 ====== ## Highlights * fortigate-parser(): new parser to parse fortigate logs Example: ``` log { source { network(transport("udp") flags(no-parse)); }; parser { fortigate-parser(); }; destination { }; }; ``` An adapter to automatically recognize fortigate logs in app-parser() has also been added. ([#3536](https://github.com/syslog-ng/syslog-ng/pull/3536)) * `patterndb`: Added `OPTIONALSET` parser. It works the same as `SET`, but continues, even if none of the characters is found. ([#3540](https://github.com/syslog-ng/syslog-ng/pull/3540)) ## Features * `syslog-parser()`: add no-header flag to tell syslog-ng to parse only the PRI field of an incoming message, everything else is just put into $MSG. ([#3538](https://github.com/syslog-ng/syslog-ng/pull/3538)) * `set-pri()`: this new rewrite operation allows you to change the PRI value of a message based on the string directly parsed out of a syslog header. ([#3546](https://github.com/syslog-ng/syslog-ng/pull/3546)) * telegram: option to send silent message Example: ``` destination { telegram(bot-id(...) chat-id(...) disable_notification(true)); }; ``` ([#3558](https://github.com/syslog-ng/syslog-ng/pull/3558)) * `app-parser()`: added automatic classification & parsing for project Lumberjack/Mitre CEE formatted logs ([#3569](https://github.com/syslog-ng/syslog-ng/pull/3569)) * diskq: if the dir() path provided by the user does not exists, syslog-ng creates the path with the same permission as the running instance ([#3550](https://github.com/syslog-ng/syslog-ng/pull/3550)) ## Bugfixes * `network()`, `syslog()` destinations: fix reconnection timer when DNS lookups are slow After a long-lasting DNS query, syslog-ng did not wait the specified time (`time_reopen()`) before reconnecting to a destination. This has been fixed. ([#3526](https://github.com/syslog-ng/syslog-ng/pull/3526)) * cmake: minor fixes ([#3523](https://github.com/syslog-ng/syslog-ng/pull/3523)) * `stats-level()`: fix processing the changes in the stats-level() global option: changes in stats-level() were not reflected in syslog facility/severity related and message tag related counters after first configuration reload. These counters continued to operate according to the value of stats-level() at the first reload. ([#3561](https://github.com/syslog-ng/syslog-ng/pull/3561)) * `date-parser()`: fix hour-only timezone parsing If the timestamp contains a short timezone offset (e.g. hours only), the recent change in strptime() introduces an error, it interprets those numbers as minutes instead of hours. For example: Jan 16 2019 18:23:12 +05 ([#3555](https://github.com/syslog-ng/syslog-ng/pull/3555)) * `loggen`: fix undefined timeout while connecting to network sources (`glib < 2.32`) When compiling syslog-ng with old glib versions (< 2.32), `loggen` could fail due a timeout bug. This has been fixed. ([#3504](https://github.com/syslog-ng/syslog-ng/pull/3504)) * `grouping-by()`: fix deadlock when context expires In certain cases, the `grouping-by()` parser could get stuck when a message context expired, causing a deadlock in syslog-ng. This has been fixed. ([#3515](https://github.com/syslog-ng/syslog-ng/pull/3515)) * `date-parser`: Fixed a crash, which occured sometimes when `%z` was used. ([#3553](https://github.com/syslog-ng/syslog-ng/pull/3553)) * `date-parser`: `%z`. We no longer ignore daylight saving time when calculating the GMT offset. ([#3553](https://github.com/syslog-ng/syslog-ng/pull/3553)) * `kafka-c`: fix a double LogMessage acknowledgement bug, which can cause crash with segmentation fault or exit with sigabrt. The issue affects both flow-controlled and non-flow-controlled log paths and it's triggered in case previously published messages failed to be delivered to Kafka. ([#3583](https://github.com/syslog-ng/syslog-ng/pull/3583)) * `python destination`: Fixed a rare crash during reload. ([#3568](https://github.com/syslog-ng/syslog-ng/pull/3568)) * `date-parser()`: fix non-mandatory parsing of timezone name When %Z is used, the presence of the timezone qualifier is not mandatory, so don't fail that case. ([#3555](https://github.com/syslog-ng/syslog-ng/pull/3555)) * `wildcard-file()`: fix infrequent crash when file renamed/recreated The wildcard-file source crashed when a file being processed was replaced by a new one on the same path (renamed, deleted+recreated, rotated, etc.). ([#3513](https://github.com/syslog-ng/syslog-ng/pull/3513)) * Remove the no-parse flag in system() source from FreeBSD kernel messages, so the message header is no more part of the message. ([#3586](https://github.com/syslog-ng/syslog-ng/pull/3586)) * Fix abort on macOS Big Sur A basic subset of syslog-ng's functionality now works on the latest macOS version. ([#3522](https://github.com/syslog-ng/syslog-ng/pull/3522)) * `affile`: Fix improper initialization in affile and LogWriter to avoid memory leak when reloading ([#3574](https://github.com/syslog-ng/syslog-ng/pull/3574)) * `udp destination`: Fixed a bug, where the packet's checksum was not calculated, when `spoof-source(yes)` and `ip-protocol(6)` were set. ([#3528](https://github.com/syslog-ng/syslog-ng/pull/3528)) * `python`: fix LogMessage.keys() listing non-existenting keys and duplicates ([#3557](https://github.com/syslog-ng/syslog-ng/pull/3557)) ## Packaging * Simplify spec file by removing obsolete technologies: - remove RHEL 6 support - remove Python 2 support - keep Java support, but remove Java-based drivers (HDFS, etc.) ([#3587](https://github.com/syslog-ng/syslog-ng/pull/3587)) * `libnet`: Minimal libnet version is now 1.1.6. ([#3528](https://github.com/syslog-ng/syslog-ng/pull/3528)) * configure: added new --enable-manpages-install option along with the existing --enable-manpages. The new option would install pre-existing manpages even without the DocBook tools installed. ([#3493](https://github.com/syslog-ng/syslog-ng/pull/3493)) ## Notes to developers * `apphook`: the concept of hook run modes were introduced, adding support for two modes: AHM_RUN_ONCE (the original behavior) and AHM_RUN_REPEAT (the new behavior with the hook repeatedly called after registration). ([#3561](https://github.com/syslog-ng/syslog-ng/pull/3561)) ## Credits syslog-ng is developed as a community project, and as such it relies on volunteers, to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. We would like to thank the following people for their contribution: 0140454, Andras Mitzki, Antal Nemes, Attila Szakacs, Balazs Scheidler, egorbeliy, Gabor Nagy, Laszlo Budai, Laszlo Szemere, László Várady, Michael Ducharme, Norbert Takacs, Peter Czanik, Peter Kokai, Pratik raj, Ryan Faircloth, Zoltan Pallagi

1 0

Syslog-ng 3.4.5 support question
by mukesh kumar 05 Mar '21

05 Mar '21

Hi, We are using syslog-ng 3.4.5 version and we are using it to utilize patterndb. We are not looking for bug fix but using it for just all the different ways we can use the patterndb xml. Please provide me the info on such as the IF and ELSE statements, For loops in the xml file. Thanks, Mukesh Kumar

4 5

CentOS Stream
by Peter Czanik (pczanik) 03 Mar '21

03 Mar '21

Hi, CentOS is right now the most popular platform to run syslog-ng. On the other hand, they are shifting focus to CentOS Stream: https://blog.centos.org/2020/12/future-is-centos-stream/ Due to these changes many people are looking now for alternative platforms. Replacements for regular CentOS releases are under way: AlmaLinux is already in RC phase, Rocky Linux is arriving soon. I heard many people switching to openSUSE. And of course, there are also non-rpm alternatives, like Ubuntu or even FreeBSD. As I'm doing syslog-ng packaging for our most popular platforms (Fedora/CentOS/RHEL, openSUSE/SLES, FreeBSD), I'm curious what to expect on the packaging frontier. What will be our future platforms? I'm running a poll on Twitter: https://twitter.com/PCzanik/status/1366391907748831235 If your choice is "other", I'd love to know what is that other platform! Thanks for your feedback, Peter 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