FKM - unable to access monitored file

This problem is related to the following:

• Unable to access logfile
• Unable to access FKM file
• Permission denied
• No such file or directory

Problem Copied

• Linux

You can see the following error in the Netprobe log:

ERROR: FKM2[FKM test] Failed to open file /home/sandbox/temp/testfile. Error code 13 (Permission denied).

Screenshot of FKM dataview in the Active Console:

• Windows

You can see the following error in the Netprobe log:

2021-08-17 18:10:44.217+0800 ERROR: FKM2[FKM] Failed to open file D:\temp\file.txt. Error code 2 (No such file or directory).

FKM dataview in the Active Console:

Possible causes Copied

• File is not existing in the directory.
• The Netprobe user does not have permissions to file monitored or the file’s parent directories. This can also occur if the wildcard pattern matches multiple directories, some of which may be protected.

Possible solutions Copied

• File should be existing in the defined directory. If filename or directory is incorrect, you need to update it to the correct filename or directory in the FKM sampler.
• You need to ensure the Netprobe has the necessary permission (read access) to both the directories and the files. If there are sufficient file permissions, the Active Console displays OK in the status column.

For more information, see File Keyword Monitor (FKM) documentation.