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!

How much can you really learn in 3 minutes?

Observability can certainly be hard to understand – there's a lot of jargon and buzzwords and it seems to ...

Event Series: The Agentic SOC: Trust Before Autonomy

AI is fundamentally changing security operations, but true progress requires more than just automation—it ...

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...