Monitoring Splunk

./splunkd: /usr/lib64/libxslt.so.1: no version information available (required by ./splunkd) on OpenSuse 11.3

cwichoski
New Member

Hi, when I try to run splunkd on my OpenSuse 11.3 i got follow message, but libxslt package is installed:

dvl01:/opt/splunk/bin # ./splunkd 
./splunkd: /usr/lib64/libxslt.so.1: no version information available (required by ./splunkd)
./splunkd: /usr/lib64/libxslt.so.1: no version information available (required by ./splunkd)
Couldn't open log file configuration "/etc/log.cfg": No such file or directory

and here is the ldd output:

ldd splunkd
./splunkd: /usr/lib64/libxslt.so.1: no version information available (required by ./splunkd)
./splunkd: /usr/lib64/libxslt.so.1: no version information available (required by ./splunkd)
    linux-vdso.so.1 =>  (0x00007fffbbdff000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f88e3694000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f88e348b000)
    libpcre.so.0 => /lib64/libpcre.so.0 (0x00007f88e325d000)
    libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f88e2f07000)
    libxslt.so.1 => /usr/lib64/libxslt.so.1 (0x00007f88e2ccc000)
    libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007f88e2a78000)
    libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007f88e26e5000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00007f88e24e1000)
    libarchive.so.2 => /usr/lib64/libarchive.so.2 (0x00007f88e22b1000)
    libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f88e20a2000)
    libz.so.1 => /lib64/libz.so.1 (0x00007f88e1e8c000)
    libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x00007f88e1bfe000)
    libm.so.6 => /lib64/libm.so.6 (0x00007f88e19a7000)
    libc.so.6 => /lib64/libc.so.6 (0x00007f88e1647000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f88e38b1000)
    libacl.so.1 => /lib64/libacl.so.1 (0x00007f88e143e000)
    libattr.so.1 => /lib64/libattr.so.1 (0x00007f88e1239000)
Tags (3)
0 Karma
1 Solution

Drainy
Champion

Try ./splunk start / restart / status

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

You should not be trying to run splunkd yourself directly. Use splunk start or splunk start splunkd.

0 Karma

Drainy
Champion

Try ./splunk start / restart / status

Get Updates on the Splunk Community!

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...

Detecting Remote Code Executions With the Splunk Threat Research Team

REGISTER NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If ...