- syslog-ng - lists.balabit.hu

Reprocess disk buffer files
by Aaron Daniel 31 Mar '12

31 Mar '12

In the LTS version of PE, we have some servers that have old disk-buffer files (var/*qf) still on disk, with the contents not sent to a central server. Is there a way to force syslog-ng to re-process those, or do we have to manually process them ourselves? The files contain very old log entries that still need to be processed, and syslog-ng appears to be using a newer *.qf file for it's disk buffer. When it does this, it's completely ignoring the old log entries so we have some gaps in our central processing system. (Sorry if this has been asked before, google's not been my friend on this search...) -- Aaron Daniel

2 1

High volume of syslog message getting dropped
by Samuel Petreski 31 Mar '12

31 Mar '12

I'm running syslog-ng 3.3.4 on FreeBSD 8.2, but am getting choppy logging from syslog-ng. I'm continually (every minute or so) getting the following messages from syslog-ng, Mar 19 17:09:24 system syslog-ng[47183]: Syslog connection accepted; fd='51', client='AF_INET(10.33.11.249:24813)', local='AF_INET(0.0.0.0:1470)' Mar 19 17:09:25 system syslog-ng[47183]: Syslog connection closed; fd='51', client='AF_INET(10.33.11.249:24813)', local='AF_INET(0.0.0.0:1470)' Mar 19 17:09:46 system syslog-ng[47183]: Syslog connection accepted; fd='25', client='AF_INET(10.166.166.234:50240)', local='AF_INET(0.0.0.0:1470)' Mar 19 17:09:47 system syslog-ng[47183]: Syslog connection closed; fd='25', client='AF_INET(10.166.166.234:50240)', local='AF_INET(0.0.0.0:1470)' Most of my hosts sending their logs to syslog-ng are Cisco ASAs and they are configured to send their logs securely. Also these devices send syslog messages at a very high rate (few of the devices generate logs in excess of 10GB/day). My relevant syslog-ng paramenters are as follows, **************** #global options options { chain_hostnames(off); keep_hostname(yes); use_fqdn(off); flush_lines(0); stats_freq(360); threaded(yes); dns_cache(2000); dns_cache_expire(87600); flush_lines(10000000); flush_timeout(6000); }; #destination, source and logging destination d_cisco_devices { file("/data/log/$HOST-$YEAR$MONTH$DAY.log" perm(0400)); }; source tls_clients { tcp(ip(0.0.0.0) port(1470) max-connections(300) log_iw_size(300000000) log_fetch_limit(2000000) tls( key_file("/etc/syslog-ng.key") cert_file("/etc/syslog-ng.crt") peer_verify(optional-untrusted)) ); }; log { source(tls_clients); destination(d_cisco_devices); flags(flow-control); }; **************** I've read through the manual and have tried to increase the flush_line, log_fetch_limit, log_iw_size parameters but have not been able to fine tune its operation. Most of the my recorded syslog messages are for about few seconds, and then they start again the next minute. Any help or pointers anyone can provide would be greatly appreciated. Thanks. --Samuel

2 1

allow setting up unix named sockets for listening
by Patrick Hemmer 30 Mar '12

30 Mar '12

When troubleshooting issues with our production syslog servers, its often not possible to deliberately duplicate discovered issues as it then affects production. Something which would be extremely useful in this case is if we could configure syslog-ng to set up a unix socket as a listener. Then whenever clients connect logs can be sent to the client. Syslog-ng currently has unix-stream and unix-dgram destinations, but they act as clients, only sending to already created sockets. There could be other uses for this, basically allowing clients to connect whenever they want and receive the logs. Kind of like a pipe destination, but it works a bit cleaner since if no client is connected, syslog-ng wouldnt have to buffer and drop messages (and it would allow multiple clients). Fairly low priority, but just something that I thought would be useful. -Patrick

2 1

syslog-ng Insider - March 2012
by Peter Czanik 29 Mar '12

29 Mar '12

Dear syslog-ng users, This is the 12th issue of the syslog-ng Insider, a monthly newsletter that brings you syslog-ng related news. Your feedback and news tips about the next issue is welcome at documentation(a)balabit.com <mailto:documentation@balabit.com> FEATURED NEWS GSoC wants you to code syslog-ng in the summer ---------------------------------------------- GSoC ( 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 project. If you are interested in enhancing syslog-ng or Zorp, 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 Alpha1 of syslog-ng 3.4 is released ----------------------------------- The first alpha version of syslog-ng 3.4 is released. Major new features are junctions & channels which add even more flexibility to the syslog-ng configuration. There is now also a json parser, smtp destination and modules are now loaded automatically. For more details on what is new, please check Bazsi's blog: http://bazsi.blogs.balabit.com/2012/03/first-alpha-release-of-syslog-ng-3-4… Instead of using the release, it is recommended to use sources from git, which have some major stability fixes: https://github.com/bazsi/syslog-ng-3.4 If you intend to package syslog-ng 3.4, it's recommended to check the mailing list for patches from Algernon, which make packaging easier. A snapshot of his work is available at: http://packages.madhouse-project.org/syslog-ng/algernon/3.4/syslog-ng-alger… There are already packages for openSUSE and an updated syslog-ng-devel port for FreeBSD. See http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The (r)evolution of name value pairs ------------------------------------ Name value pairs were at the heart of syslog-ng even before PatternDB made it obvious. And now the CEE board and the Lumberjack project also push into this direction: instead of free form text messages, use name value pairs for logging. Recent developments in syslog-ng also serve this purpose: v3.3 can output name value pairs in JSON and v3.4 will be able to parse these logs and turn them into name value pairs again. How project Lumberjack can improve logging: http://bazsi.blogs.balabit.com/2012/02/project-lumberjack-to-improve-linux-… How syslog-ng can be used for CEE (JSON) logs: http://algernon.blogs.balabit.com/2012/02/cee-handling-with-syslog-ng/ How using name value pairs can improve logging: http://czanik.blogs.balabit.com/2012/03/state-of-the-art-logging-syslog-ng-… which is also the basis for our syslog-ng presentation at the LOADays conference: http://loadays.org/ syslog-ng community forum ------------------------- BalaBit has had a very positive experience with the syslog-ng community and we believe that your feedback has played a key role in the success of syslog-ng. We have decided to adopt this community model to our other products so that we can have our customers involved in product design. It could be interesting for you to visit this brand new community site at http://communities.balabit.com <http://communities.balabit.com/>. You are one of the first of our friends to be invited. OTHER SHORT NEWS * An introduction to RLTP, a protocol to make syslog-ng PE even more reliable: http://pzolee.blogs.balabit.com/2012/03/zero-message-loss-with-syslog-ng-pr… * The libumberlog library is a thin, LD_PRELOAD-able layer on top of the legacy syslog() function, that turns those calls into something that emits its message part as a JSON formatted structured log message:http://algernon.github.com/libumberlog/ * ELSA, the high performance web GUI for syslog-ng, received a few interesting updates to make resolving security incidents even more quick and efficient. For the latest examples check: http://ossectools.blogspot.com/ NEW RELEASES: * syslog-ng OSE 3.4 alpha1: http://bazsi.blogs.balabit.com/2012/03/first-alpha-release-of-syslog-ng-3-4… * syslog-ng PE 4F2: http://andrea.blogs.balabit.com/2012/02/balabits-new-syslog-ng-premium-edit… * lumberlog 0.1.0: http://algernon.github.com/libumberlog/ ARCHIVE 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

IP Address folder
by Julien Groselle 28 Mar '12

28 Mar '12

Hello everybody, 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

1 1

Fix for bug 162 in an official release yet?
by Mr. Jan Walter 26 Mar '12

26 Mar '12

We're running into the frame header issue a lot in our deployment environment, so I am wondering if the fix, committed the day before the 3.3.4 release, made it into 3.3.4. It's not in the changelog posted, but given the dates, it was worth the question. https://bugzilla.balabit.com/show_bug.cgi?id=162 Did it? Cheers, Jan

2 3

Installing syslog-ng 3.3.4 OSS on multiple Centos servers
by Srinivasan Subramanian 26 Mar '12

26 Mar '12

Hi I have a need to install syslog-ng 3.3.4 on multiple Centos servers. Unfortunately i am unable to find RPMs for the newer versions and only find the source downloads. 1. Any links to contributed repositories for Centos 5.x?2. Alternatively can anyone point me to Source RPMs for Centos 5.x so that I can at least make the RPMs myself? Even EPEL 6 I find only 3.2.x source RPMs RegardsSrini

6 5

RFC: Removing the 'dummy' module
by Gergely Nagy 23 Mar '12

23 Mar '12

Hi! syslog-ng comes with a 'dummy' module, that does nothing, but emit a notice whenever it receives a message. I doubt anyone uses it, because it is useless, and serves as an aid for module writers only, as a skeleton to build on. However, it is built AND installed by default, which is kinda awkward, in my opinion, and perhaps a bit confusing too: when I see a dummy module automatically installed, I start to wonder just what the heck it is good for and why it is there in the first place? Since it's completely useless, I'd like to propose either of the following: 1) Remove the module completely from the source code. The rationale behind this is that it's a very basic example, shows very little about how a destination driver should work, and is even a little bit stale here and there. For example, the grammar directly pokes the driver structure, which is a bad habit (accessors are a whole lot better!). Furthermore, when I wanted to write a driver, I looked at the dummy driver first, but after a couple of minutes, I concluded it has so very little information, that it's not enough for me as a starting point. So I started to look at other drivers, and learned from there. In that sense, it doesn't even succeed at being a reasonable skeleton, or starting point. A HOWTO document, or something similar about the architecture of the various drivers would be much much more useful, but this document is yet to be written. 2) Keep the module, but don't install it, ever. As a compromise, the module could be kept, but not installed. This way we still have a very small example, but it's not installed needlessly. I think it's obvious I'd rather go with the first option, but perhaps there's good reasons for keeping it, that I overlooked. The decision is in Bazsi's hand, anyway. -- |8]

2 1

[Bug 154] New: Processes forked via program() do not properly terminate
by bugzilla＠bugzilla.balabit.com 23 Mar '12

23 Mar '12

https://bugzilla.balabit.com/show_bug.cgi?id=154 Summary: Processes forked via program() do not properly terminate Product: syslog-ng Version: 3.2.x Platform: Other OS/Version: Solaris Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: hendrik.volker(a)de.verizonbusiness.com Type of the Report: --- Estimated Hours: 0.0 I am using a SyslogNG 3.2.4 build for our company internal version of Solaris 10 on some SUN V245 SPARC servers. In a project I am using the following config: ---8<--- source s_whsvoipgwv2_ngrep_bge1 { program ( "/prod/tools/ngrep -d bge1 -t -q -W single SIP port 5060" flags (no-parse) tags ("IF1") ); }; parser p_whsvoipgwv2_ngrep { csv-parser ( columns ("NGREP.PROTO" "NGREP.DATE", "NGREP.TIME", "NGREP.SRCADDR", "NGREP.DUMMY", "NGREP.DSTADDR", "NGREP.MSG" ) flags (drop-invalid, escape-none, greedy, strip-whitespace) delimiters (" ") ); }; template t_whsvoipgwv2_ngrep { template ( "$MONTH_ABBREV $DAY ${NGREP.TIME} $HOST ${NGREP.PROTO} ${NGREP.SRCADDR} ${NGREP.DSTADDR} ${ NGREP.MSG}\n" ); }; destination d_whsvoipgwv2_sip_voipslp { file ("/var/home/voipslp/sip/sip.$YEAR$MONTH$DAY$HOUR.log" owner("voipslp") group("voipsl") perm(0644) template(t_whsvoipgwv2_ngrep) ); }; log { source(s_whsvoipgwv2_ngrep_bge1); parser(p_whsvoipgwv2_ngrep); destination(d_whsvoipgwv2_sip_voipslp); flags (final); }; ---8<--- With the log file rotation every hour it seems that SyslogNG is starting new instances of ngrep, while not terminating the old instances. This results in lots! of running but unused ngreps. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 11

[Bug 150] New: Possible memory leak for TLS connections
by bugzilla＠bugzilla.balabit.com 23 Mar '12

23 Mar '12

https://bugzilla.balabit.com/show_bug.cgi?id=150 Summary: Possible memory leak for TLS connections Product: syslog-ng Version: 3.3.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: eric(a)sevenscale.com Type of the Report: --- Estimated Hours: 0.0 I've noticed that memory usage seems to grow as clients using TLS connect and disconnect. I ran syslog-ng under valgrind while I caused a number of clients to connect and disconnect a few times and saved the leak summary from valgrind: https://gist.github.com/893a9687bf98dc53f0e7 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 6