- syslog-ng - lists.balabit.hu

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

running syslog-ng and syslogd concurrently?
by Matt Camuto 29 Nov '08

29 Nov '08

Hi There - I am new to this group so I thank you in advance for any help. We are in the process of evaluating syslog-ng for a replacement for normal syslogd. However it is desired for a few months to have syslog-ng and syslogd running on the same box with syslog-ng simply not handling the normal 'syslog traffic' (udp/514). We currently have a 30 day eval license to test out syslog-ng. We are using a sun t1000 box as an fyi. When we install syslog-ng the install script informs us that syslogd will be removed as a service?!?! Has anybody ever run syslogd (in either agent or server mode) on the same machine with syslogd running. Any guidance there would be highly appreciated. We are not in the position to do a hard cross over to syslog-ng for our production environment. Thanks in advance. Matt

5 6

syslog-ng 2.1.3 has been released
by devel＠balabit.hu 26 Nov '08

26 Nov '08

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 2.1.3 SUMMARY : new stable release DATE : Nov 26, 2008 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (2.1.3) has been released. For latest fixes in the 2.1.x branch you are recommended to upgrade to this version. CHANGES: NOTE: this release fixes a security problem CVE-2008-5110, see the changelog below for more details. Bugfixes: * Fixed chroot() support to change into the chrooted directory after chroot is invoked. This fixes the security problem CVE-2008-5110. NOTE: this vulnerability is not exploitable on its own, it only makes breaking out of the jail somewhat easier. Please also NOTE that, even with this patch applied, it is still possible to break out of the jail if syslog-ng is running as root. * Fixed the code to resolve usernames, 2.1.2 had a regression which caused all username lookups to fail. BINARY DOWNLOAD: If you have a binary subscription, you can download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… OR, if you have a platform that is supported by apt-get, use the following apt sources to fetch the latest releases: Debian GNU/Linux ---------------- sarge: deb https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ debian-sarge/syslog-ng-2.1 syslog-ng etch: deb https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ debian-etch/syslog-ng-2.1 syslog-ng RedHat Enterprise Linux ----------------------- RHEL-4 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ rhel-4/syslog-ng-2.1 syslog-ng SUSE 10 ------- SUSE 10.0 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ suse-10.0/syslog-ng-2.1 syslog-ng SUSE 10.1 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ suse-10.1/syslog-ng-2.1 syslog-ng HTTP can also be used in the place of HTTPS If your version of apt-get does not support the HTTPS protocol. When using plain HTTP, the username and password will not be encrypted. SOURCE DOWNLOAD: The latest versions of syslog-ng in source format can be found at: http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src/

4 4

syslog-ng 2.0.10 has been released
by devel＠balabit.hu 26 Nov '08

26 Nov '08

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 2.0.10 SUMMARY : new stable release DATE : Nov 26, 2008 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (2.0.10) has been released. For latest fixes in the 2.0.x branch you are recommended to upgrade to this version. CHANGES: NOTE: this release fixes a security problem CVE-2008-5110, see the changelog below for more details. Bugfixes: * Fixed Solaris door support, the door portion of sun-streams() sources did not work in previous releases, as the door specific thread was lost through the fork() call used to background syslog-ng. * Fixed a possible segfault if non-existing, optional source files are present in the configuration. * Fixed the internal representation of "facility" values, earlier an 8 bit value was used for both the priority and facility values, and although systems do not define facilities in this range, the LOG_FACMASK macro defines two additional bits. The type of this field was changed to 16 bits. * Fixed a possible 100% CPU usage case on HP-UX. HP-UX may return POLLERR on its own without the other flags set, this was not properly handled by syslog-ng, causing it to spin on the CPU. * Fixed chroot() support to change into the chrooted directory after chroot is invoked. This fixes the security problem CVE-2008-5110. NOTE: this vulnerability is not exploitable on its own, it only makes breaking out of the jail somewhat easier. Please also NOTE that, even with this patch applied, it is still possible to break out of the jail if syslog-ng is running as root. BINARY DOWNLOAD: If you have a binary subscription, you can download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… OR, if you have a platform that is supported by apt-get, use the following apt sources to fetch the latest releases: Debian GNU/Linux ---------------- sarge: deb https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ debian-sarge/syslog-ng-2.0 syslog-ng etch: deb https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ debian-etch/syslog-ng-2.0 syslog-ng RedHat Enterprise Linux ----------------------- RHEL-4 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ rhel-4/syslog-ng-2.0 syslog-ng SUSE 10 ------- SUSE 10.0 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ suse-10.0/syslog-ng-2.0 syslog-ng SUSE 10.1 rpm https://USERNAME:PASSWORD@apt.balabit.com/syslog-ng/open-source/ suse-10.1/syslog-ng-2.0 syslog-ng HTTP can also be used in the place of HTTPS If your version of apt-get does not support the HTTPS protocol. When using plain HTTP, the username and password will not be encrypted. SOURCE DOWNLOAD: The latest versions of syslog-ng in source format can be found at: http://www.balabit.com/downloads/files/syslog-ng/sources/2.0/src/

1 0

2 Issues - Resolving User and corrupt forwarding
by Robert Kong 22 Nov '08

22 Nov '08

Syslog-ng Version 3.0+20081121 is not resolving the user when using the option "owner(0)" or "owner(root)". The following error message is displayed: Error resolving user; user='root' or Error resolving user; user='0' Going through the archives I found a posting stating a similar problem. I am wondering if the incorrect patch was also applied to version 3.0? After a little debugging I noticed that in resolve_user the conditional check "if (*user) return FALSE" looks to be the culprit. When comparing resolve_user to resolve_group I notice that under resolve_group the conditional is "if (!*group) return FALSE". Negating the conditional in resolve_user seems to correct the problem. Though I am not sure if would be the correct thing to do. The second issue that I am having is with forwarding of incoming syslog messages to a secondary server running a native syslogd daemon. If I leave the original syslog message un-touched destination D_ONE { udp("10.10.10.10" port(514)); }; log { source(S_ALL); destination(D_ONE); }; The remote server receives and processes the syslog msg correctly. However, if I attempt to use a template the forwarded syslog msg become corrupted. destination D_ONE { udp("10.10.10.10" port(514) template("$DATE $HOST $MSGHDR$MSGONLY")); }; log { source(S_ALL); destination(D_ONE); }; What seems to be occurring is the PRI portion of the syslog msg becomes malformed when using the template. Is this the proper behavior or am I doing something wrong? Thanks Bob

1 0