What to do if your MFT directory resource monitor is not triggering files

A directory resource monitor polls a directory for files that match a trigger specification. For each file that matches the trigger specification, a transfer request is generated to the agent. When the request is submitted, the triggering file is ignored until the file is changed.

Possible reasons why the files are not triggering

The directory resource monitor found a file that matched the trigger specification, but the generated transfer request was invalid and the agent was unable to process the request. The reasons can include the following:
- Invalid destination agent
- Missing destination agent
- Transfer canceled by program invocation
In all these examples, the directory resource monitor marks the triggering file as processed and ignores the file even though the transfer failed.
The file is outside the scope of the resource monitor trigger specification. The reasons can include the following:
- Incorrect trigger pattern
- Monitoring the incorrect directory
- Insufficient file permissions
- Failure to connect to remote file system

Why a file can trigger a second transfer

A trigger file can generate a Managed File Transfer transfer request for the following reasons:

If the presence of the trigger file is detected, when it was not there before.
If the trigger file has been updated, causing the last modified date to change.

Potential scenarios for a second trigger are:

The file is removed, then replaced.
The file is locked by one application, then unlocked by another application.
The monitor file system fails. For example, if the network connection fails, this can give the appearance of the file being removed, then replaced.
The file directory is updated by another application, causing the last modified date to change.

Command to set info level output for all resource monitors of an agent

In this example, all resource monitors are being monitored because you have not specified a name, or names, of specific resource monitors. The name of the agent is AGENT1.

fteSetAgentLogLevel -logMonitor=info AGENT1

See fteSetAgentLogLevel for details of the logMonitor parameter, and examples of how you use the different options.

Example of info level output for all resource monitors of an agent


==================================================================================================================================================================
[21/04/2017 11:08:49:367 IST] BFGUT0036I: Resource monitor event log level has changed to "info" for all resource monitors of this agent.
==================================================================================================================================================================

==================================================================================================================================================================
Date        Time              Thread ID   Monitor Name                      Event               Description                                             
==================================================================================================================================================================
[21/04/2017 11:08:51:842 IST] 00000023    QMON                              Monitor Started     Resource Monitor Started
[21/04/2017 11:08:51:844 IST] 00000025    QMON                              Start Poll          New poll cycle started
[21/04/2017 11:08:51:924 IST] 00000023    MON1                              Monitor Started     Resource Monitor Started
[21/04/2017 11:08:51:925 IST] 00000026    MON1                              Start Poll          New poll cycle started
[21/04/2017 11:08:52:029 IST] 00000026    MON1                              End Poll            Poll cycle completed in 105 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:08:52:055 IST] 00000025    QMON                              End Poll            Poll cycle completed in 212 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:09:51:840 IST] 00000025    QMON                              Start Poll          New poll cycle started
[21/04/2017 11:09:51:875 IST] 00000025    QMON                              End Poll            Poll cycle completed in 34 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:09:51:924 IST] 00000026    MON1                              Start Poll          New poll cycle started
[21/04/2017 11:09:51:969 IST] 00000026    MON1                              End Poll            Poll cycle completed in 45 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:10:51:840 IST] 00000025    QMON                              Start Poll          New poll cycle started
[21/04/2017 11:10:51:924 IST] 00000026    MON1                              Start Poll          New poll cycle started
[21/04/2017 11:10:51:962 IST] 00000025    QMON                              End Poll            Poll cycle completed in 121 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:10:51:963 IST] 00000026    MON1                              End Poll            Poll cycle completed in 39 milli seconds. Trigger items matched [ 0 ]
[21/04/2017 11:10:55:063 IST] 00000041    MON1                              Monitor Stopped     Resource Monitor Stopped
[21/04/2017 11:10:55:079 IST] 00000041    QMON                              Monitor Stopped     Resource Monitor Stopped