- syslog-ng - lists.balabit.hu

closing inactive or idle incoming connections
by Evan Rempel 07 Apr '21

07 Apr '21

Using syslog-ng 3.26 at the moment but can use the latest if the options are available or easier. Is there a way to configure the idle timeout for incoming connections. I have a use case where we want to log from a mobile work force, which can be anywhere on the internet. This means that our syslog server needs to be open to the internet. The bad guys are connecting to our port and not sending anything, just tying up the port. The port requires a certificate so is "safe", however, the connection is consumed for approx 2 hours before syslog-ng dropes the connection with syslog-ng[22490]: Error reading RFC6587 style framed data; fd='3769', error='Connection timed out (110)' syslog-ng[22490]: Syslog connection closed; fd='4509', client='AF_INET()', local='AF_INET()' Is there a way to configure syslog-ng to drop the connection if it does not receive the certificate in 60 seconds? Is there a way to configure syslog-ng to drop the connection if no syslog messages are received in 10 minutes? Thanks, -- Evan

2 1

syslog-ng has add extra field
by Ivan Nepryahin - Bercut 26 Mar '21

26 Mar '21

Hi all! I think I have a stupid question, but I really dont know how this make. Situation: When I send syslog message with timestamp in format "1Mar 25 2021 16:35:49" everything works great, but when I send message with timestamp in format "1Mar 25 2021 16:35:49+03:00", syslog-ng adding two extra fields with timestamp and IP address and due that break down file naming. Question: How can I say to syslog-ng server do not add extra fields when he get message with +03:00 in timestamp? message without +03:00 Mar 25 13:11:57 HUAWEI-CORE-OFFICE-1 <bla bla bal> mesage with +03:00 Mar 25 13:46:45 192.168.100.34 Mar 25 2021 16:46:45+03:00 HUAWEI-CORE-OFFICE-1 <bla bla bla> I will be appreciate for any advice! P.s sorry for bad english it is not my native language best regards, Nepryahin Ivan IT Department Phone: +7 812 327 32 33 Mobile: +7 911 291 81 68

3 8

how syslog-ng users handle sflow in their environmen
by Ali Okan Yuksel 25 Mar '21

25 Mar '21

Hi team, How we can collect sflow messages and feed to syslog-ng? I found a project but I am not sure that if this project can be used for feeding syslog-ng https://github.com/sflow/sflowtool/ I want to get sflow traffic from A10 cgnat solution and feed it as syslog. What are your suggestions? I want to use open-source tools. -- http://www.siyahsapka.org

2 1

Upgrade to 3.31 from 3.19
by Faine, Mark R. (MSFC-IS40)[NICS] 23 Mar '21

23 Mar '21

I need to know the significant format differences between the configuration files for the two versions. Is there some place I can go to get that or some command I can run to convert the file? Thanks, -Mark

4 7

Destination with disk-buffer and reliable(yes) looses queued messages on restart/crash?
by Ralf.Steppacher＠swisscom.com 22 Mar '21

22 Mar '21

Hello, I am probably missing something here: I am trying to configure syslog-ng (3.27.1) running in a Kubernetes Pod, using a Persistent Volume mounted at /var/log, such that queued messages are spooled to disk and in the event of a crash of syslog-ng the queue can be recovered. I configured the destination like so: destination d_forwarder { syslog( "`HEAVY_FORWARDER_HOST`" port(`HEAVY_FORWARDER_PORT`) transport("tls") tls( ca-dir("/etc/syslog-ng/ca.d") key-file("/vault/secrets/client_key.pem") cert-file("/vault/secrets/client_cert.pem") peer-verify(required-trusted) ) disk-buffer( mem-buf-size(524288) disk-buf-size(104857600) reliable(yes) dir("/var/log") ) ); }; The documentation for the `reliable` flag says: "If set to yes, syslog-ng OSE cannot lose logs in case of reload/restart, unreachable destination or syslog-ng OSE crash." I can see several *.rqf files being created in /var/log. As soon as the latest of them reaches roughly 100MB messages start to get dropped. So far everything as expected. Stats: { "center_queued_processed": 72031, "center_received_processed": 36016, "destination_d_forwarder_processed": 36015, "destination_d_local_processed": 36016, "dst_syslog_d_forwarder_0_tls_heavy-forwarder_shared-services_svc_cluster_local_6514_dropped": 4173, "dst_syslog_d_forwarder_0_tls_heavy-forwarder_shared-services_svc_cluster_local_6514_processed": 36015, "dst_syslog_d_forwarder_0_tls_heavy-forwarder_shared-services_svc_cluster_local_6514_queued": 31842, "dst_syslog_d_forwarder_0_tls_heavy-forwarder_shared-services_svc_cluster_local_6514_written": 0, ... "source_s_external_tls_processed": 36015 ... } /var/log: I have no name!@syslog-ng-76f898f5bb-sh9q8:/var/log$ ls -lh total 213M -rw------- 1 10001 10001 38K Mar 22 08:33 syslog-ng-00000.rqf -rw------- 1 10001 10001 4.0K Mar 22 09:25 syslog-ng-00001.rqf -rw------- 1 10001 10001 101M Mar 22 09:29 syslog-ng-00002.rqf -rw------- 1 10001 10001 4.0K Mar 22 09:46 syslog-ng-00003.rqf -rw------- 1 10001 10001 4.0K Mar 22 10:14 syslog-ng-00004.rqf ... Now, if I kill the syslog-ng Pod or gracefully scale the deployment to 0 and back up to 1, the queue is still lost. The stats all go back to 0 and bringing up the destination shows no (queued) messages coming in. On every restart a new .rqf gets created. New messages get spooled to the latest .rqf file until that one reaches the configured 100Mb size limit as well. What am I missing here? Thanks in advance! Ralf

2 2

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