No log file exists

Symptoms

• When viewing a job history page in the FME Server web user interface, you see the error message No log file exists.
• The "Log" tab of the job view is disabled.
• When browsing the Logs resource, there are no job log files under Logs\engine\current\jobs

Cause

This is most often caused by the automated emergency cleanup procedure of FME Server (2015 and newer), which is triggered by default when disk space is low (< 10%).

Resolution

• The recommended resolution is to free some disk space, as this will stop the emergency cleanup, and ensure proper functioning of FME Server and any other services the machine may be running.
• If you are unable to clear enough disk space, or you have other automated cleanup procedures in place, you may wish to set a higher threshold for disk use. This involves editing the configuration file for the cleanup service:

#--------------------------------------
# Cleanup Watch
#--------------------------------------
CLEANUP_WATCH_INTERVAL=300

CLEANUP_WARN_NOTIFICATION_TOPIC=
CLEANUP_WARN_MINDISKSIZE_GB=20
CLEANUP_WARN_MINDISKSIZE_PCT=20
CLEANUP_WARN_OP=AND

CLEANUP_CRITICAL_NOTIFICATION_TOPIC=
CLEANUP_CRITICAL_MINDISKSIZE_GB=10
CLEANUP_CRITICAL_MINDISKSIZE_PCT=10
CLEANUP_CRITICAL_OP=AND