Installation

Why am I getting splunkd "ERROR: pid 8610 terminated with signal 11" after fedora 3.11.10 Splunk install?

Jagmeet_Arora
Engager

Hi

Did anybody face following issue with fedora 3.11.10 splunk installation:

[root@splunk bin]# ./splunk start

Splunk> All batbelt. No tights.

Checking prerequisites...
Checking http port [8000]: open
Checking mgmt port [8089]: open
.....
.....
All preliminary checks passed.

Starting splunk server daemon (splunkd)...

ERROR: pid 8610 terminated with signal 11

splunkweb process is able to start without any issue. I have tried clean uninstall and re-install with both rpm and tar packages: splunk-6.1.3-220630-Linux-i686.tgz

Requesting splunk team and community members to help resolve the issue.

Thanks

Labels (1)
0 Karma
1 Solution

grijhwani
Motivator

Sig 11 is SIGSEGV - boundary violation. It signifies an out-of-bounds access which in turn suggests a hardware fault (usually RAM or processor) or attempting to run code on the wrong architecture.

On the whole a Splunk installation is self-contained enough that it is dependent only on the right minimum kernel version, all substantial support libraries being statically linked or packaged locally with it. That said, I don't think it is certified to run on Fedora.

View solution in original post

grijhwani
Motivator

Sig 11 is SIGSEGV - boundary violation. It signifies an out-of-bounds access which in turn suggests a hardware fault (usually RAM or processor) or attempting to run code on the wrong architecture.

On the whole a Splunk installation is self-contained enough that it is dependent only on the right minimum kernel version, all substantial support libraries being statically linked or packaged locally with it. That said, I don't think it is certified to run on Fedora.

Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...