Hi All,
I installed splunk enterprise in a RedHat Enterprise Linux x86_64 with rpm sucessfully.
But when I run the splunkd, there is below error:
bin/splunkd: error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory
I checked and found the libjemalloc.so.1 and libjemalloc.so in /usr/local/lib, why splunk can't find it?
You shouldn't be running splunkd directly. You should run bin/splunk which is responsible for setting up the proper environment for splunkd to operate in, and it then launches splunkd.
maybe do this:
sudo ln -s /opt/splunk/bin/splunk /etc/init.d/.
... so when your system restarts the correct splunk binary gets the "start" signal.
If you followed the documentation for installing and starting splunk the first time, you probably assumed (as I did) that calling sudo -u splunk /opt/splunk/bin/splunkd start —accept-license
would work for subsequent starts, and then got the libjemalloc.so.1 error. As mentioned above, giving the start command to the splunk binary (not splunkd) solves this. So the real answer to your question (assuming you've installed in the default /opt/splunk/ path) is:
sudo /opt/splunk/bin/splunk start
sudo $SPLUNK_HOME/bin/splunk start
Same error running the following command:
./btprobe -d /opt/splunk/var/lib/splunk/fishbucket/splunk_private_db/ --file /opt/splunk/var/log/
/opt/splunk/bin/splunkd: error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory
uname -a:
Linux
Hi marco, this is the same run btool like this
$SPLUNK_HOME/bin/splunk cmd btool .....
You shouldn't be running splunkd directly. You should run bin/splunk which is responsible for setting up the proper environment for splunkd to operate in, and it then launches splunkd.