 |
Why do I get 'FKM stopped on this file - excessive update rate detected.' message? You get this error message when your current FKM setting cannot keep up with the fast updates on the file. By default, FKM reads a maximum of 20,000 lines per sample. If the limit is exceeded for 20 consecutive samples then processing of this file stops and displays the message "WARNING: FKM stopped on this file - excessive update rate detected." in the status column for that file. If a file is updating very quickly, the sampler can "fall behind" and not reach the end of the line at each sample. |
 |
Additional Information The "FKM stopped on this file - excessive update rate detected." error is not a message contained in the file(s) you are monitoring with FKM. Therefore, you cannot use the ignore key to ignore this error. To have this warning status cleared, you need to manually accept the file, or you can configure a timeout to have the sampler automatically accept it. The timeout setting is in the FKM sampler -> Advanced tab -> excessiveUpdatesTimeout (in seconds); it will make the sampler auto accept the warning and start reading the file from the end. Also, you can try modifying other FKM settings like maxLinesProcessed to allow it to read more than 20,000 lines and also increase the maxSamplesLagging to determine how many samples a file can lag for before the file is ignored as updating too fast. Adjusting these settings and lowering the FKM Sample interval will enable the NetProbe to do more frequent sampling and read more lines each time. Please refer to UNIVERSAL FKM Plug-in User Guide for more details about FKM and the settings. |
-
Tags:
Comments
0 comments
Please sign in to leave a comment.