Security

databasePartitionPolicy - cannot access lock file

vadud3
Path Finder

I am getting few warnings like these

08-24-2011 14:32:48.373 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.
08-24-2011 14:34:33.103 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.
08-24-2011 14:34:54.101 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.
08-24-2011 14:35:52.974 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/acme_cdrs/hot_v1_4.lock. Ignoring file.
08-24-2011 14:35:55.952 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.
08-24-2011 14:36:37.841 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.
08-24-2011 14:37:19.843 +0000 WARN  databasePartitionPolicy - Cannot access /opt/splunk/var/lib/splunk/audit/hot_v1_4.lock. Ignoring file.

Any suggestion on how to address this?

Tags (3)
1 Solution

yannK
Splunk Employee
Splunk Employee

Hi Vadud3

A bucket can be locked by creating this file during 3 operations,
to avoid running more than one of them concurrently on the same bucket :

  • fsck (bucket check after a restart)
  • move (to warm or cold or frozen)
  • delete (to frozen or the empty darkness of the void)

When splunk is calculating the size of an index, it may log the warning you saw, if the lock file disappeared between the beginning and the end of the calculation.
this is not a relevant Warning.

View solution in original post

yannK
Splunk Employee
Splunk Employee

Hi Vadud3

A bucket can be locked by creating this file during 3 operations,
to avoid running more than one of them concurrently on the same bucket :

  • fsck (bucket check after a restart)
  • move (to warm or cold or frozen)
  • delete (to frozen or the empty darkness of the void)

When splunk is calculating the size of an index, it may log the warning you saw, if the lock file disappeared between the beginning and the end of the calculation.
this is not a relevant Warning.

jrodman
Splunk Employee
Splunk Employee

BTW, this message no longer exists in Splunk 4.3

0 Karma
Get Updates on the Splunk Community!

Why You Can't Miss .conf25: Unleashing the Power of Agentic AI with Splunk & Cisco

The Defining Technology Movement of Our Lifetime The advent of agentic AI is arguably the defining technology ...

Deep Dive into Federated Analytics: Unlocking the Full Power of Your Security Data

In today’s complex digital landscape, security teams face increasing pressure to protect sprawling data across ...

Your summer travels continue with new course releases

Summer in the Northern hemisphere is in full swing, and is often a time to travel and explore. If your summer ...