March 2011 - syslog-ng - lists.balabit.hu

syslog-ng stats
by Ioan Indreias 21 Mar '11

21 Mar '11

Hello, Running with syslog-ng OSE 3.2.1 and wondering what exactly mean some of the parameters by STATS. Please find below an extract of the output we get (with the default stats_level) , hoping to receive some hints from you. global > payload_reallocs = ? global > msg_clones = ? global > sdata_updates = ? why center > received is 0 ? From OSE 3.2 manual, Chapter 14, it should be the "total number of messages received from every configured sources." BR, Ioan ### [root@myhost TOOLS]# /opt/syslog-ng/sbin/syslog-ng-ctl stats SourceName;SourceId;SourceInstance;State;Type;Number global;payload_reallocs;;a;processed;1643977 source;s_net;;a;processed;615301996 global;msg_clones;;a;processed;1230603992 destination;d_mysql1;;a;processed;247656 destination;d_mysql2;;a;processed;1354498 global;sdata_updates;;a;processed;0 center;;received;a;processed;0 center;;queued;a;processed;0 ###

2 2

Syslog-ng returning a TCP Reset
by Andy Ruch 20 Mar '11

20 Mar '11

Hello, I was evaluating syslog-ng and have come across a strange problem. When connecting to syslog-ng using the 'syslog' source, syslog-ng will return a TCP Reset at random intervals. The interesting thing about this error is it only seems to appear when the message length varies between logs. After some experimenting, I was able to reproduce the error using loggen to send logs from a file. However, when loggen generates its own fixed length messages, syslog-ng will receive everything properly. I'm concerned about the reliability of syslog-ng. I don’t want it to close the connection if it gets overloaded. I know that I can add some options to improve performance, but that seems like a patch and not a fix. I would think syslog-ng would utilize TCP flow control to prevent the sender from sending too fast. Am I doing something wrong? Does this look like a bug or have I just reached the max performance of syslog-ng? Any help is appreciated. Below I’ve included some information about the commands that I was running as well as my system setup. Thanks, Andy ***** Details ***** - Two machine setup (one sender and one receiver) - Receiver is using an evaluation copy of Syslog-PE-4.0.1a (but I first saw this issue using open source version 3.2.2 ) - CentOS 5.5 ***** Send Command ***** This is the console output that I receive from loggen. As you can see, the failure did not happen every time. In this particular case, it was the second execution that failed. I normally just run it back to back until it fails. $ ./loggen -P -r 40000 -R /tmp/syslog_10-40 10.64.27.38 6514 average rate = 16503.22 msg/sec, count=50000, time=3.297, (last) msg size=112, bandwidth=1627.75 kB/sec $ ./loggen -P -r 40000 -R /tmp/syslog_10-40 10.64.27.38 6514 Send error Connection reset by peer5 msg/sec average rate = 15483.69 msg/sec, count=15435, time=0.9968, (last) msg size=114, bandwidth=1527.27 kB/sec ***** Send File ***** The following pattern was put into a file and repeated for a total of 50,000 lines. I tried to attach the complete file but it was too large for this mailing list. Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ***** Syslog-ng.conf ***** @version: 4.0 options { }; ###### # sources source s_local { # message generated by Syslog-NG internal(); # standard Linux log source (this is the default place for the syslog() # function to send logs to) unix-stream("/dev/log"); # messages from the kernel file("/proc/kmsg" program_override("kernel")); }; source s_net { syslog( ip(0.0.0.0) transport("tcp") port(6514) ); }; ###### # destinations destination d_messages { file("/var/log/messages"); }; destination d_tmp_file { file("/tmp/log_messages"); }; ###### # paths log { source(s_local); destination(d_messages); }; log { source(s_net); destination(d_tmp_file); flags(flow-control); };

3 2

Local7 issue
by Cardia E. - GDI/BH/O&I 20 Mar '11

20 Mar '11

Gentlemen, I've got an issue that the bootlog info doesn't appear in the bootlog file as I would like ( running Red Hat 5.6 EL ). Here are the syslog-ng.conf file parameters : destination bootlog { file("/var/remote2_log/$HOST/$YEAR$MONTH$DAY/boot.log"); }; filter f_local7 { facility(local7); }; log { source(system); filter(f_local7); destination(bootlog); }; Someone an idea ?? Greetz, Efisio --------------------------------------------------------------------------------- Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. Ministerie van Veiligheid en Justitie This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. Ministry of Security and Justice ---------------------------------------------------------------------------------

2 1

TLS - Authentication problem
by Honza Mach 18 Mar '11

18 Mar '11

Hi everyone, I am currently implementing central syslog server using syslog-ng and I have encontered some problems when configuring mutual TLS authentication. On client machine I keep getting the following errors: Mar 18 12:54:22 machine syslog-ng[5432]: Syslog connection established; fd='9', server='AF_INET(xxx.113.161.23:514)', local='AF_INET(0.0.0.0:0)' Mar 18 12:54:22 machine syslog-ng[5432]: Certificate validation failed; subject='CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE', issuer='CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE', error='self signed certificate in certificate chain', depth='3' Mar 18 12:54:22 machine syslog-ng[5432]: SSL error while writing stream; tls_error='SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed' Mar 18 12:54:22 machine syslog-ng[5432]: I/O error occurred while writing; fd='9', error='Broken pipe (32)' Mar 18 12:54:22 machine syslog-ng[5432]: Syslog connection broken; fd='9', server='AF_INET(xxx.113.161.23:514)', time_reopen='60' This is the exact same problem as in the following thread: https://lists.balabit.hu/pipermail/syslog-ng/2011-January/015613.html I have verified the functionality without TLS settings and everything works perfectly, so there is no problem on the way (firewall, etc.). I studied carefully the manual and everything is as it is supposed to be: CLIENT MACHINE -------------- OS - Debian 6.0 Squeeze SYSLOG-NG VERSION: client:# syslog-ng --version syslog-ng 3.1.3 Installer-Version: 3.1.3 Revision: ssh +git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.1#master#def34661b08109f8148904b860457d5747c425b3 Compile-Date: Feb 1 2011 19:36:27 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: on Enable-Linux-Caps: on Enable-Pcre: on DESTINATION CONFIGURATION FROM SYSLOG-NG.CONF: destination d_net { tcp("xxx.113.161.23" port(514) tls( key_file("/etc/ssl/private/client.company.cz-nopass.key") cert_file("/etc/ssl/certs/client.company.cz.pem") ca_dir("/etc/ssl/trusted_ca")) ); }; CA HASH: client:# openssl x509 -in /etc/ssl/trusted_ca/tcs.pem -noout -hash 9df51c42 CA CERTIFICATE DIRECTORY: client:# ll /etc/ssl/trusted_ca total 12 lrwxrwxrwx 1 root root 27 Mar 18 12:30 9df51c42.0 -> /etc/ssl/trusted_ca/tcs.pem -rw-r--r-- 1 root root 1655 Mar 18 12:29 tcs.pem VALIDATE CERTIFICATE AGAINST CA: client:# openssl verify -CAfile /etc/ssl/trusted_ca/9df51c42.0 -verbose /etc/ssl/certs/client.company.cz.pem /etc/ssl/certs/client.company.cz.pem: OK SERVER MACHINE -------------- OS - Debian 6.0 Squeeze SYSLOG-NG VERSION: server:# syslog-ng --version syslog-ng 3.1.3 Installer-Version: 3.1.3 Revision: ssh +git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.1#master#def34661b08109f8148904b860457d5747c425b3 Compile-Date: Feb 1 2011 19:36:27 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: on Enable-Linux-Caps: on Enable-Pcre: on SOURCE CONFIGURATION FROM SYSLOG-NG.CONF: source s_net { tcp( ip(0.0.0.0) port(514) tls( key_file("/etc/ssl/private/server.company.cz-nopass.key") cert_file("/etc/ssl/certs/server.company.cz.pem") ca_dir("/etc/ssl/trusted_ca")) ); }; CA HASH: server:# openssl x509 -in /etc/ssl/trusted_ca/tcs.pem -noout -hash 9df51c42 CA CERTIFICATE DIRECTORY: server:# ll /etc/ssl/trusted_ca total 12 lrwxrwxrwx 1 root root 27 Mar 18 12:30 9df51c42.0 -> /etc/ssl/trusted_ca/tcs.pem -rw-r--r-- 1 root root 1655 Mar 18 12:29 tcs.pem VALIDATE CERTIFICATE AGAINST CA: server:# openssl verify -CAfile /etc/ssl/trusted_ca/9df51c42.0 -verbose /etc/ssl/certs/server.company.cz.pem /etc/ssl/certs/server.company.cz.pem: OK Certificates for the CA are the same on both machines. I tried to put either the whole chain up to the root certificate, or the last certificate, but the error keeps to appear. It the thread mentioned above the community member Baszi suggested following: ------ It's the whole point in certificate validation to use self-signed CA certificates. (after all, a centrally trusted CA is self-signed too). Try validating that your directory is correct usign "openssl verify", once that validates the cert, syslog-ng should too. -- Bazsi ------- What is meant by validate the directory, I do not understand that. As I said, I succefully validated both client and server certificate against the CA certificate using openssl command, but syslog-ng is still complaining. Am I missing something? I will gladly provide more information, if needed. Thank you for your time Regards Honza Mach

2 1

SEC-2.6.0 released
by Risto Vaarandi 18 Mar '11

18 Mar '11

hi all, since a number of sites are running syslog-ng with SEC event log correlator, I thought I'll let you know about the new major release of SEC: http://sourceforge.net/projects/simple-evcorr/files/sec/2.6.0/ kind regards, risto

1 0

Syslog-ng Cisco CSS switch
by add gy 17 Mar '11

17 Mar '11

Hi, I am not ablle to recive syslog messsages from Cisco content switches I am able to recive messages from rest of the devices ex: cisco routers , switches ,firewalls , loadbalancers etc .. But not able to recive messages from cisco CSS Syslog version 3.0.9 stable Operating system Cento OS 4.7 Is there any configuration changes to be done on syslog file? Thanks Add

1 0

logging to the cloud
by Peter Czanik 16 Mar '11

16 Mar '11

Hello, Two weeks ago I wrote about Loganalyzer, which was one of my most read blog post ever. This time I wrote about a different approach: logging to the cloud: http://czanik.blogs.balabit.com/2011/03/logging-to-the-cloud/ which also provides a nice, web based gui for syslog-ng logs, without the need to set anything up locally. There are already a few more syslog web gui apps on my radar, as I wrote at the end Loganalzer blog. Please let me know, if you have any other syslog related web applications you find interesting! Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

FreeBSD install with SSL
by John Kristoff 16 Mar '11

16 Mar '11

I have a FreeBSD system that has the SSL libraries not built from ports. Apparently the syslog-ng port expects ssl to be installed from ports. I'd prefer not to do that at this time. However, when building syslog-ng from source, it expects pkg-config (or gnome-config as this FreeBSD still refers to it) for SSL, which also is not going to work. I've not tried the balabit supplied FreeBSD package. Any guidance on the best approach to get syslog-ng with SSL support installed onto this FreeBSD box? Keep in mind I'd like to avoid changing the installed openssl libaries at this time. Will the balabit package do the trick? Perhaps it is better to modify the build process from source? John

5 4

afsql module error
by Eshan Bhide 15 Mar '11

15 Mar '11

Hi guys, I'm trying to setup a master syslog-ng server which listens on UDP syslog port to incoming squid access log and Cisco syslog messages. It uses a db_parser to parse and store these access logs in different variables. I now need to store these values in a simple mysql database. I have created the database schema and thought of using a pipe and a wrapper script to write the query. But read that there are problems sometimes with this approach. I then thought about doing it using libddb and downloaded the package syslog-ng_3.2.2 from the website. So far so good, but when I try to run syslog-ng it gives me an error: syslog-ng Error opening plugin module; module='afsql', error='/usr/local/lib/syslog-ng/libafsql.so: undefined symbol: dbi_result_free' Error opening plugin module; module='afsql', error='/usr/local/lib/syslog-ng/libafsql.so: undefined symbol: dbi_result_free' Error parsing destination, destination plugin sql not found in /usr/local/etc/syslog-ng.conf at line 61, column 3: sql(type(mysql) ^^^ Any pointers on what I'm missing here ? I have commented out the '@module afsql' line in modules.conf, have made sure I've got the latest libdb and libdb-devel packages. I'm running CentOS 5.x and just don't know how to proceed :( Appreciate all and any help guys thank you. -- Eshan Bhide Engineer, Core Infrastructure and Systems Development Global Gossip 14 Wentworth Ave Surry Hills, NSW 2010 Australia ------------------------------------------------- IMPORTANT NOTICE : The information in this email is confidential and may also be privileged. If you are not the intended recipient, any use or dissemination of the information and any disclosure or copying of this email is unauthorised and strictly prohibited. If you have received this email in error, please promptly inform us by reply email or telephone. You should also delete this email and destroy any hard copies produced.

5 14

[PATCH] Fix autogen.sh to autogen submodules by default.
by Gergely Nagy 15 Mar '11

15 Mar '11

Call autogen_submodules even if $skip_modules is unset (which it would be on most systems that just cloned the repository). Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- autogen.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/autogen.sh b/autogen.sh index 3569af3..569f134 100755 --- a/autogen.sh +++ b/autogen.sh @@ -31,7 +31,7 @@ autogen_submodules() done } -if [ "$skip_submodules" = 0 ]; then +if [ -z "$skip_submodules" ] || [ "$skip_modules" = 0 ]; then autogen_submodules fi -- 1.7.2.3

2 1