- syslog-ng - lists.balabit.hu

race condition in destination driver deinit?
by Michael Hocke 07 Apr '12

07 Apr '12

-----BEGIN PGP SIGNED MESSAGE----- Me again.... Hi guys, I've been running 3.3.3 on Solaris 10 x86 for quite a bit now. I've got two boxes, both running the same OS release and the same release of syslog-ng. One of them (box A) has a destination configured that doesn't really exist so I've been getting Mar 13 14:46:15 flowmon-sys syslog-ng[20118]: I/O error occurred while writing; fd='24', error='Connection refused (146)' which is perfectly fine and I just ignored it. The other Solaris box (box B) does not have this destination configured. It now happens that after a random number of HUP signals syslog-ng on box A crashes with a segmentation fault and the following backtrace: (gdb) bt #0 0xfef2a7a8 in log_dest_driver_release_queue_method (self=0x80d2958, q=0x83e58955, user_data=0x0) at driver.c:80 #1 0xfef2aa5c in log_dest_driver_deinit_method (s=0x80d2958) at driver.c:80 #2 0xfe914a14 in afsocket_dd_deinit (s=0x80d2958) at afsocket.c:109 #3 0xfef29cd6 in log_dest_group_deinit (s=0x8074198) at dgroup.c:59 #4 0xfef24a21 in log_center_deinit (self=0x8090cc0) at center.c:67 #5 0xfef25493 in cfg_deinit (cfg=0x80d2848) at cfg.c:90 #6 0xfef406b2 in main_loop_reload_config_apply () at mainloop.c:364 #7 0xfef40a42 in main_loop_io_worker_sync_call (func=<value optimized out>) at mainloop.c:364 #8 0x08047900 in ?? () I was able to reproduce this over and over again. Sometimes it happens after 11 HUPs, sometimes after 35, but it eventually does crash. Since the only difference between box A and box B is the one additional destination I suspect that this is the cause for this segfault. Maybe the HUP signal came at a time when syslog-ng was trying to send something to the non-existing destination? I'll try to collect some more data. If anybody could give me some direction on where exactly I should look into, I'll be happy to do that. - - Michael -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 10.0.3 (Build 1) Charset: us-ascii wsBVAwUBT1+ZRZbfnpCg64TVAQEiVgf7BmePJa6Va396QRyBLNPpOHzAvi9p3n07 uVvvYOcMHUFwixZoC0BXs+21EfSkMOmROQWupXBTcEbyBMOf0+HXDsuO7mfZDznU AZzLBzhgaDPf0stx55PqOssKTf28QLtxs1gUmJSb2DgmK9WjtMsovAlS83pQOa6O oQIaK3SBIUtrbijdx7vLvS0VUcqhDzJI9TJ7R+A0x3i9dAWKIvDb7wLW4CvB9k19 7bmmXFwpAClGZ6DS1CdIt4eHuDiuIoes2uXNhh5xReZpCh89FHzv8LxWxVnph3ms 6FctjAt4JMQTGnZRHN7QidYAGwjjabqtGjKWvXtRfoBCdUfLfC+wAA== =JjOa -----END PGP SIGNATURE-----

2 1

AUTO: James B Horwath/TheGuardian is out of the office. (returning 04/09/2012)
by James B Horwath 07 Apr '12

07 Apr '12

I am out of the office until 04/09/2012. I am out of the office until Monday April 9, 2012 with limited access to e-mail. If there are Nitro issues please contact Dante Rodino at 212-919-2819 or Sunil Gupta at 610-807-6710. Any other issues please contact Al Limone manager of IT Security Services & Governance. Thanks, Jim Note: This is an automated response to your message "syslog-ng Digest, Vol 84, Issue 10" sent on 4/6/2012 20:49:46. This is the only notification you will receive while this person is away. ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.

1 0

Handling multiple timezones
by Chris Hiestand 07 Apr '12

07 Apr '12

After some googling and reading the admin guide, I think what I want to do is not possible. But I'd like confirmation. My syslog-ng server gets syslog messages from clients with two timezones: UTC and US/Pacific. But the UTC clients (ESXi servers) cannot specify the UTC timezone, so the collector incorrectly assumes the timestamps are local (US/Pacific). I'd really like to convert the UTC timezone to US/Pacific so my entire output is in US/Pacific. But the only place I can specify a source timezone is in the source section - however both client groups send syslogs to the same source so I cannot do that. So potential workarounds are: A. Set all the clients to output in the UTC timezone so that I can set UTC in the common source and then convert to US/Pacific as the default output timezone. B. Setup another IP address to collect syslogs, and set the different timezone on that source (and configure all of those timezones clients to syslog to a different IP). This means you need N IP addresses to collect N different timezones. Is it considered "Best Practice" to have all clients send syslogs in UTC timezone to avoid this complication? Any help is appreciated. Thanks, Chris

2 2

[PATCH] afsocket: Do not die if a destination is not resolvable at startup.
by Gergely Nagy 06 Apr '12

06 Apr '12

If a destination cannot be resolved at init time, do not panic, just bail out, but otherwise pretend we succeeded: after time_reopen, we'll retry anyway! And on that note, teach afsocket_dd_start_connect() to call afsocket_dd_apply_transport() if our fd is -1 (ie, not connected). Reported-by: Peter Palfrader <weasel(a)debian.org> Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- modules/afsocket/afinet.c | 2 +- modules/afsocket/afsocket.c | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/modules/afsocket/afinet.c b/modules/afsocket/afinet.c index f83ff38..a7d3635 100644 --- a/modules/afsocket/afinet.c +++ b/modules/afsocket/afinet.c @@ -498,7 +498,7 @@ afinet_dd_apply_transport(AFSocketDestDriver *s) if ((self->bind_ip && !resolve_hostname(&self->super.bind_addr, self->bind_ip)) || !resolve_hostname(&self->super.dest_addr, self->super.hostname)) - return FALSE; + return TRUE; afinet_set_port(self->super.dest_addr, self->dest_port ? : default_dest_port, self->super.flags & AFSOCKET_DGRAM ? "udp" : "tcp"); diff --git a/modules/afsocket/afsocket.c b/modules/afsocket/afsocket.c index ae9c5c2..095f5a5 100644 --- a/modules/afsocket/afsocket.c +++ b/modules/afsocket/afsocket.c @@ -1103,6 +1103,11 @@ afsocket_dd_start_connect(AFSocketDestDriver *self) gchar buf1[MAX_SOCKADDR_STRING], buf2[MAX_SOCKADDR_STRING]; main_loop_assert_main_thread(); + + if (self->fd == -1) + if (!afsocket_dd_apply_transport(self)) + return FALSE; + if (!afsocket_open_socket(self->bind_addr, !!(self->flags & AFSOCKET_STREAM), &sock)) { return FALSE; @@ -1169,10 +1174,7 @@ afsocket_dd_init(LogPipe *s) /* these fields must be set up by apply_transport, so let's check if it indeed did */ g_assert(self->transport); - g_assert(self->bind_addr); - g_assert(self->dest_addr); g_assert(self->hostname); - g_assert(self->dest_name); if (cfg) { -- 1.7.9

2 3

[Bug 171] New: Unwanted IP adress Folder
by bugzilla＠bugzilla.balabit.com 04 Apr '12

04 Apr '12

https://bugzilla.balabit.com/show_bug.cgi?id=171 Summary: Unwanted IP adress Folder Product: syslog-ng Version: 3.1.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: julien.groselle(a)gmail.com Type of the Report: bug Estimated Hours: 0.0 Hi, I work for a lange society, and we use syslog-ng for 5 years now. We have a centralized server with storage tank to keep logs securly. Concretely, we have 2 centralized servers syslog-ng in chrooted environement, and 50 clients servers. Since we use TLS transport in place of stunnel workaround, we have many issues : - First of all, many logs aren't writen in $HOST folder but in IPADDRESS folder. So, to be clear, this is an exemple : # ls drwxr-x--- 8 root adm 4,0K 1 mars 00:07 10.0.0.1 drwxr-x--- 53 root adm 4,0K 19 mars 00:35 host1 I assume that host1 have 10.0.0.1 IP address and # tree 192.168.100.79/2012-03/ 10.0.0.1/2012-03/ ├── 02-user-10.0.0.1.log.bz2 ├── 06-user-10.0.0.1.log.bz2 ├── 07-user-10.0.0.1.log.bz2 ├── 08-user-10.0.0.1.log.bz2 ├── 09-user-10.0.0.1.log.bz2 ├── 12-user-10.0.0.1.log.bz2 ├── 13-user-10.0.0.1.log.bz2 ├── 14-user-10.0.0.1.log.bz2 ├── 15-user-10.0.0.1.log.bz2 ├── 16-user-10.0.0.1.log.bz2 └── 19-user-10.0.0.1.log # tree host1/2012-03/ |grep 19- ├── 19-apache.access-host1.log ├── 19-apache.error-host1.log ├── 19-authpriv-host1.log ├── 19-auth-host1.log ├── 19-cron-host1.log ├── 19-daemon-host1.log ├── 19-kern-host1.log ├── 19-mail-host1.log ├── 19-nagios-host1.log ├── 19-puppetd-host1.log ├── 19-syslog-host1.log └── 19-user-host1.log (we have this problem with many servers) In facility "user" for host 10.0.0.1 in fact i have log for snmptrapd... But why ?? We have config for snmpd but not for snmptrapd... So i have tried to define a default facility => failed After i have tried many dns and hostnames options => failed As anyone here have a way to search for me ? If you need more details, i'm your's. Kind regards. -- JG -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 6

GSoC wants you to code syslog-ng/Zorp in the summer
by Peter Czanik 03 Apr '12

03 Apr '12

Hello, This was included in last weeks newsletter, but as the deadline is three days away, it needs some extra attention: Google Summer of Code ( http://code.google.com/soc/ ) is a nice opportunity for higher education students to spend their summers productively by coding in open source software projects. This time BalaBit participates in GSoC with the help of the openSUSE <http://www.opensuse.org/> project. If you are interested in enhancing syslog-ng <http://www.balabit.com/network-security/syslog-ng/opensource-logging-system…> or Zorp <http://www.balabit.com/network-security/zorp-gpl/overview>, please see our project ideas on the openSUSE ideas page: http://en.opensuse.org/openSUSE:GSOC_ideas#syslog-ng and http://en.opensuse.org/openSUSE:GSOC_ideas#Zorp *Why it is worth attending?* - You can have a lifetime experience - It looks good in your CV - If you need documentation from Google to provide to your school so you can obtain course credit, you can get it -- after the positive final evaluation from your mentor - You can earn 5000 USD for a 3 months student job *When can I apply?* The deadline is 6th April (Friday) 2012, 19:00 UTC. *Who can apply?* - Students, 18 years of age or older on or before April 23, 2012. Google defines a student as an individual enrolled in or accepted into an accredited institution including (but not necessarily limited to) colleges, universities, masters programs, PhD programs and undergraduate programs. You are eligible to apply if you are enrolled in an accredited pre-university educational program provided you meet all of the other eligibility requirements. More details: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/fa… *How to apply?* - Please discuss your application first with the project mentor (syslog-ng: Gergely Nagy algernon(a)balabit.hu <mailto:algernon@balabit.hu>, Zorp: Szilard Pfeiffer coroner(a)balabit.hu <mailto:coroner@balabit.hu>) and then apply at Google at http://www.google-melange.com/ <http://www.google-melange.com/>and introduce yourself on the opensuse-project mailing list(http://lists.opensuse.org/opensuse-project/ <https://lists.opensuse.org/opensuse-project/>) - Please also attach a test exercise (depends on the project you apply to) a log of a successful *syslog-ng* 3.3 compilation from source/a log of a successful *Zorp* 3.9.5 compilation from source. An even more interesting thing would be if applicants already tried the Zorp virtual machines in advance, to get familiar with the software. *When I will be informed about further details?* On 23rd April the accepted student proposals announced on the Google Summer of Code 2012 site. For further timeline, please visit <http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/fa…>http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/fa… In case of any questions, please visit the Google Summer of Code 2012 Frequently Asked Questions site: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/fa… We wish you good luck, and hope to hear from you soon! (this page is the current content of http://czanik.blogs.balabit.com/2012/03/gsoc-wants-you-to-code-syslog-ngzor… , which hold more recent information later on). Bye, -- Peter Czanik (CzP)<czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

Ongoing 3.3.4 memory leaks
by Marvin Nipper 02 Apr '12

02 Apr '12

Hi. Sorry, looking for some help. Still trying to chase some memory leaks that I see on Solaris 10. I'll crank up syslog-ng, and it'll start running at around 7 or 8MB, and interestingly, it will run that way sometimes for several hours, and then (for reasons unknown), I'll take a look at it a bit later, and suddenly it will have jumped to 26MB (or later on, maybe 75MB). I've already applied the (older) logwriter.c fix and the (new) Gergely driver.h/afsocket.c fix, in an attempt to resolve known issues. Certainly the logwriter fix corrected a super-nasty, continuous leak problem, but this other leak problem still lingers. MY PROBLEM is that I'm wanting to use the debug symbols in syslog-ng, so that I can have the Solaris tools specifically show the exact location where these leaks are happening, BUT, whereas a non-debugging version of syslog-ng executes properly, when I configure syslog-ng with -enable-debug, the resulting executable will no longer start. It immediately exits, coughing up what amounts to a syntax error (even though I'm using the exact same command-line invocation that I use on the non-debugged executable): #/etc/init.d/syslog-ng start syslog-ng service starting. mkfifo: File exists mkfifo: File exists Usage: /usr/local/sbin/syslog-ng { start | stop } # Something about enabling debugging is impacting the operational behavior of the resulting binary. Anyway, I can use (for Solaris) libumem and mdb to narrow this down to a particular module, but without the debug symbols, I can't really get to a specific chunk of code, so it would obviously help to get that working. If anyone has any ideas, I certainly would appreciate the input. THANKS Marvin Nipper This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

3 3

On FreeBSd: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)'
by Traiano Welcome 02 Apr '12

02 Apr '12

Hi List I've been seeing the following in the messages log of my freebsd syslog server for quite some time now: --- Mar 20 12:19:12 syslog2 syslog-ng[35313]: I/O error occurred while writing; fd='12', error='No buffer space available (55)' Mar 20 12:19:12 syslog2 syslog-ng[35313]: Connection broken; time_reopen='60' Mar 20 12:19:12 syslog2 syslog-ng[35313]: I/O error occurred while writing; fd='13', error='No buffer space available (55)' Mar 20 12:19:12 syslog2 syslog-ng[35313]: Connection broken; time_reopen='60' --- These happen at a frequency of about 7 per minute on average. See attached trend graphs for an idea of the volume of traffic we're doing, as well as the memory and cpu utilisation trends on this server during this period. As can be seen from the graphs, load does not seem to be the issue. Occasionally during the week, the system freezes and requires a reboot, I think it's related to the above message, though I'm not sure. My question is: What does this error mean, and how can I resolve it? I have tried to frame this as an operating system kernel resource issue, and experimented with increasing the freebsd kernel sysctls for UDP performance: --- [root@syslog2 <mailto:root@syslog2.ops.mtnbusiness.co.za> /var/log]# sysctl kern.ipc.nmbclusters=102400 kern.ipc.nmbclusters: 25600 -> 102400 [root@syslog2 <mailto:root@syslog2.ops.mtnbusiness.co.za> /var/log]# sysctl kern.ipc.maxsockbuf=201326592 kern.ipc.maxsockbuf: 100663296 -> 201326592 [root@syslog2 <mailto:root@syslog2.ops.mtnbusiness.co.za> /var/log]# sysctl net.inet.udp.recvspace=33554432 net.inet.udp.recvspace: 16777216 -> 33554432 --- This has reduced the frequency of the errors a little, but in general the problem still remains. Syslog version: -- [root@syslog2]# syslog-ng -V syslog-ng 2.0.10 -- FreeBSD version: -- FreeBSD 7.2-STABLE #0 -- Any help would be much appreciated! Traiano

3 4

Building syslog-ng on OpenBSD v5 with SQL support
by Richard Brooks 01 Apr '12

01 Apr '12

I'm having a really hard time trying to find out how to tweak the make file supplied on the ports for syslog-ng v3.1.4, so that I get a binary that supports SQL on OpenBSD. Any tips would be gratefully received. Regards Richard

2 2

Known memory leak issues in 3.3.4?
by Marvin Nipper 01 Apr '12

01 Apr '12

After considerable effort, I managed to get 3.3.4 built (using gcc 4.4.2, along with glib 2.29.92 and the requisite eventlog 0.2.12). The problem is that the resulting syslog-ng component grows continuously (at an alarming rate). Whereas my 3.0.5 syslog-ng process starts out running in just under 3MB, and then stabilizes at about 3.3MB, the 3.3.4 version starts out small, and then at the point where I killed it (about 2 hours after starting it), it had already grown to 277MB. I'm doing nothing fancy here (config shown below). No data transformations, no use of time normalization features, no DB components. In short, I'm not trying to use any of the many new/elaborate features that have been added over the past few years. I'm just "eating log input", writing it to handful of files and pipes, just like I've been doing since the syslog-ng 2.x days. As one of the regular problems that I see mentioned in various threads is "some new fix for a memory leak", I'm just trying to see if there's some known problem in the virgin 3.3.4 code, that might be causing my problems. (I.E. should I wait for 3.3.5, and try again?) FYI, my environment is Solaris 10 x86. Aside from having moved to the newer gcc compiler (in order to even attempt to compile the latest syslog-ng version), the only other major component change was the newer version of glib, which as I recall, was also necessary to resolve compilation issues with the new syslog-ng versions. Anyway... before I beat my head against the wall trying to figure out what to do next, I figured that I'd ask the easy question (about "known bugs") first, so that I don't spend any time chasing a problem that may already be fixed. (I did dig thru the mailing list, and saw at least one mention of a memory leak in 3.3.4, but it seemed to be related to a specific bit of functionality, that I didn't think applied in my situation.) (And just a side-comment, FWIW, I noticed that when I swapped the 3.3.4 version, for the 3.0.5 version, the host system immediately incurred what I estimate to be at least a 20% high CPU load that had been required by the 3.0.5 version. And when I reverted back to 3.0.5 a few hours later, I saw that happen in reverse. I'm not sure why the newest version requires more resources, again, when I'm not asking it to do anything new, but it definitely seems that it does.) Thanks for your time and input. Existing config file shown below. Note that other than the version change, the only other modification (from the file that I was using in 3.0.5) relates to the threading changes, which I made based upon Bazsi's recommendations in an email on 3/18, about how to avoid potential data loss on inbound UDP packets. Again, thanks for any help/input: @version:3.3 options { dir_perm(0755); perm(0640); group(wheel); chain_hostnames(no); keep_hostname(yes); log_fifo_size(41000); threaded(no); dns_cache_size(5000); dns_cache_expire(86400); dns_cache_expire_failed(86400); }; source any_udp { udp(flags(store-legacy-msghdr)); }; source any_tcp { tcp(port(601) max-connections(40) flags("store-legacy-msghdr", "threaded") use_dns(no)); }; destination SEC {pipe("/tmp/sec"); }; destination WIN-PIPE {pipe("/tmp/windows"); }; destination routers_log { file("/var/adm/log/routers.log" create_dirs(yes) flags("threaded")); }; destination ravlin_log { file("/var/adm/log/ravlin.log" create_dirs(yes) flags("threaded")); }; destination windows_log { file("/var/adm/log/windows.log" create_dirs(yes) flags("threaded")); }; destination workstation_log { file("/var/adm/log/workstation.log" create_dirs(yes) flags("threaded")); }; destination catch-all_log { file("/var/adm/log/catch-all.log" create_dirs(yes) flags("threaded")); }; destination test { file("/var/adm/log/test.log" create_dirs(yes) flags("threaded")); }; destination dev_null {}; destination secdevedc01 { udp("10.132.193.245" spoof_source(yes) flags("threaded")); }; destination engedc01 { udp("10.132.192.199" spoof_source(yes) flags("threaded")); }; destination egssiem { udp("10.10.36.157" spoof_source(yes) flags("threaded")); }; log { source(any_udp); destination(SEC); }; log { source(any_udp); destination(egssiem); }; filter f_4 { facility(syslog) and level(info..emerg); }; log { source(any_udp); filter(f_4); destination(WIN-PIPE); }; log { source(any_udp); filter(f_4); destination(windows_log); flags(final); }; filter f_1_acl { facility(local5) and level(debug..emerg) and match("SEC-6-IPACCESSLOG" value("MESSAGE")) ; }; filter f_1 { facility(local5) and level(debug..emerg); }; log { source(any_udp); filter(f_1_acl); destination(routers_log); flags(final); }; log { source(any_udp); filter(f_1); destination(engedc01); }; log { source(any_udp); filter(f_1); destination(routers_log); flags(final); }; filter SonicWallNoise { match("id=firewall" value("MESSAGE")) and filter(SonicWallMsgs); }; filter SonicWallMsgs { match("m=97" value("MESSAGE")) or match("m=98" value("MESSAGE")) or match("m=537" value("MESSAGE")); }; log { source(any_udp); filter(SonicWallNoise); destination(dev_null); flags(final); }; filter f_3 { facility(local0) and level(debug..emerg); }; log { source(any_udp); filter(f_3); destination(ravlin_log); flags(final); }; log { source(any_tcp); destination(workstation_log); flags(final); }; log { source(any_udp); destination(catch-all_log); flags(final); }; Marvin Nipper Director of Security Stream Global Services mailto:marvin.nipper@stream.com ph: (303) 670-2705 PGP Key ID: 0x8EE28551 (DSS/DH) 8C5D 403A D107 0A95 672B B637 BCF1 919A 8EE2 8551 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

5 10