Monitoring Splunk

ERROR BucketMover

abhayneilam
Contributor

Hi, I am getting the below error in splunkd.log :

07-24-2014 01:30:51.609 +0200 INFO BucketMover - will attempt to freeze: candidate='/opt/SP/apps/splunk/splunk-6.0.1/var/lib/splunk/rest/db/db_1392823223_1392819715_1' because

frozenTimePeriodInSecs=2419200 exceeds difference between now=1406158251 and latest=1392823223
07-24-2014 01:30:51.664 +0200 ERROR BucketMover - sizeBytes=12288 candidateBytes=19456
07-24-2014 01:30:51.760 +0200 ERROR BucketMover - sizeBytes=1486336 candidateBytes=1574400

Please let me know how to solve this one !!

Tags (1)

vhallan_splunk
Splunk Employee
Splunk Employee

This issue has been fixed in 6.0.6 and planned to be fixed in 6.1.4. The problem is that the bucket is attempting to freeze and due to an error the bucket does not role to frozen. Workaround is to delete/move the bucket manually.

0 Karma

abhayneilam
Contributor

After some time in the search head UI it is showing :

Splunkd daemon is not responding: ('Error connecting to /servicesNS/name.title%40xxx.com/apix/search/jobs: The read operation timed out',)

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

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