Deployment Architecture

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

bmacias84
Champion

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.

1 Solution

bmacias84
Champion

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.

View solution in original post

bmacias84
Champion

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.

Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In January, the Splunk Threat Research Team had one release of new security content via the Splunk ES Content ...

Expert Tips from Splunk Professional Services, Ensuring Compliance, and More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Release Update: AI Assistant, AppD + Observability Cloud Integrations & ...

This month’s releases across the Splunk Observability portfolio deliver earlier detection and faster ...