December 2008 - syslog-ng - lists.balabit.hu

Problem compiling syslog-ng with enable-spoof-source on AIX 5.2
by CentralRegion IPAdmin 20 Dec '08

20 Dec '08

Hi, I'm trying to compile syslog-ng.2.1.3 after configuring with --enable-spoof-source. libnet is a prereq as I have learned, but I can't find any hint how to install libnet. Latest version of libnet is "0.10.11: released 18/02/2003" and it seems there is no mailinglist available. The code comes with some makefile templates such as "beos.mak, djgpp.mak, freebsd.mak, linux.mak, mingw.mak, rsxntdj.mak", but none of them works with AIX I have used "GNU Make 3.81" and "gcc version 3.3.2" to compile libnet. All are failing. Do you have any ideas how to get it done? Thank You! Werner

3 3

Performance issues
by farouk.s.khawaja＠jpmorgan.com 18 Dec '08

18 Dec '08

I'm finding that my Syslog-NG 2.0.9 OSE is not able to send more than 19 msgs/sec. I've tried setups with/without flow control, but keep coming up with similar performance results. I'm using the 'file' driver to read the data from application log files. I supposed I could use a named pipe, but I rather not create a new tool to write data to the pipe and create other bottlnecks and buffering issues. The application logs I want to follow writes at a pace of ~130msgs/sec during peak usage with average message size of ~410bytes. My destination log location is on NFS. I've verified that it's not the network or NFS that's causing the issues. I whipped up a simple perl script that made a socket connection from the source host to the destination host where syslog-ng was listening. I was able to pump 48320 messages to that remote syslog port that was configured to write the data to a NFS partition. That's ~3200 msgs/sec. So I also know that the destination syslog-ng is working fine. My guess is that the problem lies with the file driver. I'd like to get syslog-ng to be the tool I use to consolidate logs across N number of hosts instead of writing some bootleg code of my own to which I will forever be a slave to maintain. Any assistance you can provide would be appreciated. Source syslog-ng.conf ########################################################## # G L O B A L O P T I O N S ########################################################## options { use_dns (no); use_fqdn (no); create_dirs (yes); log_fifo_size(2100); time_sleep (10); }; ########################################################## # Template ########################################################## template t_clog { template("$MSG\n"); template_escape(no); }; ########################################################## # Sources ########################################################## # ## default source for logging syslog messages source s_internal { internal(); }; # ## source s_ldsol01_file { file("/tmp/ldsol01-clog.log" follow_freq(10) flags(no-parse) log_fetch_limit(1000) log_iw_size(2000) ); }; ########################################################## # Destinations ########################################################## # ## default destination for logging syslog messages destination d_syslog_file { file("/home/csh_apps/twataprd/Logs/SYSLOG-NG/syslog-ng.log"); }; # ## eqny-cshweb2 destination d_ldsol01_tcp { tcp( "10.3.22.43" port(20534) ); }; destination d_ldsol01rej_tcp { tcp("10.3.22.43" port(20535)); }; ########################################################## # logs ########################################################## log { source( s_internal ); destination ( d_syslog_file ); }; log { source( s_ldsol01_file ); destination( d_ldsol01_tcp ); flags(flow-control); }; Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

3 2

Ronald Jones is out of the office.
by Ronald Jones 18 Dec '08

18 Dec '08

I will be out of the office starting 12/18/2008 and will not return until 12/29/2008. I will respond to your message when I return. ----------------------------------------- ________________________________________________________ DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

1 0

include file syntax
by Balazs Scheidler 11 Dec '08

11 Dec '08

Hi, This is a repost of my blog bost at http://bazsi.blogs.balabit.com/, if you have an opinion about the subject please either reply to this e-mail, or post a comment on my blog. ---- I'm about to implement configuration file includes, and although the implementation is quite straightforward, the syntax to be used is something to give a thought or two. Currently the syslog-ng configuration file consists of statements, each with the following basic format: stmt [] { ... }; The "id" gives a unique identifier of the statement, and the braces enclose the contents. Currently only the ID part is optional, the braces are always there. To make the include statement consistent with that, it'd have to look something like: include { "filename" }; Obviously I don't like this too much, as it is way different from all other applications permitting the use of include statements. What about this: include "filename"; E.g. use the ID part the name of the file to be included. I like this better. A third option might be the use of 'pragma' directives, currently only used to specify the file format compatibility in the case of syslog-ng 3.0: @version: 3.0 This'd mean that include statements would look like this: @include: filename The problem with this last option is that pragmas are currently only processed at the beginning of the configuration file. So that code should also be generalized. I think I'd go with the second option, that's not completely inconsistent, but still the most intuitive to use. What do you think? -- Bazsi

3 3

Need help to send logs to a different server
by Swapna 11 Dec '08

11 Dec '08

Hi, We have syslog-ng configuration as follows: - There are 50 clients communicating to one log server - The log server is kept in secured place where nobody have access - All the logs of 50 clients are coming to the log server and the logs are kept as follow /var/log/syslog-ng/<client host>/extended.log We want all the log of each client to relay into a seperate server live. Means the current log file of each host will go to the new server simultaneously as it is going to the central log server. We can configure a second log server like the existing one. But our requirement is, that all the logs will be received from the central log server not from the client hosts. Any help is really appreciated. Thanks

5 8

[Bug 25] New: 3.03 MSI package bails out on server 2008
by bugzilla＠bugzilla.balabit.com 11 Dec '08

11 Dec '08

https://bugzilla.balabit.com/show_bug.cgi?id=25 Summary: 3.03 MSI package bails out on server 2008 Product: syslog-ng Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: critical Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: erik.linder(a)riksgalden.se Type of the Report: bug Estimated Hours: 0.0 Created an attachment (id=5) --> (https://bugzilla.balabit.com/attachment.cgi?id=5) MSI-install log I cannot make the 3.03 MSI to install on server 2008. I have tried several servers, both DC's and domain members. Same result every time. See attached MSI-logfile. This is stopping our rollout completely. Best regards, ./Erik -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

newbie
by McGranahan, Jamen 10 Dec '08

10 Dec '08

Ok, I guess I'm just too used to the Windows environment that I'm having a hard time adjusting to command line interfaces. Here's the deal: I need to get syslog-ng running on my server. I think I have it installed, downloading the file from sunfreeware.com, putting the file in the /var/spool/pkg directory (file = syslogng-2.0.9-sol10-sparc-local.gz). I then used the pkgadd -d command to install it, which seemed to be fine. But where do I go from here? Has it started or do I need to manually start it? I'm also looking for a syslog-ng.conf file in order to modify it - I'm using this to push log data to another server, and according to the central logging program we are using, I need to modify this file like this: options { use_fqdn(yes); log_fifo_size(8192); }; source local { file("/var/log/messages"); udp(ip(127.0.0.1) port(514)); internal(); }; filter notdebug { level(info...emerg); } destination loghost { tcp("name.of.yoursplunkserver" port (9514)); }; log { source(local); filter(notdebug); destination(loghost); }; Any advice/or guidance is greatly appreciated. I know the more I use these Unix boxes, the more I'll learn... Jamen McGranahan Systems Services Librarian Vanderbilt University 419 21st Avenue South Nashville, TN 37240

2 1

checking configuration file syntax
by Pavel Shaydo 10 Dec '08

10 Dec '08

Hello all! I'm trying to automate configuration file syntax checking and can't figure out how I can do it. According to manual -s option should perform syntax checking. I'm trying following: syslog-ng -s -f file-to-check It always exits with zero status and never outputs anything, regardless of correct configuration file or it contains errors. Is there something I missed? I tested it on 2.0.9 and on premium edition 2.1.11a. -- Best regards, Pavel Shaydo

3 3

syslog-ng uses 100% cpu when i use program() destination driver
by Scott McGillivray 10 Dec '08

10 Dec '08

Hi all, I have installed syslog-ng via apt-get on an Ubuntu 8.10 server. I have added the below to the configuration file: template t_smtp { template_escape(no); template("NOOP HELO localhost MAIL From: admin(a)example.com RCPT To: scott(a)example.com DATA From: admin(a)example.com To: scott(a)example.com Subject: Syslog msg from $HOST - [$FACILITY:$PRIORITY] $PROGRAM $S_DATE [$FACILITY:$PRIORITY] $MSG . QUIT "); }; log { source(s_all); filter(f_at_least_notice); destination(d_logfile); }; destination d_logfile { program("sendmail -bs > /var/log/syslog-email.log 2>&1" template(t_smtp)); }; For some reason with the above config after a message hits d_logfile the CPU usage jumps to 100% and stays there until syslog-ng is stopped. It's like some file it uses during the process gets locked and the thing jams up waiting forever. The only way to solve the problem is remove the program() entry and replace it with file("/var/log/temp.log" template(t_smtp)); in which case it works fine. To test the program()destination I created a php script that just slept for 10 seconds <?php sleep(10); ?> And called it in d_logfile { } with program("/usr/bin/php /tmp/sleep-test.php") And sure enough the cpu jumped to 100% and stayed there until syslog-ng was stopped. Can anyone see a program with my above config or suggest why syslog-ng can't cope when the program() doesn't return immediately? Thanks Scott ********************************************************************************** Disclaimer The information and attached documentation in this e-mail is intended for the use of the addressee only and is confidential. If you are not the intended recipient please delete it and notify us immediately by telephoning or e-mailing the sender. Please note that without Codemasters’ prior written consent any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Attachments to this e-mail may contain software viruses. You are advised to take all reasonable precautions to minimise this risk and to carry out a virus check on any documents before they are opened. Any offer contained in this communication is subject to Codemasters’ standard terms & conditions and must be signed by both parties. Except as expressly provided otherwise all information and attached documentation in this e-mail is subject to contract and Codemasters’ board approval. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Codemasters. This footnote also confirms that this email message has been swept by SurfControl for the presence of computer viruses. **********************************************************************************

2 2