Deployment Architecture

error starting universal forwarder

a212830
Champion

I am getting the following error starting up a UF on Windows 2008 64-bit server:

4-16-2013 15:57:26.770 -0400 FATAL loader - Timed out waiting for config lock; see splunkd_stderr.log for details.

I don't see a splunkd_stderr.log in ../var/log/splunk. Would it be somewhere else? I also get an error 1067 when trying to start it via services.

Tags (1)
1 Solution

kristian_kolb
Ultra Champion

jrodman
Splunk Employee
Splunk Employee

On Windows, we lack a splunkd_stderr.log, so this message is misleading.

However, the most likely cause of the problem is fixed in Splunk 6.1.3. If you see it after 6.1.3, then you may want to doublecheck permissions etc on var/run/splunk/conf-mutator.pid and/or contact support.

0 Karma

kristian_kolb
Ultra Champion

It should be in $SPLUNK_HOME/var/log/splunk

Have a look here;

http://splunk-base.splunk.com/answers/73843/splunk-will-not-start-and-is-waiting-for-config-lock

/K

a212830
Champion

That worked. Thanks!

0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...