- syslog-ng - lists.balabit.hu

Filtering out messages before any other action
by Faine, Mark R. (MSFC-IS40)[NICS] 27 Mar '19

27 Mar '19

I have the following as the first log path in my configuration, however, My understanding is that this should match any message with the text 'type=traffic' AND any of the listed policyid=## or a message with the text 'action=timeout'. Flags(final) indicates that it should not be further processed by any other log path. However, I'm still seeing messages that should be discarded, am I doing something wrong? log { if { filter { message('type=traffic') }; filter { ( message('policyid=35 ') or message('policyid=37 ') or message('policyid=38 ') or message('policyid=40_D ') or message('policyid=5 ') or message('policyid=10 ') or message('policyid=12 ') or message('policyid=50 ') or message('policyid=3 ') or message('action=timeout ') ) }; destination { file("/dev/null"); }; }; flags(final); }; Thanks, -Mark

2 2

syslog-ng.conf filter not working
by Lin, Victor 27 Mar '19

27 Mar '19

Dear All, I am trying to forwarding all cisco IOS and Nexus to remote server Here is from my syslog-ng.conf ********************* # Syslog collection for all devices source s_network { network( transport("udp") port(514) flags(syslog_protocol) keep_hostname(yes) keep_timestamp(yes) use_dns(no) use_fqdn(no) ); }; destination d_all_logs { file("/app/syslog-ng/My_custom/My_output/all_devices.log"); }; #All syslogs log { source(s_network); destination(d_all_logs); }; ***************************** #Cisco to elastic Mar.22.2019 destination d_cisco_logs { file("/app/syslog-ng/My_custom/My_output/cisco.log"); network("10.20.30.44" port(2514) transport(udp) spoof_source(yes)); }; ***************************************** #Cisco logs to elastic Mar.22.2019 log { source(s_network); filter(f_cisco_message); destination(d_cisco_logs); }; *********************************** #Cisco to elastic Mar.22.2019 filter f_cisco_message { match ("Cisco IOS", value ("MESSAGE")); or match ("Cisco Nexus", value ("MESSAGE")); }; But looks like cisco.log is never have any data inside. Below is from Could you please review my config and advice ? Thank you so much for your reply in advance! VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

Best way to manage apache's access logs
by Nik Ambrosch 26 Mar '19

26 Mar '19

How are people managing their apache access logs using syslog-ng these days - still just piping through logger? I'm looking to take over logging entirely using syslog-ng, not just reading files from disk and sending to ES or something. In the past I've used cronolog, which works fine, but I'd love the flexibility of sending the logs through syslog-ng.

3 4

Setting and using variables
by Faine, Mark R. (MSFC-IS40)[NICS] 25 Mar '19

25 Mar '19

Is there a way to set variables in syslog-ng? I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch: log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ... I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this: if ( tags('mytag') ) { app = asa location = msfc elif ... and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" Thanks, -Mark

3 11

seems like program filter is broken
by Stanislav 22 Mar '19

22 Mar '19

Greetings, I'm getting this issue after my last package upgrade ====================================== Name : syslog-ng Version : 3.20.1 Installed on : Mon Mar 11 23:27:29 2019 EET Origin : sysutils/syslog-ng Architecture : FreeBSD:12:amd64 Prefix : /usr/local Categories : sysutils Licenses : Maintainer : cy(a)FreeBSD.org WWW : http://www.syslog-ng.org/ Comment : Powerful syslogd replacement Options : AMQP : off CURL : off DOCS : on GEOIP2 : off IPV6 : off JAVA : off JAVA_MOD : off JSON : on MONGO : off PYTHON : off REDIS : off RIEMANN : off SMTP : off SPOOF : off SQL : off TCP_WRAPPERS : off ====================================== I have following configuration: options { chain_hostnames(off); flush_lines(0); threaded(yes); create_dirs(yes); }; source local { internal(); unix-dgram( "/var/run/log" owner(root) group(wheel) perm(0666) ); unix-dgram( "/var/run/logpriv" owner(root) group(wheel) perm(0600) ); file( "/dev/klog" program_override("kernel") ); }; ... destination all { file("/var/log/all.log"); }; destination maillog_mda { file("/var/log/maillog-mda"); }; ... filter p_mail_imap { program("dovecot"); }; ... log { source(local); destination(all); }; log { source(local); filter(p_mail_imap); destination(maillog_mda); }; ====================================== # ps auxww|grep dovecot root 9648 0.0 0.1 13268 4196 - Is 00:46 0:00.04 /usr/local/sbin/dovecot -c /usr/local/etc/dovecot/dovecot.conf dovecot 9651 0.0 0.0 12724 3784 - I 00:46 0:00.01 anvil: [2 connections] (anvil) root 15259 0.0 0.0 12796 4168 - I 01:42 0:00.00 dovecot/log root 16126 0.0 0.1 13744 5020 - I 01:52 0:00.02 dovecot/config dovecot 16127 0.0 0.0 12724 4180 - I 01:52 0:00.01 stats: [3 connections] (stats) dovecot 17328 0.0 0.1 21284 12276 - I 02:05 0:00.01 auth: [0 wait, 0 passdb, 0 userdb] (auth) ====================================== # syslog-ng -s # echo $? 0 ====================================== I'm getting logs from dovecot program to /var/log/all.log but not /var/log/maillog-mda . As I mentioned before it was working on previous version of syslog-ng . Does anybody have this issue? Just me, lucky?

3 8

use loggen to insert content of a file into local log file
by Lin, Victor 19 Mar '19

19 Mar '19

Hello Fabien, Udp 5514 be listening by syslog-ng and write the info into /app/syslog-ng/output/AAA.log ****************************************************************** Here is from syslog-ng.conf source s_AAA_network { network( transport("udp") port(5514) flags(syslog_protocol) keep_hostname(yes) keep_timestamp(yes) use_dns(no) use_fqdn(no) tags("cppm") ); }; destination d_cppm_logs { file("/app/syslog-ng/output/AAA.log"); network("192.168.22. 39" port(5514) transport(udp) spoof_source(yes)); }; log { source(s_AAA_network); destination(d_AAA_Audit_logs); }; I can see both AAA.log and remote server 192.168.22. 39 can receive the syslog messages. ************************************************************************ When I run a test command below, I got the following output /app/syslog-ng/bin/loggen -D localhost 5514 "test test test" count=1864, rate = 963.75 msg/sec count=2348, rate = 967.19 msg/sec count=2830, rate = 963.87 msg/sec count=3314, rate = 967.87 msg/sec count=3796, rate = 963.87 msg/sec count=4280, rate = 967.41 msg/sec count=4762, rate = 963.75 msg/sec count=5246, rate = 967.87 msg/sec count=5728, rate = 963.87 msg/sec count=6212, rate = 967.87 msg/sec count=6694, rate = 963.71 msg/sec count=7177, rate = 965.46 msg/sec count=7660, rate = 965.70 msg/sec count=8142, rate = 963.74 msg/sec count=8626, rate = 967.71 msg/sec count=9108, rate = 963.85 msg/sec count=9590, rate = 963.84 msg/sec count=10074, rate = 966.30 msg/sec count=10554, rate = 959.80 msg/sec average rate = 1055.01 msg/sec, count=10554, time=10.0037, (average) msg size=256, bandwidth=263.75 kB/sec but I didn't see "test test test" been writen into /app/syslog-ng/output/AAA.log Do I using the correct format of loggen command? Thank you very much! VL -----Original Message----- From: syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of syslog-ng-request(a)lists.balabit.hu Sent: 2019, March, 07 7:00 AM To: syslog-ng(a)lists.balabit.hu Subject: syslog-ng Digest, Vol 167, Issue 15 Send syslog-ng mailing list submissions to syslog-ng(a)lists.balabit.hu To subscribe or unsubscribe via the World Wide Web, visit https://lists.balabit.hu/mailman/listinfo/syslog-ng or, via email, send a message with subject or body 'help' to syslog-ng-request(a)lists.balabit.hu You can reach the person managing the list at syslog-ng-owner(a)lists.balabit.hu When replying, please edit your Subject line so it is more specific than "Re: Contents of syslog-ng digest..." Today's Topics: 1. Re: use loggen to insert content of a file into local log file (Fabien Wernli) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Mar 2019 09:03:34 +0100 From: Fabien Wernli <wernli(a)in2p3.fr> To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu> Subject: Re: [syslog-ng] use loggen to insert content of a file into local log file Message-ID: <20190307080334.n3xc2q5nq2kfr7wv(a)ccfawe.in2p3.fr> Content-Type: text/plain; charset=iso-8859-1 On Wed, Mar 06, 2019 at 01:35:02PM +0000, Lin, Victor wrote: > Could anyone can give an example of using loggen to insert content of a file into a local log file ? you could use loggen to send to a specific port, on which syslog-ng would be listening, then create a log statement sendîng to that file, e.g. off the top of my head: log { source { syslog( port(1234) ); }; destination { file( '/tmp/loggen.log' ); }; }; loggen -D "blah blah blah" localhost 1234 ------------------------------ Subject: Digest Footer _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng ------------------------------ End of syslog-ng Digest, Vol 167, Issue 15 ****************************************** _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

Insider 2019-03: syslog-ng 3.20.1; fail2ban; HTTP source; container tools; UDP; Conferences & Webinars
by Czanik, Péter 14 Mar '19

14 Mar '19

Dear syslog-ng users, This is the 73rd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS syslog-ng 3.20.1 released ------------------------- Version 3.20.1 of syslog-ng was released. It adds persist-tool to manipulate persists files, a collectd destination, parsers for Netskope and Websense logs, and list support to JSON and XML. Naturally, bug fixes and many more changes were under the hood as well. There are some developer facing improvements, too, such as the fact that Python developers can now generate internal() log messages. For a complete list of changes with links to individual pull requests describing the changes in more detail, check https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.20.1 Documentation for most of the new features is now available online at https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-ed… Visualizing Fail2ban logs in Kibana ----------------------------------- In his previous syslog-ng blog post, Balage wrote about how you can enrich Fail2ban logs with GeoIP metadata and other data parsed from the logs. In this post he will show you how you can use syslog-ng to send the logs into Elasticsearch and how visualizing Fail2ban logs in Kibana can show you where the failed login attempts come from. https://balagetech.com/visualizing-fail2ban-logs-in-kibana/ Creating an HTTP source for syslog-ng in Python ----------------------------------------------- HTTP is quickly becoming the universal transport protocol of the Internet. Nowadays even DNS over HTTPS implementations are available. There is no HTTP source implemented in C for syslog-ng, but starting with syslog-ng version 3.18, you can write new source drivers for syslog-ng in Python. While performance is not as good as it would be using C, you gain flexibility and ease of implementation by using Python. From this blog post you can learn how to create a basic HTTP source for syslog-ng in Python. https://www.syslog-ng.com/community/b/blog/posts/creating-an-http-source-fo… Building and running a syslog-ng container using the latest tools ----------------------------------------------------------- >From this blog you can learn the basics of skopeo, buildah and podman through the examples of a syslog-ng container. These tools come from Red Hat, replacing and extending functionality of the docker daemon without the need to run a “big fat daemon” on the hosts. The architectural redesign is closer to the UNIX philosophy and here is no single point of failure. https://www.syslog-ng.com/community/b/blog/posts/building-and-running-a-sys… Improved log collection over UDP -------------------------------- “I'd tell you the joke about UDP, but you might not get it.” This old joke perfectly summarizes UDP. There is no guarantee (frankly, not even a real effort) that data sent over UDP ever reaches the receiving end. Still, a surprisingly large number of syslog(-ng) users still keep using UDP as their transport protocol. The introduction of the so-reuseport() option for the UDP source in syslog-ng 3.19 is for those people who, for policy or other reasons, can not switch to TCP logging but still want to make UDP log reception as reliable as possible. https://www.syslog-ng.com/community/b/blog/posts/improved-log-collection-ov… CONFERENCES * DevOps Pro talk: Syslog-ng for DevOps: Customized Logging with Python ( https://devopspro.lt/peter-czanik/ ) WEBINARS You can watch our past webinars: * Got a Hungry Splunk? Feed it Smartly with syslog-ng: https://www.brighttalk.com/webcast/16207/350610 Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Trigger dynamic action in syslog-ng
by Jim Hendrick 08 Mar '19

08 Mar '19

I was wondering if anyone has used syslog-ng to trigger some dynamic action based on logs. For example, if a certain threshold of messages happens in a time window, send an alert. LIke suppress () but more general actions. Or if a specific event happens, send *.debug from that system for 5 minutes. Or run a program to collect system data and send it along based on some condition. Not thinking SIEM functionality here, but maybe allow the log servers to be more dynamic around what actions they take for basic things. Thoughts? Thanks. Jim

3 3

Problems parsing Cisco syslogs
by N. Max Pierson 08 Mar '19

08 Mar '19

Hi List, I have been trying to get something in place that can parse syslogs from various Cisco devices. The message format is almost the same with a few exceptions. Here is what I have tried and it works but now it has created another problem I do not know how to troubleshoot. So that I could see exactly what was being parsed, I disabled the default parsing using the below. source s_network { udp(ip(0.0.0.0) port(514) flags(no-parse)); }; rewrite r_cisco{ subst('^<\d+>(\d+:|:)\s+(\.\w+|\w+)\s+\d+\s+\d+\s\d+:\d+:\d+:\s|^<\d+>:\s+\d+\s+\w+\s+\d+\s+\d+:\d+:\d+\s\w+:\s|^<\d+>(\d+:|:)\s', "", value("MESSAGE"), type("pcre"), flags("ignore-case")); }; destination d_mysql { sql(type(mysql) host("127.0.0.1") username("syslog-ng") password("password") database("syslog") table("messages_${HOST}") columns("datetime datetime", "host varchar(50)", "level varchar(10)", "message text") values("${R_YEAR}-${R_MONTH}-${R_DAY} ${R_HOUR}:${R_MIN}:${R_SEC}", "${HOST}", "${LEVEL}", "${MESSAGE}") indexes("datetime", "level") ); }; log { source(s_network); rewrite(r_cisco); destination(d_mysql); }; This works perfectly as it formats the message as I want and covers IOS and NX-OS devices. The problem is when I turned off the default parser, now all of my logs show "notice" in the $LEVEL macro and doesn't reflect the real message header level. The $HOST macro still works fine however. Is this the expected behavior that the message header fields are not parsed as well as the $MESSAGE itself not being parsed? How can map the header level field properly to the $LEVEL marco if I disable the default parser? Regards, Max

7 20

use loggen to insert content of a file into local log file
by Lin, Victor 07 Mar '19

07 Mar '19

Dear All, Could anyone can give an example of using loggen to insert content of a file into a local log file ? Thank you very much for you great help! VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

replacing log statements
by Sergey 06 Mar '19

06 Mar '19

Hello. "allow-config-dups" allow to replace some objects. As I understand log objects cann't have identifier and cann't be replaced therefore. Is it true or I wrong? It would be nice to be able to replace log object also. -- Regards, Sergey

4 5

Check if field in message and use default if not.
by Ronald Fenner 05 Mar '19

05 Mar '19

I generate a Kafka topic to send the message to by doing: topic("${topic}.${environment}") What I'd like to do if the field wasn't in the json message to provide a default value. Im looking for like a tertiary operator to use In the topic or perhaps a rewrite rule. I see the conditional expressions but from the docs it doesn't look like I can use it in the topic or a rewrite rule NOTE: My messages are json stings that get parsed and then imploded back to json as it's sent. Thanks Ronald Fenner Network Architect Game Circus LLC. rfenner(a)gamecircus.com

3 4

RFC 3195
by venkateswarlu vinjamuri 04 Mar '19

04 Mar '19

Hi All, I would like to know if there is any syslog-ng version that supports RFC-3195. If so, please let me know the version and any config related changes. Please also provide the links for the same. Regards Venkat

2 1

How to use regex in syslog-ng.conf
by Lin, Victor 04 Mar '19

04 Mar '19

Thanks a lot Kokan!!!!! I got the result :-) One more question For the following two %AAA-6-AAA_ACCOUNTING_MESSAGE: update:10.94.200.210@pts/0:syslogtest:deleted user victor %AAA-6-AAA_ACCOUNTING_MESSAGE: update:10.94.201.173@pts/0:syslogtest:added user victor I try to use the following regex to match the text in red color, it shows works. AAA-6-AAA_ACCOUNTING_MESSAGE: [a-zA-Z0-9]+:[0-9.]+@[a-zA-Z0-9]+\/[a-zA-Z0-9]+:[a-zA-Z0-9]+:[a-zA-Z]+ user Is there a simple way to math " update:10.94.200.210@pts/0:syslogtest:" Thank you very much again‼‼! VL -----Original Message----- From: syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of syslog-ng-request(a)lists.balabit.hu Sent: 2019, March, 01 7:00 AM To: syslog-ng(a)lists.balabit.hu Subject: syslog-ng Digest, Vol 167, Issue 1 Send syslog-ng mailing list submissions to syslog-ng(a)lists.balabit.hu<mailto:syslog-ng@lists.balabit.hu> To subscribe or unsubscribe via the World Wide Web, visit https://lists.balabit.hu/mailman/listinfo/syslog-ng or, via email, send a message with subject or body 'help' to syslog-ng-request(a)lists.balabit.hu<mailto:syslog-ng-request@lists.balabit.hu> You can reach the person managing the list at syslog-ng-owner(a)lists.balabit.hu<mailto:syslog-ng-owner@lists.balabit.hu> When replying, please edit your Subject line so it is more specific than "Re: Contents of syslog-ng digest..." Today's Topics: 1. unofficial syslog-ng 3.20 packages for Debian/Ubuntu (Laszlo Budai) 2. Re: How to use regex in syslog-ng.conf (Péter) 3. Re: How to use regex in syslog-ng.conf (Fabien Wernli) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Mar 2019 10:09:03 +0000 From: Laszlo Budai <laszlo.budai(a)outlook.com<mailto:laszlo.budai@outlook.com>> To: Syslog-ng users' and developers' mailing list <syslog-ng(a)lists.balabit.hu<mailto:syslog-ng@lists.balabit.hu>> Subject: [syslog-ng] unofficial syslog-ng 3.20 packages for Debian/Ubuntu Message-ID: <VI1PR0601MB2237CC24E8908466F6ABC1B38E760(a)VI1PR0601MB2237.eurprd06.prod.outlook.com<mailto:VI1PR0601MB2237CC24E8908466F6ABC1B38E760@VI1PR0601MB2237.eurprd06.prod.outlook.com>> Content-Type: text/plain; charset="iso-8859-1" Hi, syslog-ng 3.20.1[1] packages are available in OBS repo[2]. List of supported OSs: * Debian 8.0 * Debian 9.0 [including armv7l] * Ubuntu 14.04 * Ubuntu 16.04 * Ubuntu 16.10 * Ubuntu 17.04 * Ubuntu 17.10 * Ubuntu 18.04 * Ubuntu 18.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-get install syslog-ng-core` Links -------- [1] https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.20.1 [2] https://build.opensuse.org/package/show/home:laszlo_budai:syslog-ng/syslog-… regards, Laszlo Budai -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190301/2e2934b4/a…> ------------------------------ Message: 2 Date: Fri, 1 Mar 2019 11:34:00 +0100 From: Péter, Kókai <peter.kokai(a)oneidentity.com<mailto:peter.kokai@oneidentity.com>> To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu<mailto:syslog-ng@lists.balabit.hu>> Subject: Re: [syslog-ng] How to use regex in syslog-ng.conf Message-ID: <CABxQCpjDdn3JSwA1btkF7GZGLX_De0qGq+i9GtOcz8JWjhgpzA(a)mail.gmail.com<mailto:CABxQCpjDdn3JSwA1btkF7GZGLX_De0qGq+i9GtOcz8JWjhgpzA@mail.gmail.com>> Content-Type: text/plain; charset="utf-8" Hello, Based on your example one possible solution could be: match("cmd=username [a-z]+ privilege 15" value("MESSAGE")); You could also check out the syslog-ng administrator guide, it covers a lot of possibilities: https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edi… -- Kokan On Thu, Feb 28, 2019 at 3:50 PM Lin, Victor <victor.lin(a)rbc.com<mailto:victor.lin@rbc.com>> wrote: > Dear all, > > I am trying to use regex in syslog-ng.conf without success L > > Below is from my filter > > match("cmd=username toto privilege 15", value("MESSAGE")); > > could you please let me know how could I replace username toto with > regex ? tried /w+ , but didn’t passing through > > Thank you very much for your instruction! > > VL > > > > > ______________________________________________________________________ > _ > > If you received this email in error, please advise the sender (by > return email or otherwise) immediately. You have consented to receive > the attached electronically at the above-noted email address; please > retain a copy of this confirmation for future reference. > > Si vous recevez ce courriel par erreur, veuillez en aviser > l'expéditeur immédiatement, par retour de courriel ou par un autre > moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par > voie électronique à l'adresse courriel indiquée ci-dessus; veuillez > conserver une copie de cette confirmation pour les fins de reference future. > > > ______________________________________________________________________ > ________ Member info: > https://lists.balabit.hu/mailman/listinfo/syslog-ng > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > FAQ: http://www.balabit.com/wiki/syslog-ng-faq > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190301/7921ceb3/a…> ------------------------------ Message: 3 Date: Fri, 1 Mar 2019 12:50:50 +0100 From: Fabien Wernli <wernli(a)in2p3.fr<mailto:wernli@in2p3.fr>> To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu<mailto:syslog-ng@lists.balabit.hu>> Subject: Re: [syslog-ng] How to use regex in syslog-ng.conf Message-ID: <20190301115050.hs3d5vjf27a7lwfe(a)ccfawe.in2p3.fr<mailto:20190301115050.hs3d5vjf27a7lwfe@ccfawe.in2p3.fr>> Content-Type: text/plain; charset="iso-8859-1" On Fri, Mar 01, 2019 at 11:34:00AM +0100, Péter, Kókai wrote: > Hello, > > Based on your example one possible solution could be: > match("cmd=username [a-z]+ privilege 15" value("MESSAGE")); > > You could also check out the syslog-ng administrator guide, it covers > a lot of possibilities: > https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-sourc > e-edition/3.20/administration-guide/63#TOPIC-1122022 also, prefer single quotes over double quotes: will make escaping easier -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2801 bytes Desc: not available URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190301/21433a6a/a…> ------------------------------ Subject: Digest Footer _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu<mailto:syslog-ng@lists.balabit.hu> https://lists.balabit.hu/mailman/listinfo/syslog-ng ------------------------------ End of syslog-ng Digest, Vol 167, Issue 1 ***************************************** _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

How to send test syslog message to a local log file
by Lin, Victor 04 Mar '19

04 Mar '19

Dear All, Could you please let me know can I do this? Would like to insert the following test syslog messages Feb 5 10:16:03 10.2.3.4 2019 Feb 5 15:16:03.560 UTC: %AUTHPRIV-5-SYSTEM_MSG: New user added with username victor - securityd Feb 5 10:16:03 10.2.3.4 2019 Feb 5 15:16:03.561 UTC: %AAA-6-AAA_ACCOUNTING_MESSAGE: update:10.24.3.46@pts/0:syslogtest:added user victor Feb 5 10:16:03 10.2.3.4 2019 Feb 5 15:16:03.561 UTC: %TACACS-6-TACACS_ACCOUNTING_MESSAGE: update: 10.24.3.46@pts/0: syslogtest: added user victor to a local log file /MyApp/syslog-ng/output/test.log Thank you so much for your help! VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

3.19.1 and "make check"
by Sergey 03 Mar '19

03 Mar '19

Hello. How can I use unit tests when building? As I see $ ./configure --help | grep "unit test" --enable-valgrind Whether to enable Valgrind on the unit tests I should enable "valgrind". Ok, I attempt to do it but it unsuccesful. valgrind is detected: checking whether to enable Valgrind on the unit tests... checking for valgrind... valgrind yes checking for Valgrind tool memcheck... memcheck checking for Valgrind tool helgrind... helgrind checking for Valgrind tool drd... drd checking for Valgrind tool exp-sgcheck... exp-sgcheck but isn't used: Test dependencies: Criterion : no Unit tests : no And expected: $ make check Makefile:21717: *** "Unit tests disabled". Stop. Or is availability of Criterion a necessary condition also ? btw, what is the "Criterion"? Is it https://github.com/Snaipe/Criterion ? -- Regards, Sergey

2 1

How to add a keyword into syslog
by Lin, Victor 02 Mar '19

02 Mar '19

Dear All, I would like to add the sources of syslog (for example CiscoIOS, CiscoNXOS, Arista) when I forward the received syslog to remote server, Could you please let me know how to do it? Below is from my current syslog-ng.conf destination d_Arista_logs { file("/MyApp/syslog-ng/output/Arista.log"); network("10.2.234.21" port(514) transport(udp) spoof_source(yes)); }; VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

1 0

How to use regex in syslog-ng.conf
by Lin, Victor 01 Mar '19

01 Mar '19

Dear all, I am trying to use regex in syslog-ng.conf without success :( Below is from my filter match("cmd=username toto privilege 15", value("MESSAGE")); could you please let me know how could I replace username toto with regex ? tried /w+ , but didn't passing through Thank you very much for your instruction! VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

3 2

unofficial syslog-ng 3.20 packages for Debian/Ubuntu
by Laszlo Budai 01 Mar '19

01 Mar '19

Hi, syslog-ng 3.20.1[1] packages are available in OBS repo[2]. List of supported OSs: * Debian 8.0 * Debian 9.0 [including armv7l] * Ubuntu 14.04 * Ubuntu 16.04 * Ubuntu 16.10 * Ubuntu 17.04 * Ubuntu 17.10 * Ubuntu 18.04 * Ubuntu 18.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-get install syslog-ng-core` Links -------- [1] https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.20.1 [2] https://build.opensuse.org/package/show/home:laszlo_budai:syslog-ng/syslog-… regards, Laszlo Budai

1 0

OSE 3.20.1
by Szakacs, Attila 28 Feb '19

28 Feb '19

3.20.1Features - Add persist-tool (#2511 <https://github.com/balabit/syslog-ng/pull/2511>) - Collectd destination (#1433 <https://github.com/balabit/syslog-ng/pull/1433>) - Config reload status feedback (#2367 <https://github.com/balabit/syslog-ng/pull/2367>) - Netskope parser (#2541 <https://github.com/balabit/syslog-ng/pull/2541> ) - Websense parser (#2471 <https://github.com/balabit/syslog-ng/pull/2471> ) - Json list support (#2536 <https://github.com/balabit/syslog-ng/pull/2536>) - Xml-parser: add list support (#2544 <https://github.com/balabit/syslog-ng/pull/2544>) Bugfixes - DNS memory leak/segfault fix (#2500 <https://github.com/balabit/syslog-ng/pull/2500>) - Elasticsearch2: fix bulk send for client-mode("http") (#2478 <https://github.com/balabit/syslog-ng/pull/2478>) - Few leak fix (#2563 <https://github.com/balabit/syslog-ng/pull/2563>) - Filter-re: ref/unref NVTable around regex eval (#2494 <https://github.com/balabit/syslog-ng/pull/2494>) - Fix allowing negative version number in config (#2548 <https://github.com/balabit/syslog-ng/pull/2548>) - Fix app-parser() per reload memory leak (#2469 <https://github.com/balabit/syslog-ng/pull/2469>) - Fix non-reliable disk-queue truncating problem on load (#2406 <https://github.com/balabit/syslog-ng/pull/2406>) - Fix threaded source/destination crash when reverting configuration ( #2555 <https://github.com/balabit/syslog-ng/pull/2555>) - Http: add missing free for self->body_template (#2558 <https://github.com/balabit/syslog-ng/pull/2558>) - Java, elasticsearch2, explicit unsupport for named templates (#2534 <https://github.com/balabit/syslog-ng/pull/2534>) - Loggen: parameter handling (#2477 <https://github.com/balabit/syslog-ng/pull/2477>) - Python-source: fix crash when posting from python thread (#2533 <https://github.com/balabit/syslog-ng/pull/2533>) - Read acknowledgments send by Riemann (#2523 <https://github.com/balabit/syslog-ng/pull/2523>) - Redis, Riemann: fix ref/unref-ing templates (#2514 <https://github.com/balabit/syslog-ng/pull/2514>, #2530 <https://github.com/balabit/syslog-ng/pull/2530>) - Syslog-ng@default: use pid file location on control socket (#2489 <https://github.com/balabit/syslog-ng/pull/2489>) - Threaded-dest: Fix integer overflow (#2512 <https://github.com/balabit/syslog-ng/pull/2512>) - Threaded-dest: make persist_name local (#2516 <https://github.com/balabit/syslog-ng/pull/2516>) - Xml/geoip2: make prefix optional (#2538 <https://github.com/balabit/syslog-ng/pull/2538>) Other changes - Autotools, cmake: add detection for pylint, nosetests (#2537 <https://github.com/balabit/syslog-ng/pull/2537>,#2564 <https://github.com/balabit/syslog-ng/pull/2564>) - Autotools: relaxing python dependency requirement (#2472 <https://github.com/balabit/syslog-ng/pull/2472>) - Cfg-parser: printing error positions in case of parse failure (#2455 <https://github.com/balabit/syslog-ng/pull/2455>) - Cmake: add missing detections (#2510 <https://github.com/balabit/syslog-ng/pull/2510>) - Collect-cov.sh: make coverage should work with lcov in bionic (#2515 <https://github.com/balabit/syslog-ng/pull/2515>) - Configure: fix "--with-docbook*" option usage (#2465 <https://github.com/balabit/syslog-ng/pull/2465>) - Custom LGTM.com query for detecting uses of gmtime that are not covered by a lock (#2413 <https://github.com/balabit/syslog-ng/pull/2413> ) - Fix static uClibc-ng support (#2501 <https://github.com/balabit/syslog-ng/pull/2501>) - Format non-literal fixes (#2567 <https://github.com/balabit/syslog-ng/pull/2567>) - Grammar: remove the pragma less include (#2550 <https://github.com/balabit/syslog-ng/pull/2550>) - Http-worker: refactor & fix curl_easy_getinfo error message (#2527 <https://github.com/balabit/syslog-ng/pull/2527>) - Lib/compat: replace strcasestr() implementation (#2482 <https://github.com/balabit/syslog-ng/pull/2482>) - Libtest: Adding stopwatch.h into libtest_HEADERS list (#2553 <https://github.com/balabit/syslog-ng/pull/2553>) - Packaging: fix the description of mod-examples (#2522 <https://github.com/balabit/syslog-ng/pull/2522>) - Python-debugger: fix macro completion (#2439 <https://github.com/balabit/syslog-ng/pull/2439>) - Python, java destination add already introduced retry (#2559 <https://github.com/balabit/syslog-ng/pull/2559>) - Remove elastic v1 support (#2554 <https://github.com/balabit/syslog-ng/pull/2554>) - Simplify libtest queue utils (#2556 <https://github.com/balabit/syslog-ng/pull/2556>) - Syslog-ng.8.xml: remove unneeded default-modules section (#2475 <https://github.com/balabit/syslog-ng/pull/2475>) - Travis: use the latest Bison version (macOS) (#2529 <https://github.com/balabit/syslog-ng/pull/2529>) - Various fixes for issues reported by LGTM (#2524 <https://github.com/balabit/syslog-ng/pull/2524>) Notes to the developers - Example-msg-generator: num option (#2565 <https://github.com/balabit/syslog-ng/pull/2565>) - Own grammar support in generator plugin (#2552 <https://github.com/balabit/syslog-ng/pull/2552>) - ProtoClient: provide process_in function to logwriter (#2468 <https://github.com/balabit/syslog-ng/pull/2468>) - Pytest_framework: eliminating __registered_instances, exposing SyslogNgCtl to user api (#2503 <https://github.com/balabit/syslog-ng/pull/2503>) - Pytest_framework: MessageReader: Explain the local context around python asserts (#2507 <https://github.com/balabit/syslog-ng/pull/2507>) - Pytest_framework: support for implicit groups in config.create_logpath (#2490 <https://github.com/balabit/syslog-ng/pull/2490>) - Pytest: Renaming pytest_framework to python_functional (#2542 <https://github.com/balabit/syslog-ng/pull/2542>) - Python-destination: send can return worker_insert_result_t, flush support (#2487 <https://github.com/balabit/syslog-ng/pull/2487>) - Python: internal() source exposed via syslogng.Logger (#2505 <https://github.com/balabit/syslog-ng/pull/2505>) - Remove unused submodules (#2525 <https://github.com/balabit/syslog-ng/pull/2525>) - Simpler names for WORKER_INSERT_RESULT_T in language bindings (#2506 <https://github.com/balabit/syslog-ng/pull/2506>) - Split xml-parser into xml-parser and xml-scanner (#2459 <https://github.com/balabit/syslog-ng/pull/2459>) 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, Andrej Valek, Antal Nemes, Attila Szakacs, Balazs Scheidler, Bas van Schaik, Fᴀʙɪᴇɴ Wᴇʀɴʟɪ, Gabor Nagy, Laszlo Boszormenyi, Laszlo Budai, Lorand Muzamel, László Várady, Mehul Prajapati, Naveen Revanna, Peter Czanik, Peter Kokai, Romain Tartière, Stephen, Terez Nemes, Norbert Takács, Soubhik Chakraborty, NottyRu, Chris Packham. https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.20.1 Best regards, Attila Szakacs

1 0

Re: [syslog-ng] syslog-ng Digest, Vol 166, Issue 14
by Lin, Victor 27 Feb '19

27 Feb '19

Thanks a lot Kokan!!!!! After I put the individual name for each persist-name, no error any more :-). Have a great day! VL -----Original Message----- From: syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of syslog-ng-request(a)lists.balabit.hu Sent: 2019, February, 27 3:25 AM To: syslog-ng(a)lists.balabit.hu Subject: syslog-ng Digest, Vol 166, Issue 14 Send syslog-ng mailing list submissions to syslog-ng(a)lists.balabit.hu To subscribe or unsubscribe via the World Wide Web, visit https://lists.balabit.hu/mailman/listinfo/syslog-ng or, via email, send a message with subject or body 'help' to syslog-ng-request(a)lists.balabit.hu You can reach the person managing the list at syslog-ng-owner(a)lists.balabit.hu When replying, please edit your Subject line so it is more specific than "Re: Contents of syslog-ng digest..." Today's Topics: 1. Re: syslog-ng.conf error (Péter) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Feb 2019 09:24:50 +0100 From: Péter, Kókai <peter.kokai(a)oneidentity.com> To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu> Subject: Re: [syslog-ng] syslog-ng.conf error Message-ID: <CABxQCpj_YRnzzkskbCoi_CULFEuNskO=X1OpsKrQ0T=0V3crug(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, In order to point out the exact location of issue, you have to share your configuration. If you do not want to share it, there is two hint to find it yourself: 1) The message "Error checking the uniqueness of the persist names, please override it with persist-name option. Shutting" actually truncated (possible by journalctl), and the full version should contain the location of the item that has conflicting persist-name. 2) About persist-name, syslog-ng uses a persist file to store some information (for example to keep data between restart/reload). Date is stored in that file via its key, those keys are generated based on the configuration item options (for file source it could be the path of the file, etc...), sometimes it could collide with other configured item and syslog-ng cannot resolve the name collition; but the user could with specifying the *persist-name* option, which override the default generated option. An example: source s { file("/tmp/file" persist-name("my-tmp-file") ); }; -- Kokan On Tue, Feb 26, 2019 at 9:57 PM Lin, Victor <victor.lin(a)rbc.com> wrote: > Dear all, > > I am a newbie for syslog-ng J, could you please help me to figure > out my issues with syslog-ng.conf ? > > After modified syslog-ng.conf by adding more source, destination and > filter, try to restart syslog-ng by /etc/init.d/syslog-ng restart > > Got the following error > ********************************************* > # */etc/init.d/syslog-ng restart* > Restarting syslog-ng (via systemctl): Job for syslog-ng.service > failed because the control process exited with error code. See > "systemctl status syslog-ng.service" and "journalctl -xe" for details. > [FAILED] > > **************************************** > # *systemctl status syslog-ng.service* â— syslog-ng.service - LSB: > start and stop syslog-NG daemon > Loaded: loaded (/etc/rc.d/init.d/syslog-ng; bad; vendor preset: > enabled > ) > Active: failed (Result: exit-code) since Tue 2019-02-26 15:17:04 > EST; 30s ago > Docs: man:systemd-sysv-generator(8) > Process: 53303 ExecStop=/etc/rc.d/init.d/syslog-ng stop > (code=exited, > status=0/SUCCESS) > Process: 292500 ExecReload=/etc/rc.d/init.d/syslog-ng reload > (code=exited, status=0/SUCCESS) > Process: 53320 ExecStart=/etc/rc.d/init.d/syslog-ng start > (code=exited, > status=1/FAILURE) > Main PID: 116276 > > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083451] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083503] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083554] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.250946] Error checking the uniqueness of the > persist names, please override it with persist-name op...conf:131:9' > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.250984] Error checking the uniqueness of the > persist names, please override it with persist-name op...conf:132:9' > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [FAILED] Feb 26 15:17:04 > ABCD.com systemd[1]: syslog-ng.service: control process exited, > code=exited status=1 Feb 26 15:17:04 ABCD.com systemd[1]: Failed to > start LSB: start and stop syslog-NG daemon. > Feb 26 15:17:04 ABCD.com systemd[1]: Unit syslog-ng.service entered > failed state. > Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service failed. > Hint: Some lines were ellipsized, use -l to show in full. > > > # *journalctl -xe* > Feb 26 15:05:28 ABCD.com puppet-agent[48945]: Could not send report: > getaddrinfo: No address associated with hostname Feb 26 15:09:40 > ABCD.com sshd[51578]: pam_sss(sshd:auth): authentication success; > logname= uid=0 euid=0 tty=ssh ruser= rhost= > m3vrb434.rbc1.royalbank.com user=VL51 Feb 26 15:09:40 ABCD.com > sshd[51578]: Accepted password for VL51 from > 10.94.201.168 port 62031 ssh2 > Feb 26 15:10:02 ABCD.com crond[51740]: pam_unix(crond:account): > password for user root will expire in 8 days Feb 26 15:10:02 ABCD.com > crond[51741]: pam_unix(crond:account): password for user root will > expire in 8 days Feb 26 15:10:02 ABCD.com crond[51740]: > pam_unix(crond:session): session opened for user root by (uid=0) Feb > 26 15:10:02 ABCD.com crond[51741]: pam_unix(crond:session): session > opened for user root by (uid=0) Feb 26 15:10:02 ABCD.com CROND[51743]: > (root) CMD (/usr/lib64/sa/sa1 1 1) Feb 26 15:10:02 ABCD.com > CROND[51742]: (root) CMD (/bin/printf > '\n******************************************************************* > ****************\n\n > For filesize:' >> /app/ > Feb 26 15:10:02 ABCD.com CROND[51740]: pam_unix(crond:session): > session closed for user root Feb 26 15:10:02 ABCD.com sendmail[51759]: > x1QKA2Bw051759: from=root, size=1598, class=-60, nrcpts=1, msgid=< > *201902262010.x1QKA2Bw051759(a)ABCD.com* > <201902262010.x1QKA2Bw051759(a)ABCD.com>>, relay=root@localho Feb 26 > 15:10:02 ABCD.com sendmail[51759]: x1QKA2Bw051759: to=root, > ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, > pri=139598, relay=[127.0.0.1] [127.0.0.1], Feb 26 15:10:02 ABCD.com > CROND[51741]: pam_unix(crond:session): session closed for user root > Feb 26 15:10:50 ABCD.com sudo[51905]: VL51 : TTY=pts/0 ; > PWD=/app/syslog-ng/custom/conf ; USER=root ; COMMAND=/usr/bin/su - Feb > 26 15:10:50 ABCD.com su[51909]: (to root) VL51 on pts/0 Feb 26 > 15:10:50 ABCD.com su[51909]: pam_unix(su-l:session): session opened > for user root by VL51(uid=0) Feb 26 15:15:01 ABCD.com crond[52764]: > pam_unix(crond:account): password for user root will expire in 8 days > Feb 26 15:15:01 ABCD.com crond[52764]: pam_unix(crond:session): > session opened for user root by (uid=0) Feb 26 15:15:01 ABCD.com > CROND[52765]: (root) CMD (/usr/sbin/logrotate > /app/syslog-ng/custom/conf/syslog-ng-rotate.conf) > Feb 26 15:15:01 ABCD.com CROND[52764]: pam_unix(crond:session): > session closed for user root Feb 26 15:17:02 ABCD.com polkitd[1117]: > Registered Authentication Agent for unix-process:53295:2185270730 > (system bus name :1.268 [/usr/bin/pkttyagent --notify-fd 5 > --fallback], Feb 26 15:17:02 ABCD.com systemd[1]: Stopping LSB: start > and stop syslog-NG daemon... > -- Subject: Unit syslog-ng.service has begun shutting down > -- Defined-By: systemd > -- Support: > *http://lists.freedesktop.org/mailman/listinfo/systemd-devel* > <http://lists.freedesktop.org/mailman/listinfo/systemd-devel> > -- > -- Unit syslog-ng.service has begun shutting down. > Feb 26 15:17:02 ABCD.com supervise/syslog-ng[116275]: Daemon exited > gracefully, not restarting; exitcode='0' > Feb 26 15:17:03 ABCD.com syslog-ng[53303]: Stopping syslog-ng: [ OK > ] Feb 26 15:17:03 ABCD.com systemd[1]: Starting LSB: start and stop > syslog-NG daemon... > -- Subject: Unit syslog-ng.service has begun start-up > -- Defined-By: systemd > -- Support: > *http://lists.freedesktop.org/mailman/listinfo/systemd-devel* > <http://lists.freedesktop.org/mailman/listinfo/systemd-devel> > -- > -- Unit syslog-ng.service has begun starting up. > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: Starting syslog-ng: > [2019-02-26T15:17:04.082875] WARNING: With use-dns(no), dns-cache() > will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com > syslog-ng[53320]: [2019-02-26T15:17:04.083333] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083396] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083451] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083503] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.083554] > WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.250946] Error checking the uniqueness of the > persist names, please override it with persist-name option. Shutting > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: > [2019-02-26T15:17:04.250984] Error checking the uniqueness of the > persist names, please override it with persist-name option. Shutting > Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [FAILED] Feb 26 15:17:04 > ABCD.com systemd[1]: syslog-ng.service: control process exited, > code=exited status=1 Feb 26 15:17:04 ABCD.com systemd[1]: Failed to > start LSB: start and stop syslog-NG daemon. > -- Subject: Unit syslog-ng.service has failed > -- Defined-By: systemd > -- Support: > *http://lists.freedesktop.org/mailman/listinfo/systemd-devel* > <http://lists.freedesktop.org/mailman/listinfo/systemd-devel> > -- > -- Unit syslog-ng.service has failed. > -- > -- The result is failed. > Feb 26 15:17:04 ABCD.com systemd[1]: Unit syslog-ng.service entered > failed state. > Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service failed. > Feb 26 15:17:04 ABCD.com polkitd[1117]: Unregistered Authentication > Agent for unix-process:53295:2185270730 (system bus name :1.268, > object path /org/freedesktop/PolicyKit1/Auth Feb 26 15:20:01 ABCD.com > crond[53909]: pam_unix(crond:account): password for user root will > expire in 8 days Feb 26 15:20:01 ABCD.com crond[53908]: > pam_unix(crond:account): password for user root will expire in 8 days > Feb 26 15:20:01 ABCD.com crond[53909]: pam_unix(crond:session): > session opened for user root by (uid=0) Feb 26 15:20:01 ABCD.com > crond[53908]: pam_unix(crond:session): session opened for user root by > (uid=0) Feb 26 15:20:01 ABCD.com CROND[53910]: (root) CMD > (/usr/lib64/sa/sa1 1 1) Feb 26 15:20:01 ABCD.com CROND[53911]: (root) > CMD (/bin/printf > '\n******************************************************************* > ****************\n\n > For filesize:' >> /app/ > Feb 26 15:20:01 ABCD.com CROND[53908]: pam_unix(crond:session): > session closed for user root Feb 26 15:20:01 ABCD.com sendmail[53926]: > x1QKK1vA053926: from=root, size=1805, class=-60, nrcpts=1, msgid=< > *201902262020.x1QKK1vA053926(a)ABCD.com* > <201902262020.x1QKK1vA053926(a)ABCD.com>>, relay=root@localho Feb 26 > 15:20:01 ABCD.com sendmail[53926]: x1QKK1vA053926: to=root, > ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, > pri=139805, relay=[127.0.0.1] [127.0.0.1], Feb 26 15:20:01 ABCD.com > CROND[53909]: pam_unix(crond:session): session closed for user root > > > Thank you very much for your expertize and instruction!!!!! > > *VL* > > > > > > > ______________________________________________________________________ > _ > > If you received this email in error, please advise the sender (by > return email or otherwise) immediately. You have consented to receive > the attached electronically at the above-noted email address; please > retain a copy of this confirmation for future reference. > > Si vous recevez ce courriel par erreur, veuillez en aviser > l'expéditeur immédiatement, par retour de courriel ou par un autre > moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par > voie électronique à l'adresse courriel indiquée ci-dessus; veuillez > conserver une copie de cette confirmation pour les fins de reference future. > > > ______________________________________________________________________ > ________ Member info: > https://lists.balabit.hu/mailman/listinfo/syslog-ng > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > FAQ: http://www.balabit.com/wiki/syslog-ng-faq > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190227/351df70d/a…> ------------------------------ Subject: Digest Footer _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng ------------------------------ End of syslog-ng Digest, Vol 166, Issue 14 ****************************************** _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

1 0

syslog-ng.conf error
by Lin, Victor 27 Feb '19

27 Feb '19

Dear all, I am a newbie for syslog-ng :), could you please help me to figure out my issues with syslog-ng.conf ? After modified syslog-ng.conf by adding more source, destination and filter, try to restart syslog-ng by /etc/init.d/syslog-ng restart Got the following error ********************************************* # /etc/init.d/syslog-ng restart Restarting syslog-ng (via systemctl): Job for syslog-ng.service failed because the control process exited with error code. See "systemctl status syslog-ng.service" and "journalctl -xe" for details. [FAILED] **************************************** # systemctl status syslog-ng.service â- syslog-ng.service - LSB: start and stop syslog-NG daemon Loaded: loaded (/etc/rc.d/init.d/syslog-ng; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-02-26 15:17:04 EST; 30s ago Docs: man:systemd-sysv-generator(8) Process: 53303 ExecStop=/etc/rc.d/init.d/syslog-ng stop (code=exited, status=0/SUCCESS) Process: 292500 ExecReload=/etc/rc.d/init.d/syslog-ng reload (code=exited, status=0/SUCCESS) Process: 53320 ExecStart=/etc/rc.d/init.d/syslog-ng start (code=exited, status=1/FAILURE) Main PID: 116276 Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083451] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083503] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083554] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.250946] Error checking the uniqueness of the persist names, please override it with persist-name op...conf:131:9' Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.250984] Error checking the uniqueness of the persist names, please override it with persist-name op...conf:132:9' Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [FAILED] Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service: control process exited, code=exited status=1 Feb 26 15:17:04 ABCD.com systemd[1]: Failed to start LSB: start and stop syslog-NG daemon. Feb 26 15:17:04 ABCD.com systemd[1]: Unit syslog-ng.service entered failed state. Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service failed. Hint: Some lines were ellipsized, use -l to show in full. # journalctl -xe Feb 26 15:05:28 ABCD.com puppet-agent[48945]: Could not send report: getaddrinfo: No address associated with hostname Feb 26 15:09:40 ABCD.com sshd[51578]: pam_sss(sshd:auth): authentication success; logname= uid=0 euid=0 tty=ssh ruser= rhost=m3vrb434.rbc1.royalbank.com user=VL51 Feb 26 15:09:40 ABCD.com sshd[51578]: Accepted password for VL51 from 10.94.201.168 port 62031 ssh2 Feb 26 15:10:02 ABCD.com crond[51740]: pam_unix(crond:account): password for user root will expire in 8 days Feb 26 15:10:02 ABCD.com crond[51741]: pam_unix(crond:account): password for user root will expire in 8 days Feb 26 15:10:02 ABCD.com crond[51740]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 26 15:10:02 ABCD.com crond[51741]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 26 15:10:02 ABCD.com CROND[51743]: (root) CMD (/usr/lib64/sa/sa1 1 1) Feb 26 15:10:02 ABCD.com CROND[51742]: (root) CMD (/bin/printf '\n***********************************************************************************\n\n For filesize:' >> /app/ Feb 26 15:10:02 ABCD.com CROND[51740]: pam_unix(crond:session): session closed for user root Feb 26 15:10:02 ABCD.com sendmail[51759]: x1QKA2Bw051759: from=root, size=1598, class=-60, nrcpts=1, msgid=<201902262010.x1QKA2Bw051759(a)ABCD.com<mailto:201902262010.x1QKA2Bw051759@ABCD.com>>, relay=root@localho Feb 26 15:10:02 ABCD.com sendmail[51759]: x1QKA2Bw051759: to=root, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=139598, relay=[127.0.0.1] [127.0.0.1], Feb 26 15:10:02 ABCD.com CROND[51741]: pam_unix(crond:session): session closed for user root Feb 26 15:10:50 ABCD.com sudo[51905]: VL51 : TTY=pts/0 ; PWD=/app/syslog-ng/custom/conf ; USER=root ; COMMAND=/usr/bin/su - Feb 26 15:10:50 ABCD.com su[51909]: (to root) VL51 on pts/0 Feb 26 15:10:50 ABCD.com su[51909]: pam_unix(su-l:session): session opened for user root by VL51(uid=0) Feb 26 15:15:01 ABCD.com crond[52764]: pam_unix(crond:account): password for user root will expire in 8 days Feb 26 15:15:01 ABCD.com crond[52764]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 26 15:15:01 ABCD.com CROND[52765]: (root) CMD (/usr/sbin/logrotate /app/syslog-ng/custom/conf/syslog-ng-rotate.conf) Feb 26 15:15:01 ABCD.com CROND[52764]: pam_unix(crond:session): session closed for user root Feb 26 15:17:02 ABCD.com polkitd[1117]: Registered Authentication Agent for unix-process:53295:2185270730 (system bus name :1.268 [/usr/bin/pkttyagent --notify-fd 5 --fallback], Feb 26 15:17:02 ABCD.com systemd[1]: Stopping LSB: start and stop syslog-NG daemon... -- Subject: Unit syslog-ng.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit syslog-ng.service has begun shutting down. Feb 26 15:17:02 ABCD.com supervise/syslog-ng[116275]: Daemon exited gracefully, not restarting; exitcode='0' Feb 26 15:17:03 ABCD.com syslog-ng[53303]: Stopping syslog-ng: [ OK ] Feb 26 15:17:03 ABCD.com systemd[1]: Starting LSB: start and stop syslog-NG daemon... -- Subject: Unit syslog-ng.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit syslog-ng.service has begun starting up. Feb 26 15:17:04 ABCD.com syslog-ng[53320]: Starting syslog-ng: [2019-02-26T15:17:04.082875] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083333] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083396] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083451] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083503] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.083554] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.250946] Error checking the uniqueness of the persist names, please override it with persist-name option. Shutting Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [2019-02-26T15:17:04.250984] Error checking the uniqueness of the persist names, please override it with persist-name option. Shutting Feb 26 15:17:04 ABCD.com syslog-ng[53320]: [FAILED] Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service: control process exited, code=exited status=1 Feb 26 15:17:04 ABCD.com systemd[1]: Failed to start LSB: start and stop syslog-NG daemon. -- Subject: Unit syslog-ng.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit syslog-ng.service has failed. -- -- The result is failed. Feb 26 15:17:04 ABCD.com systemd[1]: Unit syslog-ng.service entered failed state. Feb 26 15:17:04 ABCD.com systemd[1]: syslog-ng.service failed. Feb 26 15:17:04 ABCD.com polkitd[1117]: Unregistered Authentication Agent for unix-process:53295:2185270730 (system bus name :1.268, object path /org/freedesktop/PolicyKit1/Auth Feb 26 15:20:01 ABCD.com crond[53909]: pam_unix(crond:account): password for user root will expire in 8 days Feb 26 15:20:01 ABCD.com crond[53908]: pam_unix(crond:account): password for user root will expire in 8 days Feb 26 15:20:01 ABCD.com crond[53909]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 26 15:20:01 ABCD.com crond[53908]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 26 15:20:01 ABCD.com CROND[53910]: (root) CMD (/usr/lib64/sa/sa1 1 1) Feb 26 15:20:01 ABCD.com CROND[53911]: (root) CMD (/bin/printf '\n***********************************************************************************\n\n For filesize:' >> /app/ Feb 26 15:20:01 ABCD.com CROND[53908]: pam_unix(crond:session): session closed for user root Feb 26 15:20:01 ABCD.com sendmail[53926]: x1QKK1vA053926: from=root, size=1805, class=-60, nrcpts=1, msgid=<201902262020.x1QKK1vA053926(a)ABCD.com<mailto:201902262020.x1QKK1vA053926@ABCD.com>>, relay=root@localho Feb 26 15:20:01 ABCD.com sendmail[53926]: x1QKK1vA053926: to=root, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=139805, relay=[127.0.0.1] [127.0.0.1], Feb 26 15:20:01 ABCD.com CROND[53909]: pam_unix(crond:session): session closed for user root Thank you very much for your expertize and instruction!!!!! VL _______________________________________________________________________ If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference. Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.

2 1

Syslog-ng setup for both RFC3164 and RFC5124
by Carlan Philippe 27 Feb '19

27 Feb '19

Hi all, Is there a way to configure syslog-ng to process properly both RFC3164 and RFC5124 on the same listening port ? The scenario is a bunch of devices sending traffic to one syslog server port (both udp + tcp) with the senders typically not knowing what protocol they are sending. We are running syslog-ng 3.13 with this setup: source s_syslog { udp(ip(0.0.0.0) port(514)) ; tcp(ip(0.0.0.0) port(514)); } If needed we could upgrade syslog-ng to 3.19.1 but having checked the doc for 3.19, it seems that the solution would be to create 2 source entries, 1 for RFC3164 with network() and 1 for RFC5124 with syslog(). Neverthless, these 2 sources would have to listen on *different* ports and that is the problem for us. Note that we also have an identical issue with cisco traffic, since it's not RFC compliant, syslog-ng adds automatically a header with timestamp and hostname. Thank you.

4 3

Re: [syslog-ng] syslog-ng Digest, Vol 166, Issue 8
by Nathan Fish 25 Feb '19

25 Feb '19

Could you please clarify why the sources don't know what protocol they are sending? Are they relaying from other unknown sources? > Date: Sun, 24 Feb 2019 01:07:01 +0000 (UTC) > From: Carlan Philippe <philrmls(a)yahoo.fr> > To: "syslog-ng(a)lists.balabit.hu" <syslog-ng(a)lists.balabit.hu> > Subject: [syslog-ng] Syslog-ng setup for both RFC3164 and RFC5124 > Message-ID: <1313969407.6661190.1550970421020(a)mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > Is there a way to configure syslog-ng to process properly both RFC3164 and RFC5124 on the same listening port ? > The scenario is a bunch of devices sending traffic to one syslog server port (both udp + tcp) with the senders typically not knowing what protocol they are sending. > We are running syslog-ng 3.13 with this setup: > source s_syslog { udp(ip(0.0.0.0) port(514)) ; tcp(ip(0.0.0.0) port(514)); } > > If needed we could upgrade syslog-ng to 3.19.1 but having checked the doc for 3.19, it seems that the solution would be to create 2 source entries, 1 for RFC3164 with network() and 1 for RFC5124 with syslog(). Neverthless, these 2 sources would have to listen on *different* ports and that is the problem for us. > Note that we also have an identical issue with cisco traffic, since it's not RFC compliant, syslog-ng adds automatically a header with timestamp and hostname. > > Thank you.

2 1

Relay log message through Application LoadBalancer
by Ronald Fenner 23 Feb '19

23 Feb '19

I'm trying to figure out how to relay a message through an AWS Application Load Balancer. I have the config setup to relay the message with: destination d_kafka_unstructured { network( "<dns-name>" port(9082) );}; Look at the tcpdump log I can see that the message is relayed but the ALB doesn't know how to handle it and responds with 400 sinceing the message isn't a HTTP Request. What would be the best way to wrap the message in a http like request that the ALB will understand. Is there an easy way to just tell syslog-ng to relay the message as HTTP or would I need to write something to add/strip the HTTP wrapper. Ronald Fenner Network Architect Game Circus LLC. rfenner(a)gamecircus.com

3 3