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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...