Monitoring Splunk

btool relocation error

LCM
Contributor

I get following error when trying to execute btool

root@usmaster: # btool Warning: program compiled against libxml 207 using older 206 ld.so.1: btool: fatal: relocation error: file /opt/splunk/bin/btool: symbol xsltInit: referenced symbol not found Killed

Library seems to be ok though:

root@usmaster: # ldd ./btool libthread.so.1 => /usr/lib/libthread.so.1 librt.so.1 => /usr/lib/librt.so.1 libpcre.so.0 => /opt/splunk/lib/libpcre.so.0 libxml2.so.2 => /usr/lib/libxml2.so.2 libxslt.so.1 => /usr/lib/libxslt.so.1 libssl.so.0.9.8 => /opt/splunk/lib/libssl.so.0.9.8 libcrypto.so.0.9.8 => /opt/splunk/lib/libcrypto.so.0.9.8 libdl.so.1 => /usr/lib/libdl.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libarchive.so.2 => /opt/splunk/lib/libarchive.so.2 libbz2.so.1 => /usr/lib/libbz2.so.1 libz.so.1 => /usr/lib/libz.so.1 libsqlite3.so.0 => /opt/splunk/lib/libsqlite3.so.0 libm.so.1 => /usr/lib/libm.so.1 libc.so.1 => /usr/lib/libc.so.1 libaio.so.1 => /usr/lib/libaio.so.1 libmd.so.1 => /usr/lib/libmd.so.1 libpthread.so.1 => /usr/lib/libpthread.so.1 libm.so.2 => /usr/lib/libm.so.2 libmp.so.2 => /usr/lib/libmp.so.2 libscf.so.1 => /usr/lib/libscf.so.1 libdoor.so.1 => /usr/lib/libdoor.so.1 libuutil.so.1 => /usr/lib/libuutil.so.1 libgen.so.1 => /usr/lib/libgen.so.1

Additional Stuff:

root@usmaster: # uname -a SunOS usmaster 5.10 Generic_142910-17 i86pc i386 i86pc root@usmaster: # splunk version Warning: overriding $SPLUNK_HOME setting in environment ("/opt/splunk/diag-usmaster-2011-02-02/etc") with "/opt/splunk". If this is not correct, edit /opt/splunk/etc/splunk-launch.conf Splunk 4.1.6 (build 89596) root@usmaster: #

Tags (1)
1 Solution

yannK
Splunk Employee
Splunk Employee

use splunk to call btool, the library will be the splunk ones, not the system ones.

by example, to check the list of the inputs

cd $SPLUNK_HOME/bin
./splunk cmd btool inputs list --debug

View solution in original post

yannK
Splunk Employee
Splunk Employee

use splunk to call btool, the library will be the splunk ones, not the system ones.

by example, to check the list of the inputs

cd $SPLUNK_HOME/bin
./splunk cmd btool inputs list --debug
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...