[rsyslog] rsyslog-3.15.0 compile problem
rgerhards at hq.adiscon.com
Wed Apr 2 11:07:03 CEST 2008
> >> my guess is that rsyslog can't find its libraries (e.g.
> >> /usr/local/lib/rsyslog/lmregexp.so). You'll need to do "make
> >> or something like "ln -s $(find /path/to/rsyslog/sources/ -name
> >> "*.so") /usr/[local/]lib/rsyslog".
> >> You can run "strace ./rsyslogd -v" to see where it looks for its
> >> libraries.
> Yep, you're right. I was expecting:
> - Shared library issues at runtime to be visible using ldd(1)
> - To at least be able to get command-line help or version (-v)
> information from rsyslogd (without loadable modules)
> - A nicer error message ;-)
> strace ./rsyslogd -v -b -n 2>&1 | grep ENOENT
> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> open("/usr/lib/rsyslog/lmnet.so", O_RDONLY) = -1 ENOENT (No such file
> Can the module path (/usr/lib/rsyslog) be specified? Is there a
> ./configure option that I'm missing at compile time or a command line
> parameter to rsyslogd or config file parameter in rsyslog.conf? I've
> been through ./configure --help, rsyslogd.8 and rsyslog.conf.5 and
> seem to find anything?
That's mostly distro-specific and this is where I have very limited
knowledge. But you can set the module path via the environment, use
RSYSLOG_MODDIR=/path/to/modules/ . There is also a -m option to do the
same, but it currently is read too late to help with the core modules.
On my 64Bit system adding --libdir=/lib64 often helped with such
problems when I encountered them. Not sure if that's the right cure...
> It's very early in the US and I might just be missing something
You are *really* brave!
More information about the rsyslog