- syslog-ng - lists.balabit.hu

insider 2013-05: syslog-ng configurator on Android; Using syslog-ng with Splunk; EU data protection and logging
by Peter Czanik 16 May '13

16 May '13

Dear syslog-ng users, This is the 24th issue of the syslog-ng Insider, a monthly newsletter that brings you syslog-ng related news. FEATURED NEWS syslog-ng configurator app for Android -------------------------------------- There is now a new configurator app available for Android, developed as a hobby project by one of the syslog-ng team members. The focus of the application is to create a syslog-ng.conf wich provides optimum performance based on a number of questions. For more details and download locations read the authors blog at http://pzolee.blogs.balabit.com/2013/04/little-syslog-ng-configurator-appli… syslog-ng and Splunk -------------------- We often receive questions, how to use syslog-ng and Splunk together in a logging infrastructure. We collected the most popular usage scenarios into a white paper, together with example configurations to make testing and integration even more easy. The WP is available at http://www.balabit.com/support/documentation/pdf/syslog-ng_splunk_deploymen… syslog-ng is participating GSoC again ------------------------------------- Just as last year, syslog-ng is participating Google Summer of Code under the umbrella of the openSUSE project. We have candidates for developing a native mysql destination, a redis destination, a XMPP (jabber) destination and log signing, which is a big improvement from last year, where we only had a single candidate for a similar number of development projects. The application process is closed now and there are still a couple of weeks to go, before the final list of approved students is announced. http://news.opensuse.org/2013/04/25/opensuse-hedgewars-and-owncloud-are-mov… Big changes ahead for EU data protection regulation --------------------------------------------------- This summer will most likely bring big changes in the regulation of Data Protection in the European Union. We collected these proposed changes and also how syslog-ng and proper central log management can help to comply with these regulations: http://jluby.blogs.balabit.com/2013/04/22/big-changes-ahead-for-eu- <http://jluby.blogs.balabit.com/2013/04/22/big-changes-ahead-for-eu-data-pro…>data-protection-regulation/ <http://jluby.blogs.balabit.com/2013/04/22/big-changes-ahead-for-eu-data-pro…> Compiling syslog-ng with MS SQL support on RHEL / CentOS & Co. -------------------------------------------------------------- During the past few months many people asked, how to log from syslog-ng to MS SQL on RHEL or CentOS. If you cannot buy syslog-ng PE (http://www.balabit.com/network-security/syslog-ng/central-syslog-server) follow these steps to compile all the necessary components yourselfand configure the MS SQL part: https://czanik.blogs.balabit.com/2013/04/compiling-syslog-ng-with-ms-sql-su… SHORT NEWS: * RFC5424 syslog between syslog-ng and rsyslog: https://czanik.blogs.balabit.com/2013/04/using-the-rfc5424-syslog-protocol-… * Linuxwochen: syslog-ng, AMQP, and 3D printers: http://czanik.blogs.balabit.com/2013/05/czp-linuxwochen-syslog-ng-amqp-and-… Your feedback and news tips about the next issue is welcome at documentation(a)balabit.com <mailto:documentation@balabit.com> To read this newsletter on-line, visit: http://insider.blogs.balabit.com/ -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

Problems with failed connections and time_reopen()?
by Matt Wise 13 May '13

13 May '13

We're running Syslog-NG 3.3.4 in our mixed Ubuntu 10/12 environment. We use SSL for all of our syslog-to-syslog connections, and have logging going to two different data pipelines. Data Dest #1: SyslogNG Client ----(SSL)----> SyslogNG Server ------> Logstash File-read-in-service Data Dest #2: SyslogNG Client ----(SSL)----> Stunnel Service ------> Flume Syslog Service The data streams work fine most of the time, but if we restart either the remote syslog-ng server, or the stunnel service, it seems that the syslog ng clients don't try to reconnect for a LONG time (or ever) to the endpoints again. I end up seeing the connection on the client go into a CLOSE_WAIT state, and syslog-ng keeps thinking that its sending log events through the connection, so it seems to never try to reconnect. I've tried setting time_reopen() to 0, 1 and 5... no luck or change in behavior. Any thoughts? --Matt

3 9

Question on custom log writer message output
by Dylan Kulesza 12 May '13

12 May '13

I'm working on a custom module to integrate with a third parties native log format. My intent is to have messages come into syslog-ng and processed as usual and then sent out a custom destination driver. Right now I've hacked together different code to make it work (tcp socket connection per log source) and now I'm at the point of actually sending a custom message. I've tried to stay as "true" to the syslog-ng as possible and have leveraged the log_forward_msg method to send my LogMessage. I was hoping I could just prepend data to the LogMessage but realized after doing all the other leg work that it wasn't a simple string :) So, my question is - what would the easiest way to leverage the existing queue->log_forward_msg (doesn't require the socket to be open vs examples such as spoof_source in afsocket) to write a custom message? I see that LogTemplate may have what I need, but after submerging myself in syslog-ng for the past week I'm not seeing clearly... Can anyone lend a hint/helping hand? What I'm trying to do: Open Socket Send Magic/StartPacket Prepend all log messages with a byte message - for example: 040404040400010MESSAGE (Of course Message would be in bytes/hex). It seems I would create an NVENTRY for my prepend message and then override log_writer_format_log? to do this? Not 100% clear how I would accomplish this. I also don't want to change any of the core/lib syslog-ng to accomplish this. Should be implemented purely as a module. Thanks!

2 2

weird filter problem
by Russell Fulton 11 May '13

11 May '13

Currently on 3.2.4. I am using patterndb to classify my incoming logs and want to send those that match pattern rules do a particular destination. filter f_unknown { "${.classifier.class}" ne 'unknown' ; }; but this appears to always fail (if I change ne to eq then I get everything). I have also tried using match with the same result. Russell

2 3

rewrite part of the message...
by Russell Fulton 11 May '13

11 May '13

Apologies to those of you who have already seen this on the ELSA list. I want to get rid of the explanatory essay that accompanies some eventlog messages from windows. I tried this: rewrite r_snarex { subst("\s+This event is generated when[^|]+\|", "|", value("MSGONLY") type("pcre")); }; and added it to log section, but it did not work. I have tried various variations on the theme too. Russell

2 2

syslog-ng and logrotate
by Rakesh Rajasekharan 10 May '13

10 May '13

I am using the syslog-ng 3.3.7 version. My question is , can we manage log rotation within the syslog-ng conf file ? Please advice

4 5

[Bug 234] New: eventlog: can' t build shared libraries under Windows with mingw
by bugzilla＠bugzilla.balabit.com 08 May '13

08 May '13

https://bugzilla.balabit.com/show_bug.cgi?id=234 Summary: eventlog: can't build shared libraries under Windows with mingw Product: syslog-ng Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: ramon.garcia.f+syslog(a)gmail.com Type of the Report: --- Estimated Hours: 0.0 When trying to building, libtool gives an error message saying that it cannot find shared library versions of Windows base libraries, like KERNEL32.DLL The fix is simple: upgrade libtool. After libtoolizing with libtool 2.4.2 it builds without trouble. Best regards. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[PATCH (3.5)] afsocket: Fix compilation with systemd support enabled
by Gergely Nagy 08 May '13

08 May '13

self->super.socket_options->sock_type is replaced with self->super.transport_mapper->sock_type, follow up on this in the systemd-enabled codepath too. Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- modules/afsocket/afunix-source.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/afsocket/afunix-source.c b/modules/afsocket/afunix-source.c index dd8b8bb..c3dcbe7 100644 --- a/modules/afsocket/afunix-source.c +++ b/modules/afsocket/afunix-source.c @@ -74,7 +74,7 @@ afunix_sd_acquire_named_socket(AFSocketSourceDriver *s, gint *result_fd, if (sd_is_socket_unix(fd, 0, -1, filename, 0)) { /* check if it matches our idea of the socket type */ - if (sd_is_socket_unix(fd, self->super.socket_options->sock_type, -1, filename, 0)) + if (sd_is_socket_unix(fd, self->super.transport_mapper->sock_type, -1, filename, 0)) { *result_fd = fd; break; @@ -84,7 +84,7 @@ afunix_sd_acquire_named_socket(AFSocketSourceDriver *s, gint *result_fd, msg_error("The systemd supplied UNIX domain socket is of a different type, check the configured driver and the matching systemd unit file", evt_tag_str("filename", filename), evt_tag_int("systemd-sock-fd", fd), - evt_tag_str("expecting", self->super.socket_options->sock_type == SOCK_STREAM ? "unix-stream()" : "unix-dgram()"), + evt_tag_str("expecting", self->super.transport_mapper->sock_type == SOCK_STREAM ? "unix-stream()" : "unix-dgram()"), NULL); return FALSE; } -- 1.7.10.4

1 0

Re: [syslog-ng] supervisor not restarting a failed daemon process
by Balazs Scheidler 07 May '13

07 May '13

Hi, No kernel source handy but my guess is that the kernel is logging the tid value, which is the same as pid as long as the process is single threaded. I've checked the supervisor code and the only way this could happen is a fork/pipe error which is not logged. It should be logged but who knows that message can be lost. The supervisor attempts to restart 3 times then gives up. Hmmm the supervisor messages may be redirected to syslog after the first startup which might explain why they don't get logged. But why does fork/pipe fail? Hope this helps. Evan Rempel <erempel(a)uvic.ca> wrote: >The logs below show a "standard" syslog-ng processID=15017 that reads /dev/log /proc/kmsg >The second instance of syslog-ng is what we call our "server" which just listens on the network ports >and does all of the complex patterndb, filtering and routing to destination processes > >kern.info kernel: syslog-ng[1561]: segfault at 7f65c0000078 ip 00007f65c0000078 sp 00007f65e1385a48 error 15 >--- this is the server instance segfaulting (I assume, see WAIT below) > >syslog.notice syslog-ng[15017]: Syslog connection closed; fd='20', client='AF_INET(142.104.47.145:49803)', local='AF_INET(127.0.0.1:1514)' >syslog.notice syslog-ng[15017]: Syslog connection broken; fd='14', server='AF_INET(142.104.47.146:514)', time_reopen='5' >--- this was the standard syslog loosing connection to the server, and detecting the drop of the server instance destination to it. > >daemon.info syslog-ng-stats: server stopping on socket "/var/local/syslog-ng.server.ctl" >daemon.info msgid_profiler[832]: committing residual data >local0.info flare-timer[834]: stopping >local0.info action-handler[833]: stopping >--- these are all program destinations of the server instance shutting down gracefully after the close of their stdin. > >daemon.crit supervise/syslog-ng[27221]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='11' >syslog.err syslog-ng[15017]: Syslog connection failed; fd='14', server='AF_INET(142.104.47.146:514)', error='Connection refused (111)', time_reopen='5' > >This "connection failed" message repeats every 5 seconds until I restart the server instance. > >syslog.notice syslog-ng[1911]: syslog-ng starting up; version='3.4.1' > >So it does not look like there is anything in the logs about attempted restarts. > > >WAIT... > >This is really odd. The line > >kern.info kernel: syslog-ng[1561]: segfault at 7f65c0000078 ip 00007f65c0000078 sp 00007f65e1385a48 error 15 > >implies that there was a process ID 1561 that segfaulted, but that line is the ONLY logged line with that process ID. >We take ps snapshots every 15 minutes, and those snapshots don't show anything for that process ID. >Also, the supervisor processID is shown > > USER PID PPID NI PRI CPU VSZ ELAPSED TIME COMMAND >root 27221 1 0 19 - 26556 9-04:00:59 00:00:00 supervising syslog-ng >root 27222 27221 0 19 - 977064 9-04:00:59 1-02:52:35 /usr/local/sbin/syslog-ng --cfgfile= ... > >which matches the line >daemon.crit supervise/syslog-ng[27221]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='11' > >so its child which dies should have been processID 27222 so why is the log line >kern.info kernel: syslog-ng[1561]: segfault at 7f65c0000078 ip 00007f65c0000078 sp 00007f65e1385a48 error 15 > > >I conclude that the 1561 is not the process ID. > >Can you shed any light on this? > >Evan. > >On 04/26/2013 11:00 PM, Balazs Scheidler wrote: > > >> Strange, indeed. The supervisor gives up if the restarted daemon exits for some reason. Eg. If there's an initialization error it gives up. Any indication in the logs? >> >> Evan Rempel <erempel(a)uvic.ca> wrote: >> >>> We are sing the log line >>> >>> supervise/syslog-ng[27221]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='11' >>> >>> >>> and it looks like it should restart, but instead of restarting, >>> the supervisor terminates and then no syslog-ng process is running. >>> >>> Is this a bug in the supervisor? >>> ______________________________________________________________________________ >>> 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 >>> >> ______________________________________________________________________________ >> 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 >> > > >-- >Evan Rempel erempel(a)uvic.ca >Senior Systems Administrator 250.721.7691 >Data Centre Services, University Systems, University of Victoria >______________________________________________________________________________ >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 >

2 3

Re: [syslog-ng] Can not get DBParse match macro result (syslog-ng 3.13 debian squeeze)
by 不坏阿峰 06 May '13

06 May '13

thanks to your reply. i do not understand how to do now. it puzzle and trouble me some days. i read the balabit syslog-ng OSE guide documents and only have simple information in there. how to do on this ----->>>> If you change the patterndb ruleset pattern to use a program of system rather than ESXI I think it would work. 2013/4/28 <syslog-ng-request(a)lists.balabit.hu> > 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. Can not get DBParse match macro result (syslog-ng 3.13 > debian squeeze) (????) > 2. Re: Can not get DBParse match macro result (syslog-ng 3.13 > debian squeeze) (Evan Rempel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 27 Apr 2013 22:34:50 +0800 > From: ???? <onlydebian(a)gmail.com> > Subject: [syslog-ng] Can not get DBParse match macro result (syslog-ng > 3.13 debian squeeze) > To: syslog-ng(a)lists.balabit.hu > Message-ID: > <CA+SSH2oBB2-WWvQksbchVVoyhfZbdVvDR= > V7wJ1EJdvE6Zx9zg(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > when use pdbtool do match test, it is success. but from syslog-ng can not > return result of macro > i can not get macro result. for example, ${.esxi.month} no value, same > as ${.esxi.host_ip} ${.esxi.time} > > test log output ,just like this. > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > === system,error,critical, HOST IP , > > > do the pdbtool test, it's ok. wish someone can give me some solution and > help. i have search some mail list but i can not get the right solution. > thanks a lot. > > root@debian:~# pdbtool match -D -c -p > /etc/syslog-ng/patterndb/esxi_pattern.xml -P ESXI -M "Apr 26 15:17:31 > 192.168.88.71 vmkernel: cpu11:8203)NMP: nmp_ThrottleLogForDevice:2319: Cmd > 0x1a (0x4124444a6280, 0) to dev "mpx.vmhba0:C0:T0:L0" on path > "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. > Act:NONE" > Pattern matching part: > @STRING:.esxi.month=Apr@ @STRING:.esxi.date=26@ > @STRING:.esxi.time=15:17:31@@IPv4:.esxi.host_ip=192.168.88.71@ > @ESTRING:.esxi.program= > vmkernel: cpu11:8203)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x1a > (0x4124444a6280, 0) to dev mpx.vmhba0:C0:T0:L0 on path vmhba0:C0:T0:L0 > Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. > Act:NONE@@ANYSTRING:.esxi.message=cpu11:8203)NMP: > nmp_ThrottleLogForDevice:2319: Cmd > 0x1a (0x4124444a6280, 0) to dev mpx.vmhba0:C0:T0:L0 on path vmhba0:C0:T0:L0 > Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE@ > Matching part: > Apr 26 15:17:31 192.168.88.71 vmkernel: cpu11:8203)NMP: > nmp_ThrottleLogForDevice:2319: Cmd 0x1a (0x4124444a6280, 0) to dev > mpx.vmhba0:C0:T0:L0 on path vmhba0:C0:T0:L0 Failed: H:0x0 D:0x2 P:0x0 Valid > sense data: 0x5 0x20 0x0. Act:NONE > Values: > MESSAGE=Apr 26 15:17:31 192.168.88.71 vmkernel: cpu11:8203)NMP: > nmp_ThrottleLogForDevice:2319: Cmd 0x1a (0x4124444a6280, 0) to dev > mpx.vmhba0:C0:T0:L0 on path vmhba0:C0:T0:L0 Failed: H:0x0 D:0x2 P:0x0 Valid > sense data: 0x5 0x20 0x0. Act:NONE > PROGRAM=ESXI > .classifier.class=esxi > .classifier.rule_id=182437592347598 > .esxi.month=Apr > .esxi.date=26 > .esxi.time=15:17:31 > .esxi.host_ip=192.168.88.71 > .esxi.program= vmkernel > .esxi.message=cpu11:8203)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x1a > (0x4124444a6280, 0) to dev mpx.vmhba0:C0:T0:L0 on path vmhba0:C0:T0:L0 > Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE > root@debian:~# > > > my configuration like as below > > ######## esxi_pattern.xml ############ > <?xml version="1.0" encoding="utf-8"?> > <patterndb version='3' pub_date='2009-04-17'> > <ruleset name='esxi' id='123456678'> > <pattern>ESXI</pattern> > <rules> > <rule provider='Fone Bro' id='182437592347598' class='esxi'> > <patterns> > <pattern>@STRING:.esxi.month:@ @STRING:.esxi.date:@ > @STRING:.esxi.time::@@IPv4:.esxi.host_ip:@ > @ESTRING:.esxi.program::@ @ANYSTRING:.esxi.message@</pattern> > </patterns> > </rule> > </rules> > </ruleset> > </patterndb> > > ######## syslog-ng.conf ######## > > #####Parser##### > parser pattern_db { > db_parser( file("/etc/syslog-ng/patterndb/esxi_pattern.xml")); > }; > > #Check pattern matching > destination udp_esxi_output { > file("/var/log/pattern_output" > template("=== $PROGRAM,${.esxi_month} ${.esxi.date} ${.esxi.time} HOST > IP ${.esxi.host_ip},${.esxi.message}\n") > template_escape(no)); > }; > > #####Log##### > log { > source(s_network); > parser(pattern_db); > destination(udp_esxi_output); > }; >

3 7