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 roadmap 2.1 & 2.2

We had a meeting on the syslog-ng roadmap today where we decided some important things, and I thought I'd use this channel to tell you about it. The Open Source Edition will see a 2.1 release incorporating all core changes currently in the Premium Edition and additionally the SQL destination driver. We are going to start development on the 2.2 PE features, but some of those will also be incorporated in the open source version: support for the latest work of IETF syslog protocols unique sequence numbering for messages support for parsing message contents Previously syslog-ng followed the odd/even version numbering to denote development/stable releases. I'm going to abandon this numbering now: the next syslog-ng OSE release is going to have a 2.1 version number and will basically come out with tested code changes only. The current feature set in PE were developed in a closed manner and I don't want to repeat this mistake. The features that were decided to be part of the Open
12 comments
Read more

syslog-ng 3.0 and SNMP traps

Last time I've written about how syslog-ng is able to change message contents. I thought it'd be useful to give you a more practical example, instead of a generic description. It is quite common to convert SNMP traps to syslog messages. The easiest implementation is to run snmptrapd and have it create a log message based on the trap. There's a small issue though: snmptrapd uses the UNIX syslog() API, and as such it is not able to propagate the originating host of the SNMP trap to the hostname portion of the syslog message. This means that all traps are logged as messages coming from the host running snmptrapd, and the hostname information is part of the message payload. Of course it'd be much easier to process syslog messages, if this were not the case. A solution would be to patch snmptrapd to send complete syslog frames, but that would require changing snmptrapd source. The alternative is to use the new parse and rewrite features of syslog-ng 3.0. First, you need to f
2 comments
Read more