Getting Data In

INFO DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket

bishtk
Communicator

Dear Splunk Professionals,

We are having an On-Premise Splunk 6.2.0 (build 237341)setup with two servers. One being Indexer and other Searchhead. We are not using any Forwarder in our environment. Data are directly mounted from Application servers to our Indexer.
Recently I noticed that the data last indexed date was 21st Feb and after that no data is getting indexed. In the splunkd.log I am getting this INFO very frequently.

02-26-2018 06:16:40.090 +0100 INFO DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id= path="/opt/splunk/var/lib/splunk/defaultdb/db/hot_v1_98" (This is usually harmless as we may be racing with a rename in BucketMover or the S2SFileReceiver thread, which should be obvious in log file; the previous WARN message about this path can safely be ignored.) caller=getCumulativeSizeForPaths
02-26-2018 06:16:40.112 +0100 INFO DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id= path="/opt/splunk/var/lib/splunk/cal_XYZ/db/hot_v1_79" (This is usually harmless as we may be racing with a rename in BucketMover or the S2SFileReceiver thread, which should be obvious in log file; the previous WARN message about this path can safely be ignored.) caller=getCumulativeSizeForPaths
02-26-2018 06:16:40.112 +0100 INFO DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id= path="/opt/splunk/var/lib/splunk/cal_UVW/db/hot_v1_80" (This is usually harmless as we may be racing with a rename in BucketMover or the S2SFileReceiver thread, which should be obvious in log file; the previous WARN message about this path can safely be ignored.) caller=getCumulativeSizeForPaths

Can you please help me here how to rectify this and if its related to data not getting indexed?

Thanks,

0 Karma

bishtk
Communicator

Dear Splunkers,

Any suggestion on this as I am still facing this issue and also the data is not getting indexed with these being the only error under splunkd.log

-Thanks in advance

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...