Installation

Splunk forwarder not starting on linux with error - pid terminated signal 4

zulfikharnaiyar
Explorer

Hello,

We've installed a linux UF on a supported distribution. Done this on multiple machines but facing an issue on a single server. The forwarder fails to start with the following error:

./splunk start

Starting Splunk...
Splunk> All batbelt. No tights.
Checking prerequisites...
Checking mgmt port [8089]: open
Checking conf files for problems...
Done
Checking default conf files for edits...
Validating installed files against hashes from '/opt/splunkforwarder/splunkforwarder-8.2.0-e053ef3c985f-linux-2.6-x86_64-manifest'
All installed files intact
Done
All preliminary checks passed.

Starting Splunk server daemon (splunkd)...
ERROR: pid 90702 terminated with signal 4

Done [ OK ]

 

Tried installing it as a daemon as well. It doesn't report any error but the service fails to start. When starting directly from the bin folder, get the above error.

Any helpful pointers here please? 

Thanks.

 

Regards,

Labels (1)
0 Karma
1 Solution

zulfikharnaiyar
Explorer

Hi @SRG9 ,

Thank you for your input however it was not the case.

The splunkd service was being terminated by a dynatrace agent installed on the machine. Apparently dynatrace agent (liboneagentproc.so) injects  itself to check any service which is being initiated and was terminating the splunk process with an illegal opcode error.

Removing the dynatrace agent solved the issue in our case. However, it would've been ideal if both the solutions could coexist on the same host.

 

View solution in original post

0 Karma

SRG9
Explorer

Hi @zulfikharnaiyar 

I am not sure if below solution works , 

can you rename the splunkd.pid to splunkd.pid_old present in following location and start the splunk?.

/opt/splunkforwarder/var/run/splunk/

0 Karma

zulfikharnaiyar
Explorer

Hi @SRG9 ,

Thank you for your input however it was not the case.

The splunkd service was being terminated by a dynatrace agent installed on the machine. Apparently dynatrace agent (liboneagentproc.so) injects  itself to check any service which is being initiated and was terminating the splunk process with an illegal opcode error.

Removing the dynatrace agent solved the issue in our case. However, it would've been ideal if both the solutions could coexist on the same host.

 

View solution in original post

0 Karma

scelikok
SplunkTrust
SplunkTrust

There is also information on Dynatrace website about Splunk 8.2.

https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/oneaget-troublesho...

There is no workaround yet.

If this reply helps you an upvote is appreciated.
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!