Splunk Enterprise

Integrity check warning

BRFZ
Communicator

Hello,

I recently upgraded my Splunk instances to version 10.4.x and started seeing integrity check warnings affecting several files.

The check result is:

present_but_shouldnt_be

Has anyone else encountered this after upgrading to Splunk 10.4.x? Is this expected behavior or related to the upgrade process? If anyone knows what should be done in this case.

Thanks for your help!

Labels (2)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

It depends on the actual files (and the upgrade process - RPM/deb should remove old files, simply unpacking tgz over old directory won't).

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Analytics Workspace removal in Splunk 10.6

In Splunk Cloud Platform and Splunk Enterprise 10.6, Analytics Workspace is removed from product and no longer ...

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...