During the upgrade to Splunk 9.4.0, errors began to appear on several components (including the Search Head, Cluster Manager, Enterprise Security, and Splunk App Service) due to problems with the KVstore. Additionally, an unchanged Git repository triggered startup failures in Splunk. The only temporary workaround involved is moving the Git repository to a different directory, which is not a viable long-term solution.
Version Control was introduced in 9.4 version. It lets users track dashboard edits, add comments per version, compare versions (diff view), and revert to previous versions.
grep -m 1 -B 2 'FATAL VersionControlInitialiser' /opt/splunk/var/log/splunk/splunkd.log
01-23-2025 13:10:24.332 -0500 ERROR VersioningRepo [47037 MainThread] - Failed to open version control repository in path="/opt/splunk/var/vcs", reason=code=-3,description="could not find repository at '/opt/splunk/var/vcs'"
01-23-2025 13:10:24.332 -0500 ERROR VersioningRepo [47037 MainThread] - Failed to initialize version control repository in path="/opt/splunk/var/vcs", reason=code=-1,description="cannot overwrite gitlink file into path '/opt/splunk/etc/'"
01-23-2025 13:10:24.332 -0500 FATAL VersionControlInitialiser [47037 MainThread] - Cannot initialise the repo: cannot overwrite gitlink file into path '/opt/splunk/etc/'
Received fatal signal 6 (Aborted) on PID 1952725.
Cause:
Signal sent by PID 1952725 running under UID 1000.
Crashing thread: MainThread...Backtrace (PIC build):
[0x000055AEA582C9E8] _ZN21DisablableRepoManager24createRepoManagerOrAbortERK20VersionControlConfig + 40 (splunkd + 0x462A9E8)
[0x000055AEA582CA56] _ZN21DisablableRepoManager4initERK20VersionControlConfig + 54 (splunkd + 0x462AA56)
[0x000055AEA582CB73] _ZN20ConfServiceSetHolder29initVersionControlRepoManagerER13PropertyPagesRK8Pathname + 99 (splunkd + 0x462AB73)
[0x000055AEA2D4407E] ? (splunkd + 0x1B4207E)
[0x00007F4D01C207E5] __libc_start_main + 229 (libc.so.6 + 0x3A7E5)
Linux / xxxxxxxxx / 4.18.0-553.44.1.el8_10.x86_64 / #1 SMP Wed Mar 5 10:48:41 EST 2025 / x86_64
Last few lines of stderr (may contain info on assertion failure, but also could be old):
2025-03-20 19:22:31.551 -0400 splunkd started (build c103a21bb11d) pid=1908
2025-04-08 12:21:31.475 -0400 Interrupt signal received sent by PID 1939534, command="/app/splunkforwarder/bin/splunk stop" (UID 1000, same as my group)
2025-04-08 12:24:33.006 -0400 splunkd started (build e3bdab203ac8) pid=1940653
2025-04-08 12:25:29.181 -0400 splunkd started (build e3bdab203ac8) pid=1941417
2025-04-08 12:25:55.279 -0400 splunkd started (build e3bdab203ac8) pid=1942040
2025-04-08 12:41:22.235 -0400 splunkd started (build e3bdab203ac8) pid=1944323
2025-04-08 12:42:19.617 -0400 splunkd started (build e3bdab203ac8) pid=1944598
2025-04-08 13:28:31.775 -0400 splunkd started (build e3bdab203ac8) pid=1952123
2025-04-08 13:32:07.283 -0400 splunkd started (build e3bdab203ac8) pid=1952725
To resolve the issue, update the configuration so that version control features operate as expected:
Open the file:
$SPLUNK_HOME/etc/system/local/server.conf
Add or verify the following lines:
[version_control] disabled = true
Disabling version control does not have a negative side effect, the feature added for control versioning will not be available only.
Track and maintain dashboard changes with version history
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |