Installation

ERROR DatabaseDirectoryManager

drjly
Engager

Hi

Can anyone help on why i get this err

11-12-2013 13:18:16.521 +0100 ERROR DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id=_audit~10~650A7B6A-853B-4339-A42B-41498DE0DBC2
11-12-2013 13:18:16.522 +0100 ERROR DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id=_internal~130~650A7B6A-853B-4339-A42B-41498DE0DBC2
11-12-2013 13:18:17.684 +0100 ERROR DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id=_audit~10~650A7B6A-853B-4339-A42B-41498DE0DBC2
11-12-2013 13:18:17.685 +0100 ERROR DatabaseDirectoryManager - Getting size on disk: Unable to get size on disk for bucket id=_internal~130~650A7B6A-853B-4339-A42B-41498DE0DBC2

The err happens after upgrading from 5.0.3-163460 to 6.0-182037 on RHEL6

Regards
Jesper

Tags (1)

drjly
Engager

Found the problem some directories and files were owned by root and not the user running splunk. A bit of chown fixed tho problem

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...