- syslog-ng - lists.balabit.hu

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

Installation issue
by hari ram 07 Dec '17

07 Dec '17

Hi I have ubuntu Server install 16.X with all dependency packages #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # more /etc/debian_version stretch/sid when i try to install syslog-ng with debian package as mentioned below steps. ~# more /etc/apt/sources.list.d/syslog-ng-obs.list deb http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/xUb… ./ # apt-get update Hit:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Ign:4 http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/xUb… ./ InRelease Hit:5 http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/xUb… ./ Release Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Fetched 204 kB in 0s (350 kB/s) Reading package lists... Done # apt-get install syslog-ng-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: syslog-ng-core : Depends: libjson-c3 (>= 0.10) but it is not installable E: Unable to correct problems, you have held broken packages. But i have already install libjason package # apt-get install libjson-c-dev Reading package lists... Done Building dependency tree Reading state information... Done libjson-c-dev is already the newest version (0.11-4ubuntu2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. what is the issue, how can i install latest version of syslog-ng default syslog-ng only come with 3.5.6 version, but iam looking 3.11 and above version to install any suggestions ? R!

2 2

Syslog-ng relay: how to delete or modify special character ^M?
by alain.villefranque＠orange.com 06 Dec '17

06 Dec '17

Hi all, I have an issue with the character Carriage Return (^M) inserted by the Syslog source machine. I try to substitute or rewrite this special character with syslog-ng relay, but it is impossible to modify it, it seems this char is invisible for the program. I've tried to modified it with either with ^M or 0xD char with no success. Example of received message: Dec 4 13:35:23 conf01 2017-12-04 13:35:23,561 Level="INFO" Name="support.sip" Message="Sending SIP response" Src-address="80.12.yy.xx" Src-port="5061" Dst-address="161.105.yy.xx" Dst-port="38509" Transport="TLS" Detail="^MSIP/2.0 403 Forbidden^MVia: SIP/2.0/TLS 161.105.150.12:38509;alias;branch=z9hG4bK.MEgSOM8O4;rport=38509;received=161.105.150.12^MFrom: <sip:SondeSQS_001!@int.ovp.orange-business.com>;tag=5kYhVMAyi^MTo: sip:SondeSQS_001!@int.ovp.orange-business.com;tag=aynkBKUjt0pXHzNv^MCSeq: 25 REGISTER^MCall-ID: Vhihsb~BhQ^MAllow: INVITE,ACK,OPTIONS,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIFY,MESSAGE^MSupported: categoryList,adhoclist,sdp-anat,replaces^MContent-Length: 0^M^M" I'd like to suppress ^M or replace it with a "space" char. Is there any specific action to do in order to modify ^M special character ? Regards Alain _________________________________________________________________________________________________________________________ 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 4

OSE 3.13.2
by Budai, László 06 Dec '17

06 Dec '17

Hi, the new release contains the following fixes : - Missing manpages from release tarball (#1793 <https://github.com/balabit/syslog-ng/issues/1793>) - Package syslog-ng-mod-json is removed from (#1794 <https://github.com/balabit/syslog-ng/pull/1794>) - Drop syslog-ng-abi virtual packages (#1797 <https://github.com/balabit/syslog-ng/pull/1797>) regards, Laszlo Budai

1 0

syslog-ng 3.13.1
by Budai, László 05 Dec '17

05 Dec '17

3.13.1Features - Add app-parser() framework (automatic parsing of log messages) (#1689 <https://github.com/balabit/syslog-ng/pull/1689>) - Support microseconds in Riemann destination (#1710 <https://github.com/balabit/syslog-ng/pull/1710>) - Add osquery destination as an SCL plugin (#1728 <https://github.com/balabit/syslog-ng/pull/1728>) - Add network load balancer destination (#1706 <https://github.com/balabit/syslog-ng/pull/1706>) - Add possibility to only signal re-open of file handles (SIGUSR1) (#1530 <https://github.com/balabit/syslog-ng/pull/1530>) - It is possible from now to limit the number of registered dynamic counters (#1743 <https://github.com/balabit/syslog-ng/pull/1743>) - Add $(binary) template function (#1679 <https://github.com/balabit/syslog-ng/pull/1679>) - Add experimental transport for transferring messages in whole between syslog-ng instances (EWMM) (#1689 <https://github.com/balabit/syslog-ng/pull/1689>) - Docker based build and debian package generation (#1783 <https://github.com/balabit/syslog-ng/pull/1783>) - Add auto-parse(yes/no) to app-paser(), system() and default-network-drivers() (#1788 <https://github.com/balabit/syslog-ng/pull/1788>) - Add Graylog2 destination and $(format-gelf) template function (#1680 <https://github.com/balabit/syslog-ng/pull/1680>) Bugfixes - Exit when a read fails on an included config file instead of starting up with an empty configuration. (#1721 <https://github.com/balabit/syslog-ng/pull/1721>) - Fix double free (#1720 <https://github.com/balabit/syslog-ng/issues/1720>) - Add missing discarded counter to groupingby (#1748 <https://github.com/balabit/syslog-ng/pull/1748>) - Fix a reference leak in Python destination (#1716 <https://github.com/balabit/syslog-ng/pull/1716>) - Fix timezone issue in snmptrapd parser (#1746 <https://github.com/balabit/syslog-ng/pull/1746>) - Fix potential crash in stdin driver (#1741 <https://github.com/balabit/syslog-ng/pull/1741>) - Fix a crash when initializing new config fails for socket with keep_alive off (#1723 <https://github.com/balabit/syslog-ng/pull/1723>) - Fix filter evaluation in case of contexts with multiple elements (#1718 <https://github.com/balabit/syslog-ng/pull/1718>) - Various grouping-by fixes (#1718 <https://github.com/balabit/syslog-ng/pull/1718>) - Fix potential use after free around dns-cache during shutdown (#1666 <https://github.com/balabit/syslog-ng/pull/1666>) - Fix access to indirect values within Java destination (#1732 <https://github.com/balabit/syslog-ng/pull/1732>) - Fix a crash in affile (#1725 <https://github.com/balabit/syslog-ng/pull/1725>) - Fix a memory leak (#1724 <https://github.com/balabit/syslog-ng/pull/1724>) - Fix a crash when getent is used empty group (#1691 <https://github.com/balabit/syslog-ng/pull/1691>) - Fix jvm-options() (#1704 <https://github.com/balabit/syslog-ng/pull/1704>) - Fix a crash in Python language binding (#1694 <https://github.com/balabit/syslog-ng/pull/1694>) - Fix a crash in afmongodb (#1765 <https://github.com/balabit/syslog-ng/pull/1765>) - Fix a memory leak in afmongodb (#1766 <https://github.com/balabit/syslog-ng/pull/1766>) - Fix name-to-GID calculation in the $(getent) template function (#1764 <https://github.com/balabit/syslog-ng/pull/1764>) - Fix a crash when redis is configured without the command() option ( #1767 <https://github.com/balabit/syslog-ng/pull/1767>) - Fix a race condition in kv-parser() (#1789 <https://github.com/balabit/syslog-ng/pull/1789>) Other changes - Cleanup diskq related warning messages (#1752 <https://github.com/balabit/syslog-ng/pull/1752>) - Provide tls block for tls options in amqp(), http(), riemann() destination drivers (#1715 <https://github.com/balabit/syslog-ng/pull/1715>) - It it possible from now to register blocks and generators as plugins ( #1657 <https://github.com/balabit/syslog-ng/pull/1657>) - Drop compatiblity with configurations below 3.0 (#1709 <https://github.com/balabit/syslog-ng/pull/1709>) - Do not change permissions of a file by default (#1782 <https://github.com/balabit/syslog-ng/pull/1782>) - Allow source files to specify permissions locally (#1782 <https://github.com/balabit/syslog-ng/pull/1782>) - Minor performance improvement (#1729 <https://github.com/balabit/syslog-ng/pull/1729>) - The current config version can be queried with "--version" (#1740 <https://github.com/balabit/syslog-ng/pull/1740>) - Increase the performance of kv-parser() (#1789 <https://github.com/balabit/syslog-ng/pull/1789>) Notes to the developers - Change configure default option for jsonc and mongoc from auto to internal (#1735 <https://github.com/balabit/syslog-ng/pull/1735>) - Disable ASLR when running unit tests (#1753 <https://github.com/balabit/syslog-ng/pull/1753>) 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 Szalay, Balazs Scheidler, Gabor Nagy, Jakub Jankowski, Janos Szigetvari, Laszlo Budai, Laszlo Varady, Laszlo Szemere, Marton Illes, Mate Farkas, Peter Kokai, Pontus Andersson, Sam Stephenson, Sebastian Roland, Viktor Juhasz, Zoltan Pallagi.

2 4

syslog-ng-3.13: unofficial Debian packages: still building, be careful when updating
by Budai, László 04 Dec '17

04 Dec '17

Hi, packages will be available also for Ubuntu 17.10. There is a major change in packaging: syslog-ng-mod-json is part of syslog-ng-core from now (due to the new app-parser and Enterprise Wide Message Model). regards, Laszlo Budai

1 0

Timezone
by Sebastian Roland 01 Dec '17

01 Dec '17

Hi, after reading the admin guide and playing around with different setups several times I'm still struggling to fully understand the timezone functionality of syslog-ng. How are time-zone() / recv-time-zone() and send-time-zone() related? Some notes I made during investigation: * Logging through syslog() function logs in old BSD syslog format which does not contain a timezone. recv-time-zone() is utilized to assign a timezone. If no value has been specified the local time zone is used. * According to the admin guide send-time-zone() is only used when the timezone is not specified otherwise. This didn't turned out to be true. Example: Syslog server a sends via syslog protocol over tcp (timezone is part of the message) to server b. setting send-time-zone(x) on server b changes the timezone (and timestamp) in the destination file to the time in timezone x. If send-time-zone() is not set at all nothing happens although the admin guide states that the default is to use the local timezone. IMHO no change should be applied to the message. Note that keep- timestamp(yes) is set on server b. * If both time-zone() and send-time-zone() are set globally time-zone() overrides send-time-zone() * time-zone() can be set globally and on drivers. Specific settings overrides global config. The confusing part is the behavior when a timestamp is already set within an incoming message and send-time-zone() is explicitly set (with keep-timestamp(yes)). Is it actually intended that send-time-zone() changes a timestamp? Shouldn't the logic be that recv-time-zone() and send-time-zone() are only relevant when there is no tz offset available and a default one needs to be set for receiving and sending respectively and time-zone() is used to actually convert to a different timezone? If I'm getting something fundamentally wrong please advice. Kind regards Sebastian

2 1