PID not removed from /proc directory on disabling the data input and hence not letting the other PID to initiate

sarthakchouhan — Tue, 04 Apr 2023 08:24:25 GMT

Hi there,

I am using a Technology Add-On with Splunk which uses the data input feature to ingest the data in Splunk. I came across one issue where the when I disabled the data input from the Splunk the PID with which it was running is still present in /proc directory oi Linux environment where Splunk is setup.

Due to the non-removal of PID, when re-enable the data input the PID is not able to initiate as it gets the impression that this job is already running with some older existing PID.

To overcome this I have to manually kill the older running PID which should be removed on disabling the data input.

Can someone please help to understand the root cause of why that PID is not getting removed or terminated when I disable the data input from the Splunk itself?

Why it is present in /proc directory due to which the other PID for the data ingestion job is not getting initiated?

It would be really helpful if I get some information on the root cause as I am continuously facing this issue

Thanks in Advance!!

Re: PID not removed from /proc directory on disabling the data input and hence not letting the other PID to initiate

richgalloway — Tue, 04 Apr 2023 13:05:10 GMT

This sounds like something you should contact Splunk Support about.

topic PID not removed from /proc directory on disabling the data input and hence not letting the other PID to initiate in Splunk Enterprise

PID not removed from /proc directory on disabling the data input and hence not letting the other PID to initiate

Re: PID not removed from /proc directory on disabling the data input and hence not letting the other PID to initiate