Splunk Search

What does 'ERROR IndexProcessor - caught exception for index=os during initialzation: 'Splunk has detected that a directory has been manually copied into its database, causing id conflicts" mean?

mctester
Communicator

I had to migrate a some indexes over from one instance to another. All worked but the 'os' index, and I'm seeing this error in splunkd.log:

ERROR IndexProcessor - caught exception for index=os during initialzation: 'Splunk has detected that a directory has been manually copied into its database, causing id conflicts [/splunk/var/lib/splunk/os/db/db_1302106859_1302041818_0, /splunk/var/lib/splunk/os/db/db_1289448788_1286384533_0].'.Disabling the index, please fix-up and run splunk enable index

Can you tell me how to fix this index and get it back online? Or is it more complicated than that?

Tags (3)

gkanapathy
Splunk Employee
Splunk Employee

Rename the directory, replacing the number _0 at the end with a number that does not conflict with the number of any existing db_* folder or any hot_* folder. Do not modify other parts of the folder name.

dragoslungu
Explorer

Thank you gkanapathy ! 4 years later and it still saves lives 🙂

0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...