MonitorWare Knowledge Base

I built a copy of 3.11.0 with

./configure --disable-unix --disable-klogd
make
make install

(I do indeed not wish this daemon to listen on local sockets.)

After failure to start in a production ready manner failed, I tried with the debug option:

[root@phlsniff etc]# /usr/local/sbin/rsyslogd -f /etc/rsyslog.conf -d
dbg fl: (null)
Warning: compatibility modes < 3 are currently NOT supported - continuing...

1774.769981663:main thread: Compatibility Mode: 0
1774.770018314:main thread: Writing pidfile /var/run/rsyslogd.pid.
1774.798567949:main thread: module of type 1 being loaded.
1774.798601425:main thread: module of type 1 being loaded.
1774.798629046:main thread: module of type 1 being loaded.
1774.798658037:main thread: module of type 1 being loaded.
1774.798680703:main thread: module of type 1 being loaded.
1774.798988720:main thread: Starting.
1774.799021105:main thread: rsyslog 3.11.0.
1774.799037436:main thread: Called init.
1774.799053297:main thread: Unloading non-static modules.
1774.799070737:main thread: Clearing templates.
1774.814289224:main thread: cfline: '$ModLoad imudp.so # provides UDP syslog reception'
1774.814323351:main thread: Requested to load module 'imudp.so #'
1774.814519378:main thread: Called logerr, msg: could not load module '/usr/local/lib/rsyslog/imudp.so #', dlopen: /usr/local/lib/rsyslog/imudp.so #: cannot open shared object file: No such file or directory

1774.814725641:main thread: config line NOT successfully processed
1774.814748906:main thread: Called logerr, msg: the last error occured in /etc/rsyslog.conf, line 7
1774.814784613:main thread: cfline: '$UDPServerAddress 216.143.145.103'
1774.814803708:main thread: Called logerr, msg: invalid or yet-unknown config file command - have you forgotten to load a module?
1774.814830519:main thread: config line NOT successfully processed
1774.814849690:main thread: Called logerr, msg: the last error occured in /etc/rsyslog.conf, line 8
1774.814878756:main thread: cfline: '$UDPServerRun 514'
1774.814897887:main thread: Called logerr, msg: invalid or yet-unknown config file command - have you forgotten to load a module?
1774.814926493:main thread: config line NOT successfully processed
1774.814955964:main thread: Called logerr, msg: the last error occured in /etc/rsyslog.conf, line 9


where, as you can see, it all goes downhill starting where it tries to load imudp.so. However, in this case, the file was actually installed by make install:

[root@phlsniff etc]# ls -l /usr/local/lib/rsyslog/imudp.so
-rwxr-xr-x 1 root root 18854 Feb 7 16:29 /usr/local/lib/rsyslog/imudp.so
[root@phlsniff etc]#

I'm running SELinux and wondered if that was messing things up, though it shouldn't be, so I tried it, with the same results, with enforcing turned off.

A bit more information:

[root@phlsniff etc]# /usr/local/sbin/rsyslogd -v
dbg fl: (null)
rsyslogd 3.11.0, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: Yes
FEATURE_NETZIP (message compression): Yes
GSSAPI Kerberos 5 support: No
FEATURE_DEBUG (debug build, slow code): No
Runtime Instrumentation (slow code): No

See http://www.rsyslog.com for more information.




Any ideas?

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

argh... I see the problem with the code. There is a bug. Please remove the comment after the .so - that should do the trick. I'll open a tracker item for it. So simply use

$ModLoad imudp.so

instead of

$ModLoad imudp.so # provides UDP syslog reception

BTW: the --disable configure options are no longer strictly necessary, as it is the $ModLoad that decides what the rsyslogd listens to - but this is just FYI.

Please let me know the outcome.

Rainer

Mmmhhh... I tried to repro the problem, but to no avail in my environment. I am still pretty sure it is related to the comment. Please let me know as soon as you have any results.

Rainer

With the comment removed:

5561.570201874:main thread: Clearing templates.
5561.570311273:main thread: cfline: '$ModLoad imudp.so'
5561.570334089:main thread: Requested to load module 'imudp.so'
5561.588535602:main thread: module of type 0 being loaded.
5561.588564863:main thread: cfline: '$UDPServerAddress 216.143.145.103'
5561.588590979:main thread: cfline: '$UDPServerRun 514'
5561.588614230:main thread: Trying to open syslog UDP ports at 216.143.145.103:514.

it appears much happier.

And I sort of figured that some of the config options, not to mention -r and -m0 at runtime, didn't do much anymore.....but wasn't 100% sure.

OK, off to create a config file that actually does something interesting.

Thanks.

Progress report: identified bug, soon to be fixed. And if you didn't read it, be sure to have a look at the compatibility doc for v3 specifics. Its in the htnml doc set and on this site.

Bug tracker: http://sourceforge.net/tracker/index.ph ... tid=696552

Rainer