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.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...