All Apps and Add-ons

Getting the following error when trying to start a forwarder on a linux system

Path Finder

I am getting an error after loading Splunk forwarder on a Linux server (this same load is on other Linux servers with no issues): 6a257470b sp:7ffeb4a673a0 error:0 in[7fd6a2560000+84000]
Aug 12 12:04:18 ladcivrnvpt03 kernel: traps: splunkd[66184] trap invalid opcode ip:7fd6a257470b sp:7ffeb4a673a0 error:0 in[7fd6a2560000+84000]

I run the ./splunk start --accept-license and it appears to start, but if you ps -eaf | grep splunk, nothing is started.  No log files are generated in .../splunkforwarder/var/log/splunk for the splunkd process either.

Labels (1)
0 Karma


The compatibility issue exists between Dynatrace and Splunk 8.2. 

The below link describes it and the resolution as well -

0 Karma


Invalid opcode can mean a few things.  Basically, the CPU saw an instruction it did not support and caused the kernel to trap and kill your splunkd process.  It died.

The message you pasted suggests the process death is related to, which Google tells me is part of Dynatrace.  Does your machine have Dynatrace on it?  If it does, can you get rid of it to test and see if this fixes Splunk?

You may need to open a support case with both Dynatrace and Splunk and get them to work together on the issue.  I would probably start w/ Dynatrace because their library seems to be the one causing splunkd to crash.


0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...