- syslog-ng - lists.balabit.hu

testing fix for file source ownership and permissionso
by Jim Segrave 01 Dec '17

01 Dec '17

> hi, > I've just posted a pull request that I didn't have time to test: can you pls test if this fixes the issue for you? > https://github.com/balabit/syslog-ng/pull/1782 <https://github.com/balabit/syslog-ng/pull/1782> While my original patch worked on 3.6.5, we actually need some of the features in 3.12. I have problems with autogen/automake being unhappy with the versions of the autotool chain I have: running autogen.sh: Running autogen in 'lib/ivykis'... libtoolize: You should add the contents of the following files to 'aclocal.m4': libtoolize: '/usr/local/share/aclocal/libtool.m4' libtoolize: '/usr/local/share/aclocal/ltoptions.m4' libtoolize: '/usr/local/share/aclocal/ltversion.m4' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. (catting the suggested files onto aclocal.m4 does not remove these warnings) However configure does finish, but make bombs out with: /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -I../src/include -I../src/include -I /usr/local/src/syslog-ng -Wall -pthread -Wno-error -MT iv_avl.lo -MD -MP -MF .deps/iv_avl.Tpo -c -o iv_avl.lo iv_avl.c libtool: Version mismatch error. This is libtool 2.4.5, but the libtool: definition of this LT_INIT comes from libtool 2.4.2. libtool: You should recreate aclocal.m4 with macros from libtool 2.4.5 libtool: and run autoconf again. make[5]: *** [iv_avl.lo] Error 63 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [lib/ivykis/src/libivykis.la] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I was able to get a working version from the 3.6.5 sources. When I get the 3.12.1 sources from the Centos rpm, I can run configure without running autogen, which does complete and make completes without errors. However, the resulting executable fails to start with this error message: Error parsing config, Error compiling template (Unknown template function "format-json32: included included template-function "format-cim" "$(format-json --pair @timestamp='${R_ISODATE}' --pair .=_ --key *.*)\n"; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I know next to nothing about the automake and friends (or m4 for that matter), so I don't really know how to address this. -- -- Jim Segrave jes(a)j-e-s.net

2 1

Testing application adapters and enterprise-wide message model for syslog-ng
by Czanik, Péter 30 Nov '17

30 Nov '17

Hi, 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. While these features are work in progress and might change considerably in future releases, we appreciate early testing and feedback. With the help of your comments we could cover not just our internal use cases, but also take into account the needs of the wider community. Read more about it at https://www.balabit.com/blog/application-adapters-enterprise-wide-message-m… where you can find information where to download ready to use rpm packages and how to get started. Bye, 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

More on syslog-ng changing ownership and perms of source file
by Jim Segrave 30 Nov '17

30 Nov '17

I added the line: | file_dir_perm_option to the source_affile_option in ./modules/affile/affile-grammar.y:419 would allow setting ownership and permissions on source files (or opting for no-change) This would gave: source_affile_option : KW_FOLLOW_FREQ '(' LL_FLOAT ')' { affile_sd_set_follow_freq(last_driver, (long) ($3 * 1000)); } | KW_FOLLOW_FREQ '(' LL_NUMBER ')' { affile_sd_set_follow_freq(last_driver, ($3 * 1000)); } | KW_PAD_SIZE '(' LL_NUMBER ')' { ((AFFileSourceDriver *) last_driver)->pad_size = $3; } | file_dir_perm_option | multi_line_option | source_reader_option ; I did this with the syslog-ng.3.6.4 source and it now does the following: The owner group and permissions are changed only if the file source line specifies a value (not -1) for one of these items. In other words, it does not use any default value from the configuration, it simply leaves things as it found them. -- Jim Segrave jes(a)j-e-s.net

3 3

Syslog-ng relay: is it possible to modify or delete META SEQUENCE DATA added automaticaly?
by alain.villefranque＠orange.com 29 Nov '17

29 Nov '17

Hi, I experience a pb with the syslog-ng relay that is used in this way: Syslog-relay gather syslog network messages from different sources (legacy RFC 3164 msg ) and send these messages to a central syslog server. The central Syslog server accepts only message with a strict format:only value in green can be modified. <174>1 time_Norme_ISO8601 fqdn syslog-ng 007 - [meta sequenceid=xxxx][bbtlog@1009 bias="titi" platform="prod" produit="ppup" logfile="rtlog.sta" rtlog-river="rtl"] Message With success, I managed to write and modify incoming messages and store them locally in log files with the awaited server format. I used filters, rewrite_set to change the hostname and template to format the received message to the expected format. We don't use meta sequenceid, so we decided to write a non variant value 0000. template("<174>1 ${ISODATE} ${HOST} syslog-ng 007 - [meta sequenceid="0000"] [bblog@1009...] ${MSG}\n"); Now, the deal is to transfer the new line of the log file to the central syslog server. I use a "source" tail file to send the new messages and one new syslog remote destination to redirect the message to the syslog server Here is the message as depicted in TCPDUMP: inpavlog1i-ad.62163 > 10.114.181.43.syslog: SYSLOG, length: 379 Facility local5 (21), Severity info (6) Msg: 1 2017-11-29T10:17:57+01:00 inxipmgt.creteil.francetelecom.fr syslog-ng 007 - [meta sequenceId="1" sequencid="0000"][rtlog@1368 basicat="xip" platform="prod" produit="pexip" logfile="rtlog.sta" rtlog-river="rtl"] 10:17:57,686 Level="INFO" Name="administrator.system.configuration" Message="Conferencing node configuration updated." Node="conf02.int.ovp.orange-business.com"\0x0a So I have an issue with the field [meta sequenceid...] which automatically doubled/added to the previous...(0000) . If I modify the template by deleting the field [meta sequenceid="0000"], template("<174>1 ${ISODATE} ${HOST} syslog-ng 007 - [bblog@1009...] ${MSG}\n"); The result is so that the syslogng-relay add the [meta sequenceId="xxxx"] after the first meta sequence field and write the message with an upper case "I" . This is not accepted by the central server. I suspect also that the location in the frame could have an impact. Here is the tcpdump: inpavlog1i-ad.62163 > 10.114.181.43.syslog: SYSLOG, length: 379 Facility local5 (21), Severity info (6) Msg: 1 2017-11-29T10:17:57+01:00 inxipmgt.creteil.francetelecom.fr syslog-ng 007 - [rtlog@1368 basicat="xip" platform="prod" produit="pexip" logfile="rtlog.sta" rtlog-river="rtl"][meta sequenceId="1"] 10:17:57,686 Level="INFO" Name="administrator.system.configuration" Message="Conferencing node configuration updated." Node="conf02.int.ovp.orange-business.com"\0x0a As I don't use this meta field, is it possible to configure syslog-ng relay not add automatically this field [meta sequenceId="XX"] or to delete it with a command? 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.

1 0

syslog-ng running but not writing logs
by buckingham＠nym.hush.com 27 Nov '17

27 Nov '17

Hello forum members, Having spent a couple of weeks on this problem I thought someone might be able to help getting syslog-ng 3.9.1 to write log files on OpenBSD 6.2. The O/S was a fresh install, then syslog-ng and lastly BIND. No other packages except syslog-ng and BIND dependencies have been installed. No binaries or libs from BIND conflict or replace any from the syslog-ng installation. The .conf file was copied over from an older OpenBSD system, also running an older WORKING syslog-ng (3.1.1). The required changes to the .conf were made so that syslog-ng 3.9.1 with supervisor starts and remains running. By killing the syslog-ng process I was able to test that the supervisor process restarts syslog-ng. The rc.d script starts, stops and restarts syslog-ng as expected. /usr/local/sbin/syslog-ng -s returns no errors, indicating that the config file is sane. In /var/log the only thing it writes are syslog-ng start/stop messages. In an effort to localise the problem, a stub syslog-ng.conf was created with the following contents: @version: 3.9.1 source s_local { unix-dgram("/dev/log"); }; # destination catchall { file(/var/log/catchall); }; log { source(s_local); destination(catchall); }; The permissions and ownership on /var, /var/log, /var/run, and /etc are correct according to the OpenBSD /etc/mtree/special file. Syslog-ng starts retaining root permissions (default) and creates /dev/log if it does not exist. The syslog_ng_flags I use are: "-R /var/run/syslog_ng.persist -c /var/run/syslog_ng.ctl -p /var/run/syslog_ng.pid"Have tried running without any flags to see if that would help, but did not help. The output of syslog-ng -V is: syslog-ng 3.9.1 Installer-Version: 3.9.1 Revision: Module-Directory: /usr/local/lib/syslog-ng Module-Path: /usr/local/lib/syslog-ng Available-Modules: affile,afprog,afsocket,afsql,afuser,basicfuncs,cef,confgen,cryptofuncs,csvparser,curl,date,dbparser,disk-buffer,geoip-plugin,graphite,kvformat,linux-kmsg-format,pseudofile,system-source,add-contextual-data,json-plugin,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 On my hunt I foud a message on NARKIVE where a user was having the same problem with syslog-ng 3.6 on OpenBSD 5.9, there was no solution. There was a reply saying: "With the changes in 5.6 using sendsyslog(2), only syslogd picks up local syslog. Search the openbsd-ports list for syslog-ng to see some comments on it.". After a further search I turned up nothing that would help. Have also tried to compile syslog-ng 3.12 from source to see if that might help solve the problem, but no success on OpenBSD. Many thanks in advance. CB

2 2

Follow-up: syslog-ng changes owner and permissions on a file source (syslog-ng Digest, Vol 151, Issue 20)
by Jim Segrave 24 Nov '17

24 Nov '17

We tried putting a file source with owner and permissions in our syslog-ng configuration: file("/var/log/usenetmonitor/dev/cron-logs/Usenetmonitor-Warnings.log" flags(no-parse) program-override("custom-test") owner(-1) group(-1) perm(-1)); And at startup we get: Error parsing affile, syntax error, unexpected KW_OWNER, expecting KW_NORMALIZE_HOSTNAMES or KW_USE_DNS or KW_USE_FQDN or KW_DNS_CACHE in /etc/syslog-ng/conf.d/remote_syslog.conf at line 4, column 123: file("/var/log/usenetmonitor/dev/cron-logs/Usenetmonitor-Warnings.log" flags(no-parse) program-override("custom-test") owner(-1) group(-1) perm(-1)); ^^^^^ So the documentation is correct, the options are not valid on file sources. But it would be a good thing if they were -- Jim Segrave jes(a)j-e-s.net

1 0

Insider 2017-11: netdata; stats to graphite; logstash to syslog-ng;
by Czanik, Péter 23 Nov '17

23 Nov '17

Dear syslog-ng users, This is the 63rd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Collecting netdata metrics -------------------------- netdata is a system for distributed real-time performance and health monitoring. You can use syslog-ng to collect and filter data provided by netdata and then send it to Elasticsearch for long-term storage and analysis. The aim is to send both metrics and logs to an Elasticsearch instance, and then access it via Kibana. https://www.balabit.com/blog/sending-netdata-metrics-syslog-ng-elasticsearc… syslog-ng statistics to Graphite -------------------------------- syslog-ng makes available various types of statistics. Data is available in a couple of forms: emitted regularly from the internal() source of syslog-ng or obtained using the syslog-ng-ctl utility from the command line. Due to the format that the internal source or the “stats” option of syslog-ng-ctl uses, it is not easy to send statistical data to Graphite or anywhere else. The syslog-ng-ctl utility provides a flexible “query” option, (available in recent versions of syslog-ng) which uses an easy-to-parse output format. Using the “jo” utility by @JPMens, you can convert the output to JSON, which can then be parsed by syslog-ng and forwarded to Graphite. https://www.balabit.com/blog/collecting-syslog-ng-statistics-to-graphite/ Sending logs from Logstash to syslog-ng ---------------------------------- Logstash adds a new syslog header to log messages before forwarding them to a syslog server. In the case of syslog messages, it is problematic as there will be two syslog headers in the message. Using syslog-ng for everything logging related in an Elasticsearch environment can considerably simplify your architecture. Still, there are situations, when Filebeats and Logstash are already deployed and you need some logs from Logstash in syslog-ng. Learn how you can remove the extra syslog header. https://www.balabit.com/blog/sending-logs-logstash-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

syslog-ng changes owner and permissions on a file source
by Jim Segrave 22 Nov '17

22 Nov '17

We are running syslog-ng on a Centos-7 server: root@usenetmonitor-fe01.am4:[~]# /usr/sbin/syslog-ng -V syslog-ng 3 (3.12.1) Installer-Version: 3.12.1 Revision: Compile-Date: Nov 3 2017 15:15:50 Module-Directory: //usr/lib64/syslog-ng Module-Path: //usr/lib64/syslog-ng Available-Modules: afuser,cef,linux-kmsg-format,sdjournal,confgen,map-value-pairs,json-plugin,affile,kvformat,tfgetent,date,afstomp,csvparser,add-contextual-data,cryptofuncs,system-source,syslogformat,afsocket,afprog,pseudofile,afamqp,snmptrapd-parser,dbparser,xml,stardate,tags-parser,graphite,basicfuncs,disk-buffer Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-Linux-Caps: on Enable-Systemd: on When we tried to use syslog-ng to treat a file as a source, it changes the owner and group to root and the permissions to 0664, which is undesireable, as the file must remain writeable by the apache server. This is the source definition in syslog.conf when we were testing: source s_dev { file("/var/log/usenetmonitor/dev/cron-logs/Usenetmonitor-Warnings.log" flags(no-parse) program-override("custom-test")); }; with syslog-ng stopped, here's the status of the file: root@usenetmonitor-fe01:[~]# ls -lt /var/log/usenetmonitor/soc/cron-logs/Usenetmonitor-Warnings.log -rw-r----- 1 apache apache 0 Nov 21 11:00 /var/log/usenetmonitor/soc/cron-logs/Usenetmonitor-Warnings.log As soon as syslog-ng is started it becomes root@usenetmonitor-fe01:[~]# ls -lt /var/log/usenetmonitor/soc/cron-logs/Usenetmonitor-Warnings.log -rw-r--r-- 1 root root 0 Nov 21 11:00 /var/log/usenetmonitor/soc/cron-logs/Usenetmonitor-Warnings.log Checking with strace, I find 16258 open("/var/log/usenetmonitor/dev/cron-logs/Usenetmonitor-Warnings.log", O_RDONLY|O_NOCTTY|O_NONBLOCK) = 24 Followed shortly therafter by: 16258 fchown(24, 0, -1) = 0 16258 fchown(24, -1, 0) = 0 16258 fchmod(24, 0664) = 0 (and no, fd 24 hasn't been closed and re-opened) It's unclear to me why syslog-ng would have any reason to change ownership or permissions of file sources. As there are no options for file sources to set what it would change it to, it seems highly undesireable that this happens. The only workaround is to set global options to disable changing ownership or permissions: perm(-1); owner(-1); group(-1); and then specify those options for every destination file which is a maintenance burden Is there some other way to stop syslog-ng from latering files used as sources? -- Jim Segrave jes(a)j-e-s.net

2 1

syslog-ng events in log timestamping wrong
by Contreras, Gerald (DPS) 22 Nov '17

22 Nov '17

Hi All, I am very new to syslog-ng via Cygwin. I am having trouble with MWG proxy logs where individual events inside the log are being timestamped at the rotation time (timestamping at 00:00-00:01AM). This happens intermittently so the problem isn't constant. I have verified via packet captures that the timestamp is correct up until syslog-ng begins to handle the event and write it to the log. My syslog-ng.conf is as follows =============================================================== @version: 3.2 @include "scl.conf" options { create_dirs(yes); use_dns(yes); dns_cache_hosts(/etc/hosts); dns_cache_expire(3600); chain_hostnames(0); log_fifo_size(512); perm(0644); dir_perm(0755); time_reopen(10); time_reap(360); use_fqdn(no); keep_hostname(no); stats_freq(0); }; source s_network { udp(port("514")); }; destination s_files { file("/cygdrive/d/syslog/$HOST/$HOST-$MONTH-$DAY.log" create_dirs(yes)); }; log { source(s_network); destination(s_files); }; ============================================================== Thanks. Any help or direction would be much appreciated Important Notice: If you have received this email by mistake, please advise the sender and delete the message and attachments immediately. This email, including attachments, may contain confidential, sensitive, legally privileged and/or copyright information. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. Please consider the environment before printing this email.

3 3

Hourly Log rotate
by craig bowser 20 Nov '17

20 Nov '17

So according to https://www.balabit.com/documents/syslog-ng-ose-latest-guides/en/syslog-ng- ose-guide-admin/html/example-logrotate.html using this format: destination d_sorted { file("/var/log/remote/${HOST}/${YEAR}_${MONTH}_${DAY}.log" create-dirs(yes)); }; I can create logs folders and files based on the timestamp. And this is working nicely for us... With a caveat. We are getting a TON of logs, so we want to rotate hourly and archive quickly. My config is this: destination d_msg { file("/var/log/message_${YEAR} _${MONTH}_${DAY}_${HOUR}.log"); }; But instead of creating one file per hour according to the time the event is received, it is creating files based on the timestamp of the event (which, while useful for discovering and tracking down machines with time synch problems, is not so useful for managing log files on the syslog server). Is there a way to make it create files based on the time the event is received and NOT the timestamp of the event? Thanks.

2 2