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

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...