- syslog-ng - lists.balabit.hu

syslog-ng never frees RAM
by Jose Angel Santiago 10 Sep '18

10 Sep '18

Hi, I'm using syslog-ng 3.16.1 with wildcard-file as source (let's call it "syslog-agent), which sends log messages to another syslog-ng acting as a relay. I've noticed that syslog-agent instances RAM consumption keeps increasing until they leave no free memory in the cluster (each server has 64G of RAM). In my use case, new folders & files are created constantly under base-dir folder, but every 2 days obsolete folders & files are deleted. I assumed that syslog-ng would free some RAM every time those folders & files are deleted, but it doesn't, not even if I run a syslog-ng-ctl reload operation. log-fifo-size value is 345000, so I assume it can't be a buffer situation since 345000 messages can't occupy 40-50 GB of memory. I've performed the following test to reproduce the situation in small scale: - Launch a syslog-agent with a wildcard-file source reading from "/tmp/test/" base-dir. syslog-agent RAM usage is about 125M. - Run a simple script to create complex folder hierarchy under /tmp/test and some files with 5000 log messages to read from. - Wait until syslog-agent RAM usage gets 1GB - Stop script execution and wait until syslog-agent has send all logs to relay. - Delete everything under /tmp/test and execute syslog-ng-ctl reload operation - 24 hours after, syslog-agent RAM usage still is 1GB I've used heaptrack tool as a try to find a memory leak in syslog-ng, you can see in the attached image that iv_list_empty function in iv_list.h file is where most of the RAM usage is. How do I get syslog-ng to free RAM? Or is it a memory leak? Thanks in advance. -- | Jose Angel Santiago [image: Logo_signature2.png] <http://www.stratio.com/> Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo de Alarcón, Madrid, Spain +34 918 286 473 | www.stratio.com <https://twitter.com/stratiobd> <https://www.linkedin.com/company/stratiobd> <https://www.youtube.com/c/StratioBD>

3 7

(no subject)
by R.Naveen Naidu 08 Sep '18

08 Sep '18

Hi, I need a help to choose the syslog-ng package for Linux. What are the things need to consider when choosing the latest syslog-ng to Linux? Actually, I wanted to cross-compile the syslog-ng and load into the customized Linux version *4.1.35rt41* The current latest syslog-ng version is* 3.17.2* from below site and planning to use this. https://github.com/balabit/syslog-ng/releases -- Thanks & Regards Naveen

3 8

problems compiling 3.17.2 on Ubuntu 16.0.4 with java
by Russell Fulton 04 Sep '18

04 Sep '18

I am trying to build syslog-ng with java and json support on Ubuntu 16.0.4. I can’t use prepackaged version because ubuntu have decided that one must not have both rsyslog (which is our corporate standard) and syslog-ng (which I need for its pattern matching in an application) on the same machine. Installing one package removes the other. As well as the standard build tools I have installed these packages via apt: jsoncpp, jre and gradle. Simply running ./configure ran through but did not find java (i.e. java and java-module were both set to no). I added —enable java and configure terminated complaining that it could not find java. I dug into the configure script and found that it was executing “which javac” and “javah” both of which failed. I changed JAVAC to “java” and the configure script then completed with both java and java module enabled. Running make then failed builder@secgendev02:~/src/syslog-ng-3.17.2$ make mkdir -p modules/java/syslog-ng-core/classes GEN modules/java/syslog-ng-core/classes/org/syslog_ng/LogMessage.class Unrecognized option: -d Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. Makefile:20740: recipe for target 'modules/java/syslog-ng-core/classes/org/syslog_ng/LogMessage.class’ failed I am guessing that the version of java the jre package installed is not compatible with the configure script. builder@secgendev02:~/src/syslog-ng-3.17.2$ java -version openjdk version "1.8.0_181" OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) I know that configure checks the java version so I am somewhat surprised… Any Ideas on what to try next? Russell

2 1

Running into http module error.
by vijay amruth 30 Aug '18

30 Aug '18

Hello everyone, Running into this error: [root@xxxxxxxx ~]# syslog-ng -e [2018-08-29T10:53:16.602437] Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng', module='http' Where do I get this module or how do I fix this, any help is apprciated? -- Thanks, Vijay Amrut.

3 2

How to rewrite structured data - XML, Windows Events and format-json
by Jim Hendrick 28 Aug '18

28 Aug '18

I am struggling with a configuration to rewrite specific sections of a Windows Event log message and then send them along to splunk (I think json is probably the easiest for splunk to ingest). Many windows events contain extraneous text (e.g. "This event.....") that I would like to remove. I have been able to rewrite it using a regex "This event.*</Message>" and replacing that with "DEADBEEF</Message>" The problem is that I can only see this in a test file destination and not in one that uses format-json (I set this up from the syslog-ng WEF configuration guide) Has anyone done anything like this? I think my problem is that I don't understand how the message is changed from it's arrival through processing. My test can rewrite it within MSG or MESSAGE - but when I try to use the rewrite() in the log statement using the format-json destination, nothing seems to be changed. Tips? Thanks! Jim

2 1

Connect syslog-ng to HDFS
by Lee Keng Ket 27 Aug '18

27 Aug '18

Hi, I'm trying to connect syslog-ng 3.14.1 to HDFS to store the syslog messages. The syslog-ng can start without error, and it's able to write into local file. However, the log is not written to the HDFS. As there is no single error, I'm not sure how I should troubleshoot on this. I have installed the syslog-ng from this repo, https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng314/repo/epel-7/cza… Installed Packages syslog-ng.x86_64 3.14.1-4.el7.centos @czanik-syslog-ng314 syslog-ng-java.x86_64 3.14.1-4.el7.centos @czanik-syslog-ng314 syslog-ng-java-deps.noarch 1.0-2 @czanik-syslog-ng314 This is the message from /var/log/message: Log statistics; processed='src.internal(s_sys#0)=1', stamp='src.internal(s_sys#0)=1534491834', processed='destination(d_spol)=0', processed='destination(d_mlal)=0', processed='center(received)=2', processed='destination(d_mesg)=1', processed='destination(d_mail)=0', processed='destination(d_auth)=0', processed='destination(d_cron)=0', processed='destination(d_hdfs)=1', processed='center(queued)=3', queued='global(scratch_buffers_count)=0', processed='source(remote_log)=1', dropped='dst.java(d_hdfs#0,java_dst,hdfs,hdfs://x.x.x.x:25000,/user/syslog/$HOST-$DAY-$MONTH-$YEAR.log)=0', processed='dst.java(d_hdfs#0,java_dst,hdfs,hdfs://x.x.x.x:25000,/user/syslog/$HOST-$DAY-$MONTH-$YEAR.log)=1', queued='dst.java(d_hdfs#0,java_dst,hdfs,hdfs://x.x.x.x:25000,/user/syslog/$HOST-$DAY-$MONTH-$YEAR.log)=1', processed='global(payload_reallocs)=0', processed='src.journald(journal)=0', stamp='src.journald(journal)=0', processed='global(sdata_updates)=0', queued='global(scratch_buffers_bytes)=0', processed='destination(d_boot)=0', processed='destination(d_kern)=0', processed='source(s_sys)=1', processed='destination(remote)=1', processed='global(internal_queue_length)=0', processed='global(msg_clones)=0' Anyone has any idea how should I proceed the troubleshooting?

6 20

Problem with syslog-ng OpenSource and SELinux
by QUINONERO Paul (AREVA) 24 Aug '18

24 Aug '18

Hello everyone, I have an issue with syslog-ng on a Centos7 server. I configure a destination to use a python script for parsing my message, but, due to SELinux enforced mode the script is not called. Do you know any solution to fix this problem (I need to keep SELinux enforced)? Thanks in advance

3 3

Insider 2018-08: 3.16 & 3.17; Splunk; IoT security; Telegram; Throttling;
by Czanik, Péter 23 Aug '18

23 Aug '18

Dear syslog-ng users, This is the 68th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS syslog-ng 3.16 & 3.17 are released ---------------------------------- Version 3.16 & 3.17 of syslog-ng are now available. Support to send log messages to Telegram was added. You can also use failback mode when you have failover enabled and send your logs to your primary log server as soon as it is available again. For a complete list of changes, check https://github.com/balabit/syslog-ng/releases/. For binary packages, check https://syslog-ng.com/3rd-party-binaries. Using the syslog-ng Store Box (SSB) in front of Splunk ------------------------------------------------------ The syslog-ng application was used for many years as a log collection layer in front of Splunk. But why use a full-blown log management appliance – like SSB – with a graphical user interface instead of a simple command line application? I learned the answers at Red Hat Summit while talking to my fellow Balabit engineers and booth visitors. https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-store-box-… IoT security: logging --------------------- Recently SANS published a brand new white paper about the Internet of Things: “Stopping IoT-based Attacks on Enterprise Networks”. IoT devices have been around in the networks of enterprises for many years, just think about network-connected printers. But recently, both the number and variety of these devices skyrocketed and enterprises now have to embrace everything from BYOD phones to smart lamps. In this blog post, I would like to highlight a critical aspect of how you can protect your organization from potential IoT-based attacks: logging. https://www.syslog-ng.com/community/b/blog/posts/iot-security-logging Telegram destination in syslog-ng --------------------------------- Getting started with the Telegram destination of syslog-ng is not an easy and straightforward process, but it is well worth the efforts. If you do not know Telegram yet, Telegram is a cloud-based messaging application known for its security and speed. Best of all, it is a free app without ads. No wonder that Telegram is also used by many system administrators. With the Telegram destination of syslog-ng introduced in version 3.16, we intend to help your work as a sysadmin. As a result, you can now receive critical log messages in real-time on your mobile or desktop Telegram client. https://www.syslog-ng.com/community/b/blog/posts/telegram-destination-syslo… hook-commands: easy driver setup -------------------------------- The hook-commands() option of syslog-ng makes it easy to execute external commands when a driver is started or stopped. For example, you can open a port in the firewall when a network source is started and close it once syslog-ng is shut down. Or you could also run a command each time syslog-ng is reloaded. From this blog, you can learn how to start and stop auditing file system changes using auditctl from syslog-ng, then collect, parse and filter the results, and finally send them to Elasticsearch for storage and further analysis. https://www.syslog-ng.com/community/b/blog/posts/hook-commands-easy-driver-… Throttling log messages ----------------------- One of the main advantages of syslog-ng is that it is high performance and low on resource usage. Why throttle the messages then? There are three main reasons – licensing, performance, and bandwidth – all outside of syslog-ng. From this blog, you can learn how to identify use cases for the throttling of log messages, read about a possible drawback, and finally get a sample configuration. https://www.syslog-ng.com/community/b/blog/posts/throttling-log-messages Your feedback and news, or tips about the next issue are welcome at documentation(a)balabit.com. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

syslog-ng with multiple destinations
by swald.ext＠orange.com 22 Aug '18

22 Aug '18

Hello, We are a syslog-ng configuration with multiple destinations : source s_remote_udp { udp(ip(0.0.0.0) port(514)); }; source s_remote_tcp { tcp(ip(0.0.0.0) port(514) max-connections(1000) so_keepalive(yes)); }; destination d_SIEM_ { udp("10.0.1.145" port(514)); }; destination d_BOX_ { file("/var/log/box/FLOW_$R_MONTH$R_DAY$R_HOUR$R_MIN.log" create_dirs(yes) dir_perm(0755) dir_owner(root) dir_group(root) owner(root) group(root)); }; filter f_SIEM_ { match("FLOW:"); }; log { source(s_remote_udp); source(s_remote_tcp); filter(f_SIEM_); destination(d_BOX_); destination(d_SIEM_);flags(flow-control,final); }; We can see kind of errors : /var/log/syslog-ng.log : Aug 4 23:34:39 host1 syslog-ng[16290]: I/O error occurred while reading; fd='32', error='Connection reset by peer (104)' We lose some logs. We have a syslog-ng version 3.2. Can you help please please ? How can I diagnose the problem? How do I get to the root of the problem? Maybe debugging syslog-ng? Thanks in advance. Best regards. Sebastian. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 3

Hosts before DNS
by Oleg 21 Aug '18

21 Aug '18

I am using the latest version of ose ng, and have an issue I am trying to resolve. We have hosts that resolve to multiple names via round robin dns. So ng is capturing logs from all of those, depending on how it was resolved during during the connection. For those types of hosts, I would like to configure ng to use hosts first, and fall back to dns resolution. Tried different combinations of configs, but it does not work this way. It either uses the hosts, or it does dns lookup. Thanks in advance for any tips on resolving this. Example: 10.0.0.1 resolve to www, app1, ftp I want to call it webserver in /etc/hosts, and if the entry matches, ng would just use that name. right now it creates 3 separate log files for the same host based on the name it's able to resolve at lookup.

4 3