Job Troubleshooting

Review the content in Notes for Testing Job Actions. This topic summarizes key features that are helpful to new users.

To view log messages, use the Gateway Administrator and Hub server.log files.

The Gateway Administrator log file is on the system running the Reflection Gateway Administrator service. The default log location is:

C:\Program Files\Micro Focus\ReflectionGateway\ReflectionGateway\logs\server.log
The Hub log file is on the system running the Reflection Hub service. The default log location is:

C:\Program Files\Micro Focus\ReflectionGateway\Hub\logs\server.log

NOTE:If you are running multiple Hubs, Job actions are distributed between the Hubs, and log information for a single Job may be in multiple logs. To simplify troubleshooting, you may want to temporarily disable the other Hubs.

Also review the following troubleshooting guidelines.

Problem: You receive a success notification or see “step succeeded” in the server log, but files are not where you expect them to be.

Review the information in Set Up Directory Access on your SFTP Servers. This topic describes where files are created by default for both transfer and command Job actions.

Problem: When you click Run Now to test a Job, no files are transferred, no success or failure notifications are sent, and the Gateway Administrator log shows no error messages.

Confirm that you have newly modified files in the scan directory. If there have been no changes to the files since your last test (whether it was a success or a failure), no action will be taken.
If you want to receive failure notices when no files are found in a scan that meet the scan criteria, on the New/Edit > Job page, enable Execute failure action at the end of each scan interval if files do not meet filter conditions.
To view additional logging, including scan messages, enable debug logging to the Gateway Administrator server log.

Problem: A file transfer Job fails. If you have a failure action configured, you receive a failure notification.

If the Gateway Administrator server log file includes an ERROR message similar to this:

Scanning failed: com.attachmate.mft.hub.fileserver.FileServer Exception: Could not connect to SFTP server.

The source SFTP server may be down or unavailable.

If the Gateway Administrator server log file includes a WARN message in this format:

Failed to open destination file '/pathto/filename' on DestinationServerName:

The destination SFTP server may be down or unavailable
The UserID configured for connecting to this SFTP server may not have access rights to the specified destination directory. Review the following information:

Set Up Directory Access on your SFTP Servers.

Entering Expressions for Destination Files

Problem: A command execution Job fails. If you have a failure action configured, you receive a failure notification. The Gateway Administrator server log file includes a WARN message saying:

One or more command executions failed.

If you have specified a Windows system command, confirm that the command is preceded by cmd /c. For example:

cmd /c echo $FILENAME$ >> c:\pathto\output.txt
If your command directs output to using a fully-qualified path (as shown above), confirm that the user configured for connecting to this SFTP server has access to the location. The command is executed as a remote SSH command using the user account specified for the UserID of the server.
If you specify a command without including full path information to the executable file, confirm that the executable is on the path of the SFTP server running the command, or is available in the user’s login directory.
Use an SSH command line client to test your command on the host, as shown here:

ssh user@host "command_entered_in_job_action"