Applications Systems

Checksum does not match in the File Change Monitor template

This article describes an issue where the File Change Monitor template does not verify the checksum data against file. For example, the template does not verify the checksum data in increments of every 300 seconds to determine if the data has changed. The File Change Monitor template tests if a file is modified. The component monitor performs an MD5 checksum comparison on the file to verify that it was not modified. The statistic is the number of hours since the file modification.

First published date

11/12/2018 2:25 AM

Last published date

1/5/2022 6:20 AM

Overview

This article describes an issue where the File Change Monitor template does not verify the checksum data against a file. For example, the template does not verify the checksum data in increments of every 300 seconds to determine if the data has changed.

The File Change Monitor template tests if a file is modified. The component monitor performs an MD5 checksum comparison on the file to verify that it was not modified. The statistic is the number of hours since the file modification.

Product section

Server Application Monitor

Cause

n/a

Resolution

Download the checksum data of the file on the network share. The data should match the data in the file to be monitored.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.