Deployment Architecture

Why Windows Search Head generates a Lock file after restart and how to permanently prevent this?

OMohi
Path Finder

Hi All:

I am facing an issue where the Splunk daemon after a recycle generates a lock file on Search Head. I am required to keep on deleting the pid lock file under $SPLUNK_Home\var directory. We have Search Head on windows platform. Is there a clean way of restart or how can I permanently get rid of these pid config locks.

Tags (2)
0 Karma
1 Solution

OMohi
Path Finder

This is a known bug in Version 6.1.2 which has been alleviated by migrating to version 6.1.4.

View solution in original post

0 Karma

OMohi
Path Finder

This is a known bug in Version 6.1.2 which has been alleviated by migrating to version 6.1.4.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

What version are you running?

0 Karma

bmacias84
Champion

question are you running splunk as local system or as a service account?

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...