topic Re: splnkd can't find libjemalloc.so.1 in Installation

splnkd can't find libjemalloc.so.1

frnkhng — Tue, 07 Jan 2014 02:52:01 GMT

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?

Re: splnkd can't find libjemalloc.so.1

Ayn — Tue, 07 Jan 2014 07:34:53 GMT

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.

Re: splnkd can't find libjemalloc.so.1

marcoscala — Mon, 28 Sep 2020 15:42:02 GMT

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 2.6.32-220.17.1.el6.x86_64 #1 SMP Thu Apr 26 13:37:13 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

Re: splnkd can't find libjemalloc.so.1

MuS — Tue, 15 Apr 2014 07:43:33 GMT

Hi marco, this is the same run btool like this

$SPLUNK_HOME/bin/splunk cmd btool .....

Re: splnkd can't find libjemalloc.so.1

mikemaki — Fri, 23 Jan 2015 13:22:32 GMT

sudo $SPLUNK_HOME/bin/splunk start

Re: splnkd can't find libjemalloc.so.1

jg3 — Wed, 08 Jul 2015 17:03:07 GMT

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