Security

Receiving this warning: "cannot create "/opt/splunk/var/log/watchdog"

dataops
Engager

Why am I receieving this error?

Warning: cannot create "/opt/splunk/var/log/watchdog"

Pid file "/opt/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
Pid file "/opt/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
Pid file "/opt/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
0 Karma

richgalloway
SplunkTrust
SplunkTrust

This can happen if Splunk is run as root and then run as a non-root user without changing the ownership of all files in /opt/splunk.

---
If this reply helps you, Karma would be appreciated.

codebuilder
Influencer

Agree with Rich, I've seen this behavior in the very same circumstances.

chown the pid file to the user running splunk.
e.g.
chown splunk:splunk /opt/splunk/var/run/splunk/splunkd.pid
cycle splunk

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma

Anam
Community Manager
Community Manager

Hi @dataops

Thank you for posting your question on Splunk Answers. In order for experts to help you, can you please provide more information in context that resulted in you seeing this error? Were you making changes to the authorize.conf file?

Thanks

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!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...