- syslog-ng - lists.balabit.hu

3.13 maintenance branch
by Scheidler, Balázs 09 Jan '18

09 Jan '18

Hi, I have just pushed a branch containing a number of bugfixes for the 3.13 branch, that I felt would be useful to be published in various syslog-ng binary packages over the existing 3.13.2 release that we produced a few weeks ago. https://github.com/balabit/syslog-ng/tree/3.13/master The most important change is this: https://github.com/balabit/syslog-ng/commit/7e96705ec0b3570857ed6cd66913999… Which is bug that causes the elasticsearch2 destination SCL wrapper to fails to start up if any __VARARGS__ is used. (see https://github.com/balabit/syslog-ng/issues/1804) The other patches are just my selection of fixes that were deemed low risk to me. We expect the next official syslog-ng release to be 3.14 at the end of February, and I've felt this set of fixes would be useful even in the meantime. At this point, I take this as an experiment: if publishing fixes this way "works" (e.g. fixes get published in the OS packages that we don't maintain ourselves), then we can get some form of maintenance to older open source releases as time permits, with collaboration from our fellow OS maintainers. Also, power users, who are able to compile source code for themselves get help too. Let me know if this is useful. Cheers, -- Bazsi

2 2

Does anyone use kafka as a source
by Evan Rempel 08 Jan '18

08 Jan '18

I would like to source log messages from kafka with syslog-ng so that I can leverage some message parsing components. I may place the post parsed messages back into a kafka pipe but I am having problems determining a good way to get messages from kafka to syslog-ng. Any recommendations? -- Evan

3 2

syslog-ng inside LXC guest receives kernel messages from host
by webman＠manfbraun.de 03 Jan '18

03 Jan '18

Hello! It's the first time, that I use syslog-ng (although the plan ist old - due to the ability to use rabbitmq ...). The host (which is a VM too - do not know exactly which type) has the normal rsyslog installed (was "shipped" with it and not directly of my interest - so I kept it). What I am getting from the host are kernel messages generated from iptables logging - I know the log prefix. The guest has just now no iptables rules at all, but a running ulog2, which (no iptables rules at the moment) just runs, but has nothing to log and messages continue to arrive, after I've stopped it. I had a reboot in between, just to be sure, iptables has not something in its memory. There is a bridge to the host and the outside. While the iptables rules were active, I blocked port 514, but this does not change anything. As told, the messages now continue, even iptables has no active rules. A tcpdump inside the lxc guest does not show packages on port 514. BTW, the messages are logged with the hostname of the guest. syslog-ng uses the standards for it input (system, internal). Probably someone could shed some light on it. It is nothing more worrying, then messages from unknown source! Thanks anyway and best regards, Manfred

2 1

Syslog-ng versions available with RHEL 6
by Carter, Jed 02 Jan '18

02 Jan '18

Good morning, I am currently running syslog-ng OSE version 3.7 and RHEL 6. I'm trying to update my syslog-ng OSE through EPEL. It looks like the only way to get syslog-ng v3.12 is from RHEL 7. What is the latest version of syslog-ng OSE that is supported by RHEL 6? Thank you, Jed -- Jed Carter GCIH, GSEC, CEH Information Security Engineer Partners Health Care The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

5 5

Problem using Python Parser
by Ronald Fenner 30 Dec '17

30 Dec '17

When I try to load my config with a python parser in it I'm getting this error message: Starting /opt/syslog-ng/sbin/syslog-ng: [2017-12-29T23:00:05.813945] Error loading Python module; module='_syslogng', exception='exceptions.ImportError: No module named _syslogng' [2017-12-29T23:00:05.814066] Error looking Python parser class; parser='p_php_fpm', class='PhpFpmParser', exception='None' [2017-12-29T23:00:05.814116] Error initializing message pipeline; plugin name='python', location='/opt/syslog-ng/etc/syslog-ng.conf:52:20' I build syslog-ng from source with the python options. Here is the -V output syslog-ng 3 (3.11.1) Installer-Version: 3.11.1 Revision: Compile-Date: Dec 29 2017 21:24:13 Module-Directory: /opt/syslog-ng/lib/syslog-ng Module-Path: /opt/syslog-ng/lib/syslog-ng Available-Modules: snmptrapd-parser,affile,cef,afstomp,basicfuncs,pseudofile,tfgetent,afsocket,mod-python,json-plugin,afuser,kvformat,stardate,graphite,dbparser,csvparser,date,afmongodb,system-source,disk-buffer,confgen,linux-kmsg-format,afamqp,map-value-pairs,http,afprog,add-contextual-data,sdjournal,cryptofuncs,syslogformat Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: off Enable-TCP-Wrapper: off Enable-Linux-Caps: off Enable-Systemd: off Not sure how to fix this as from what I can tell this module is supposed to be compiled in and automatically imported. Ronald Fenner Programmer Game Circus LLC. rfenner(a)gamecircus.com

3 4

Host name issue while logging
by hari ram 16 Dec '17

16 Dec '17

Hi It was running ok till yesterday all the logs are stored with Hostname and date format after upgrade the hostname not able to log in the log format, what is the fix ? Looks like after upgrade to new 3.13 my logs no longer able to use hostname it is storing like this :-2017-12-11.log before INET-2017-12-11.log ( INET Missing why ) any changes ? in the new code 3.13 ? R!

2 2

Insider 2017-12: 3.13; Splunk HEC; Application Adapters; Graylog;
by Czanik, Péter 14 Dec '17

14 Dec '17

Dear syslog-ng users, This is the 64th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS syslog-ng 3.13 released -------------------------- The latest version of syslog-ng, 3.13 is now available. It now parses collected messages automatically using application adapters and can easily forward name-value pairs using the enterprise-wide message model. Support for Graylog and the GELF message format was also added. There are many more smaller features and bug fixes. For a complete list check the release announcements: https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.13.1 and https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.13.2 Sending logs to Splunk through HTTP ----------------------------------- For quite some time, Splunk has recommended to collect syslog messages using syslog-ng, save them to files, and send them to Splunk using forwarders. Unless you have a very high message rate, the HTTP destination of syslog-ng can greatly simplify this logging architecture. Instead of writing messages to files and reading them by a forwarder, syslog-ng can forward messages to Spunk HTTP Event Collector (HEC) directly, using HTTP or HTTPS connections. And if you parse messages using syslog-ng, you can send the resulting name-value pairs to Splunk in JSON format and be able to search them instantly. https://www.balabit.com/blog/sending-logs-splunk-http/ Application Adapters & Enterprise-wide Message Model ---------------------------------------------------- Do you want to simplify parsing your log messages? Try the new “application adapter” and “enterprise-wide message model” frameworks in syslog-ng: you can automatically parse log messages and forward the results to another syslog-ng instance. Optionally, you can also include the original, raw message that you can forward unmodified to a SIEM system for further analysis. Learn how to use these new features from https://www.balabit.com/blog/application-adapters-enterprise-wide-message-m… Graylog as destination in syslog-ng ----------------------------------- Version 3.13 of syslog-ng introduced a graylog2() destination and a GELF (Graylog Extended Log Format) template to make sending syslog messages to Graylog easier. You can also use them to forward simple name-value pairs where the name starts with a dot or underscore. If names of your name-value pairs include dots other than the first character, you should use JSON formatting directly instead of the GELF template and send logs to a raw tcp port in Graylog, which can then extract fields from nested JSON. https://www.balabit.com/blog/graylog-destination-syslog-ng/ 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.org/ Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik

1 0

"Error initializing message pipeline; plugin name='java', location='#buffer:2:3'" after update to syslog-ng 3.12
by Roegels Ruben 14 Dec '17

14 Dec '17

Hi there, I'm using the OSE of syslog-ng for some weeks. Today I updated syslog-ng to 3.13 and afterwards I started seeing -- Unit syslog-ng.service has begun starting up. Dez 13 11:53:59 syslog syslog-ng[23803]: [2017-12-13T11:53:59.572246] Error initializing message pipeline; plugin name='java', location='#buffer:2:3' Dez 13 11:53:59 syslog systemd[1]: syslog-ng.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Dez 13 11:53:59 syslog systemd[1]: Failed to start System Logger Daemon. -- Subject: Unit syslog-ng.service has failed -- Defined-By: systemd-13T11:53:59.572246] Error initializing message pipeline; plugin name='java', location='#buffer:2:3' In "journalctl -xe" If I disable the elasticsearch destination syslog-ng starts up fine. I don't know what to look at as the error message is not very meaningful to me. Did I miss some configuration format changes regarding the "elasticsearch2" destination? The header of my "/etc/syslog-ng/syslog-ng.conf": === Snip === @version: 3.13 @module mod-java @include "scl.conf" === Snip === My elasticsearch config for syslog-ng: https://pastebin.com/g6UB3gBi "ls -l {/usr/share/elasticsearch/lib/,/usr/lib/syslog-ng/3.13/java-modules/}" https://pastebin.com/nqYAVhHL "cat /etc/systemd/system/multi-user.target.wants/syslog-ng.service" https://pastebin.com/UzfQXvZL I really appreciate any help. Thank you! Best regards, Ruben ____________________________________________________________________________ netsys IT GmbH Ruben Roegels Nelly-Sachs-Str. 4 79111 Freiburg Tel. +49 761 888 691 0 Fax +49 761 888 691 10 <http://www.netsys-it.de> Ruben.Roegels(a)netsys-it.de ____________________________________________________________________________ Amtsgericht Freiburg HRB 5752 Geschaeftsfuehrer: Juergen Dufner ____________________________________________________________________________

3 2

SYSLOG-NG config issue and suggestion
by hari ram 08 Dec '17

08 Dec '17

Hi Now my syslog server running. Just try to use in my network and export the logs Logstash or elastic Search Take example I have SWITCH1, SWITCH2 ....100 How can i send logs to elasticsearch, as a ID of switch name and so i can search in Elastic search and make Kibana dashboards R!

2 1

Elastic 5 Support For More Than HTTP?
by JONATHAN PRICE 08 Dec '17

08 Dec '17

All, A project I'm working on is wanting to leverage syslog-ng as our log shipper, but we're ideally wanting it to communicate with Elasticsearch 5 over HTTPS or searchguard. My understanding is current support is only for HTTP for Elastic 5. Are there plans to add elastic 5 support for other client modes than HTTP anytime soon? I'm fine just doing HTTP for now and switching to secured communications later. If not, I'm okay spending a bit of time trying to get that working myself; I haven't delved too deep into the source, but the changes involving updates to the elastic module do not seem to be too too intensive and only include Java changes. Is this a correct interpretation? It doesn't look like it would be too difficult to do, but since it hasn't been done I was wondering if there was something else involved I'm missing. -- Thanks, Jonathan Price Associate Scientist, Cyber Security Raytheon BBN Technologies

2 1