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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

    Thursday, June 25, 2026  |  11AM PDT / 2PM EDT  Duration: 1 Hour (Includes live Q&A) Register to ...

Analytics Workspace deprecation

As of Splunk Cloud Platform 10.4.2604 and Splunk Enterprise 10.4, Analytics Workspace is now deprecated. ...

Splunk Developer Day Recap: Building, Publishing, and Growing on the Splunk Platform

Splunk Developer Day brought the Splunk developer community together for a practical look at what it means to ...