After starting Splunk on a Heavy Forwarder following maintenance activity, starting from the CLI showed "Conf is currently being modified by process <pid>", proceeds to kill that PID, then states the Web UI is not available.

Though Splunkd appeared to be running, it may not forward data.
Review of Splunkd.log shows Splunkd has encountered a file lock:
11-30-2024 13:18:46.050 -0500 WARN loader [0 MainThread] - Sleep 10 sec, waiting for config lock.
11-30-2024 13:18:56.072 -0500 WARN loader [0 MainThread] - Sleep 10 sec, waiting for config lock.
11-30-2024 13:19:06.093 -0500 WARN loader [0 MainThread] - Sleep 10 sec, waiting for config lock.
11-30-2024 13:19:16.116 -0500 WARN loader [0 MainThread] - Sleep 10 sec, waiting for config lock.
11-30-2024 13:19:26.138 -0500 WARN loader [0 MainThread] - Sleep 10 sec, waiting for config lock.
11-30-2024 13:19:36.138 -0500 FATAL loader [0 MainThread] - Timed out waiting for config lock; see splunkd_stderr.log for details. Exiting.
./splunk stop./splunk clean locks$SPLUNK_HOME\var\run\splunk\./splunk startVerify Splunk has started correctly and data is flowing.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |