Getting Data In

Why did our Splunk forwarder die getting "ERROR ProcessRunner - helper process seems to have died (child killed by signal 15: Terminated)"?

itmonitoring
Explorer

FATAL ProcessRunner - Unexpected EOF from process runner child!
ild killed by signal 1510-24-2014 06:42:23.633 -0600 ERROR ProcessRunner - helper process seems to have died (child killed by signal 15: Terminated)

yaseen417
New Member

There's a possibility that, instead of using splunk restart/stop/start, splunkd is used which is a daemon itself.

0 Karma

lguinn2
Legend

Signal 15 is sent to a process by the Linux kill command. Is it possible that someone killed the process?

0 Karma

itmonitoring
Explorer

As per logs nobody kills it manually still looking for the reason...

0 Karma

ben_leung
Builder

This also occurred on the indexer level but instead with a signal 9 in splunkd.log for version 6.0.5, is this known issue?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...