ConfPathFixer - Found dangling data at : /nobody/..

[bmacias84]

We upgrade from 4.3.3 to 5.0.5 last night now our Pool search heads receive the following messages during startup and while running ./splunk cmd btool fix-dangling. I am not familiar with the location nobody.

WARN ConfPathFixer - Found dangling data at: /nobody/<app>/props/<stanza>/CHECK_FOR_HEADER = false
WARN ConfPathFixer - Found dangling data at: /nobody/<app>/props/<stanza>/MAX_TIMESTAMP_LOOKAHEAD = 40
WARN ConfPathFixer - Found dangling data at: /nobody/<app>/props/<stanza>/NO_BINARY_CHECK = 1

This only seem to be happening to two stanzas.
If I remove the stanzas it works fine, the stanza is very similar to others expect for MAX_TIMESTAMP_LOOKAHEAD.

[bmacias84 · Accepted solution]

I discovered that this is a file level permission issue. Permission inheritance was broken on my Search Head Pool shared storage. Once the permission where restored this problem went away.

Make sure the Splunk user has the correct permissions to $SPLUNK_HOME/etc/apps dir and dispatch folders.