Back to ITRS Internal Only FAQ

Internal documentation only

This page has been marked as draft.

WARN: FKM2[<SamplerName>] Active time notification from <Filename> delayed by <LargeValue> secs. Delay threshold (5 secs) exceeded. Callback will be ignored to avoid possible data loss due to content skipped

FKM

Problem Copied

The Netprobe logs contain a WARN message indicating that the FKM plugin has detected a delay in receiving active time notifications from a monitored file. This manifests as a warning in the logs and may cause a temporary gap in file processing.

The log entry appears as follows:

WARN: FKM2[<SamplerName>] Active time notification from <Filename> delayed by <LargeValue> secs. Delay threshold (5 secs) exceeded. Callback will be ignored to avoid possible data loss due to con

Possible cause(s) Copied

Possible solution(s) Copied

Whenever an Active Time comes into effect, the FKM sampler executes a callback function to determine if it needs to process files. However, due to Netprobe performance considerations (e.g., being busy due to other samplers’ activities), it could happen that the notification for the Active Time being in effect is delayed.

Hence, the callback function first checks how much time has passed since the particular Active Time came into effect. If the time between the Active Time’s start time and the moment when the callback function received the notification is greater than five (5) seconds (i.e., activeTimeStart - activeTimeNowActiveNotificationReceived > 5), the callback function logs this warning and does not proceed in checking if there are files which need to be processed. This is done to prevent possible significant data loss due to file content skipping—the file(s) may have already been processed in an earlier sample.

Basically, this is just a fail-safe warning: when the Netprobe detects the active time notification kicking in to active but met with a slight delay, it will instruct the FKM to scan for a few lines prior so that it will ensure that no valid data was lost. This is a fix put in place since earlier probes kept the file scans in the background even when it is out of active time.

["Geneos"] ["FAQ"]

Was this topic helpful?