MonitorWare Knowledge Base

I've got librelp 0.1.3 installed, with rsyslog 3.20.4 stable.

This is the relevant output from rsyslogd -d:

Code: Select all

5991.487260668:main thread: cfline: '$ModLoad omrelp'
5991.487265802:main thread: Requested to load module 'omrelp'
5991.487270322:main thread: loading module '/usr/local/lib/rsyslog/omrelp.so'
5991.487415064:main thread: Called LogError, msg: could not load module '/usr/local/lib/rsyslog/omrelp.so', dlopen: librelp.so.0: cannot open shared object file: No such file or directory


I've tried installing librelp 0.1.1, and compiling rsyslog against that version as well - no luck. And the file definitely exists - no access restrictions to the file either... Has anybody encountered this?

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

well, dlopen usually is right... does /usr/local/lib/rsyslog/omrelp.so really exist? Please note that this is NOT provided by librelp. It is a rsyslog module which is built when the --enable-relp ./configure switch is given.

rgerhards wrote:well, dlopen usually is right... does /usr/local/lib/rsyslog/omrelp.so really exist? Please note that this is NOT provided by librelp. It is a rsyslog module which is built when the --enable-relp ./configure switch is given.

yes it does exist.. Which is why this is so puzzling.

Code: Select all

# ls -l /usr/local/lib/rsyslog/omrelp.so
-rwxr-xr-x 1 root root 34416 2009-02-17 14:09 /usr/local/lib/rsyslog/omrelp.so


puh... can you rebuild it? Maybe there was an issue with the build process?

rgerhards wrote:puh... can you rebuild it? Maybe there was an issue with the build process?

I have done so. Rebuild librelp, rebuild rsyslog, stop before rebuilding, start after 'make install', ... Hasn't been able to solve the problem.

jf/ wrote:

rgerhards wrote:puh... can you rebuild it? Maybe there was an issue with the build process?

I have done so. Rebuild librelp, rebuild rsyslog, stop before rebuilding, start after 'make install', ... Hasn't been able to solve the problem.

ok an update. Seems like a 'make distclean' should have fixed the problem.. (I opted to rm -rf, and then untarball, then rebuild again). My bad here...

So the issue is solved? If, so, that's excellent news

Rainer

rgerhards wrote:So the issue is solved? If, so, that's excellent news

Rainer

yup, thanks.