topic 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? in 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 — Thu, 07 Apr 2011 07:25:21 GMT

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?

Re: 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?

gkanapathy — Thu, 07 Apr 2011 12:33:27 GMT

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.

Re: 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?

dragoslungu — Thu, 26 Nov 2015 07:57:44 GMT

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