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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

 Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

What's New in Splunk Observability - August 2025

What's New We are excited to announce the latest enhancements to Splunk Observability Cloud as well as what is ...

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...