Skip to main content

syslog-ng OSE 3.1beta2 release

I've mentioned shortly in my previous post, but here's a more official announcement: I've released syslog-ng OSE 3.1beta2, containing some important bugfixes.

The list of changes: http://www.balabit.com/downloads/syslog-ng/open-source-edition/3.1beta2/changelog-en.txtLink

Thanks to Martin Holste for the feedback he provided, hopefully we can forget about the "beta" part soon.
Labels:

Comments

/-djs-/ said…
Bazsi- I've had some problems with the OSE and udp syslog receive speed. Since so many features have been added in 3.x, could that be a regression? I'm getting like 30KB/sec receive on a fast box that can receive 100x that amount of data with a Splunk listener. I've looked at all the tuning info out there and have tried all kinds of different options including disabling dns, etc., but I could only get an improvement from 20KB/sec to 30KB/sec. This is on RHEL 4.6 x86_64. I look forward to testing 3.1, but I'm really hoping you have some real "AHA!" info that will explain and fix this for me.

thanks,

/-djs-/
12:56 AM
Bazsi said…
is this 3.1.x or 3.0.x ? I don't know about any kind of UDP related performance regressions, but it may happen that noone told me.

But that rate seems very low indeed.

What are the symptoms you are experiencing? Message drops, or syslog-ng simply maxes out your processor?
4:05 PM
/-djs-/ said…
3.0.5 It's just not getting all the events. CPU util is 0.5% - 0.7%. netstat -su doesn't show receive errors. The only thing I've thought of since is instead of specifying the ip to listen on, just use 0.0.0.0, but that should really only increase cpu util in the ip stack to id the dest ip on the packet, right, so I don't think that will do much to fix it.
1:35 AM
Bazsi said…
hmm... does the syslog-ng dropped counter for the specific destination count any messages?

since you said that the kernel is not reporting receive errors, that pretty much means that syslog-ng itself is dropping those messages for some reason.

if you enable stats_freq(), you should see the message drop counters.

If syslog-ng itself is dropping messages, that should mean that the destination FIFO is undersized, though the default should pretty much suffice.

I've tried to reproduce the problem here and syslog-ng happily processed a couple of thousand msg/sec.
4:59 PM
Post a Comment

Popular posts from this blog

syslog-ng fun with performance

I like christmas for a number of reasons: in addition to the traditional "meet and have fun with your family", eat lots of delicious food and so on, I like it because this is the season of the year when I have some time to do whatever I feel like. This year I felt like doing some syslog-ng performance analysis. After reading Ulrich Deppert's series about stuff "What every programmer should know about memory" on LWN, I thought I'm more than prepared to improve syslog-ng performance. Before going any further, I'd recommend this reading to any programmer, it's a bit long but every second reading it is worth it. As you need to measure performance in order to improve it, I wrote a tool called "loggen". This program generates messages messages at a user-specifyable rate. Apart from the git repository you can get this tool from the latest syslog-ng snapshots. Loggen supports TCP, UDP and UNIX domain sockets, so really almost everything can be me...
17 comments
Read more

syslog-ng OSE 2.1 released

I have just uploaded the first release in the syslog-ng Open Source Edition 2.1 branch to our website. It is currently only available in source format at this location: http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src This release synchronizes the core of syslog-ng to the latest PE version and adds the SQL destination driver. This is an alpha release and thus might be rough around the edges, but it basically only contains code already tested in the context of the Premium Edition. The SQL functionality requires a patched libdbi package, which is available at the same link. We're going to work on integrating all our libdbi related patches to the upstream package. If you want to know how the SQL logging works, please see the Administrator's Guide or our latest white paper Collecting syslog messages into an SQL database with syslog-ng. The latter describes the Premium Edition, but it applies to the Open Source one equally well.
6 comments
Read more

syslog-ng 3.2 changes

I've just pushed a round of updates to the syslog-ng 3.2 repository, featuring some interesting stuff, such as: SQL reorganization: Patrick Hemmer sent in a patch to implement explicit transaction support instead of the previous auto-commit mode used by syslog-ng. I threw in some fixes and refactored the code somewhat. Configuration parser changes: the syntax errors produced by syslog-ng became much more user-friendly: not only the column is displayed, but also the erroneous line is printed and the error location is also highlighted. Additional plugin modules were created: afsql for the SQL destination, and afstreams for Solaris STREAMS devices. Creating a new plugin from core code takes about 15 minutes. I'm quite satisfied. With the addition of these two modules, it is now possible to use syslog-ng without any kind of runtime dependency except libc. The already existing afsocket module (providing tcp/udp sources & destinations) is compiled twice: once with and once withou...
4 comments
Read more