Skip to main content

syslog-ng OSE 3.2 caveats

Starting with syslog-ng OSE 3.2, syslog-ng became plugin based, which has some consequences that even experienced syslog-ng users may stumble into.

The most obvious one, is that syslog-ng now produces a series of .so files loaded at runtime, instead of being a monolithic executable. If a given .so is not not or not loaded, some of the functionality may be missing. This usually manifests itself by a syntax error when parsing the configuration file.

Second: if you compile syslog-ng from source, the unit/functional test programs also want to load plugins, and they try to do that from the install directory. This means that you first have to install syslog-ng using "make install" before running the testsuite. This is not an ideal solution, but should work for now.

Plugins are loaded from $prefix/lib/syslog-ng by default, however this can be changed using the `module-path` global, which contains the list of directories where syslog-ng should look for modules. You can change this using the syntax:

@define module-path `module-path`:/usr/local/lib/syslog-ng-plugins

I think that's it for now.
Labels:

Comments

Pedro_Castro said…
Hi,

I am trying to compile under cygwin environment.

It compiles but when i try to start syslog-ng it shows me a list of errors:

Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='syslogformat'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='basicfuncs'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afsocket'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='affile'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afprog'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afuser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='dbparser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='csvparser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='syslogformat'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='basicfuncs'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afsocket'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='affile'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afprog'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='afuser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='dbparser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='csvparser'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='confgen'
Plugin module not found in 'module-path'; module-path='/usr/local/lib/syslog-ng'
, module='confgen'


Do you know something about it?.

Regards
5:03 PM
Bazsi said…
The actual .so files are in /usr/local/lib/syslog-ng ?

I think there's a binary package for cygwin, have you tried using that?
12:54 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 contributions redefined

syslog-ng has been around for about 12 years now, but I think the biggest change in the project's life is imminent: with the upcoming release of syslog-ng OSE 3.2, syslog-ng will become an independent entity. Until now, syslog-ng was primarily maintained & developed by BalaBit, copyrights needed to be reassigned in order to grant BalaBit special privileges. BalaBit used her privileges to create a dual-licensed fork of syslog-ng, named "syslog-ng Premium Edition". The value we offer over the Open Source Edition of syslog-ng are things that larger enterprises require: support on a large number of UNIX platforms (27 as of 3.1), smaller and larger feature differences (like the encrypted/digitally signed logfile feature) better test coverage and release management longer term support Although perfectly legal, this business model was not welcome in various Free Software communities, and has caused friction and harm, because BalaBit has enjoyed a privilege that no others cou...
Post a Comment
Read more

An introduction to db-parser()

As promised on the mailing list here comes a short description of the new db-parser functionality of syslog-ng. For an introduction to parsers in general see my previous blog post here . The aim for db-parser is two-fold: extract interesting information from a log message attach tags to a log message for later classification. For instance here's a log sample (lines broken for readability): Feb 24 11:55:22 bzorp sshd[4376]: Accepted password for bazsi \ from 10.50.0.247 port 42156 ssh2 This message states that a user named "bazsi" has logged into the host named "bzorp" using SSH2 from the quoted IP and port. When you read this message as a human, the event that happened is perfectly clear. However if it is not a human, but a piece of software that has to make out the meaning of the message, you need to identify the event (e.g. that a user login has happened) and the additional information associated with the event (e.g. that he used 10.50.0.247 as the cl...
7 comments
Read more