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!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...