You are here: Reference Manual > About Log Files in FME Server

About Log Files in FME Server

FME Server creates log files for every workspace it runs and for all of its components. Use these logs to test and troubleshoot any issues related to the component that is not producing expected results.

To ensure that log files do not consume too much disk storage over time, FME Server is configured, by default, to delete old log files. You can manage automatic log file cleanup on the System Cleanup page of the FME Server Web User Interface.

Log files can be accessed on the Resources page (Logs folder) of the Web User Interface, or from the REST API.

Non-FME Cloud customers can also access log files in the <LogDir> directory:

  • Windows: C:\ProgramData\Safe Software\FME Server\resources\logs

    • C:\ProgramData is the default value of the %ALLUSERSPROFILE% environment variable. If this location is modified, the location specified above is modified accordingly.

  • Linux: <FMEServerDir>\Logs

WARNING: Log files are stored in the FME Server System Share location, which is specified at installation time. Moving the FME Server System Share to another location after installation is not supported. For more information, see Changing the File System to Another Machine.

Log files are grouped in subdirectories based on their function, in either a current or old directory. Log files are auto-archived from the current to the old directory when either of the following occurs:

  • A new log file of the same name is created.
  • The size of the file has reached 5000 lines of text.

You can control the way log files are auto-archived, and other properties of log files, by editing the applicable messagelogger.properties file. For more information, see Message Logger Properties.

FME Job Logs

Location:

<LogDir>\engine\current|old\jobs\<number>\job_<value>.log

Workspaces that are run from FME Server generate FME logs in the same manner as those run from FME Desktop. These files log the details of a translation performed by an FME Engine, and can provide important information when testing or troubleshooting jobs run from FME Server.

FME job logs can also be accessed by examining a job's properties from the Jobs page of the Web User Interface. The log is displayed under the Log tab, and can be downloaded as a text file.

FME job log files are stored and named using the following format:

\<number>\job_<value>.log

Where value is the job ID and number is the job ID group, which increments by thousand. Logs for job IDs from 0 - 999 are grouped into a 0 directory, Logs for job IDs from 1000 - 1999 are grouped into a 1000 directory, and so on.

FME Core Logs

Publisher Logs

Location:

<LogDir>\core\current|old\publishers

This directory provides logs for each of the Notification Service publisher protocols supported by FME Server. Each file logs activities of any publishers configured on the respective protocol.

Subscriber Logs

Location:

<LogDir>\core\current|old\subscribers

This directory provides logs for each of the Notification Service subscriber protocols supported by FME Server. Each file logs activities of any subscribers configured on the respective protocol.

Other Core Logs

Location:

<LogDir>\core\current|old\

fmeserver.log

This log is frequently used in testing and troubleshooting, and is created each time the FME Server is started. It shows:

  • Authentication and authorization information, including connecting to Active Directory, if applicable.
  • Connection parameters relating to the FME Server Database.
  • Messages created by the Transformation Manager and the Repository Manager.
  • The job_id of a specific job and its life cycle, including submission to the queue, processing by an FME Engine, and completion.

fmeconfiguration.log

Logs activity when performing a backup and restore.

fmeprocessmonitorcore.log

Process monitor logs are frequently used in testing and troubleshooting. A new process monitor log is created each time the FME Server is started. This log details the FME Server components that were started and if any components were restarted at any time.This log shows translation (workspace) jobs that are submitted to the queue.

fmescheduler.log

The scheduler log records the startup and shutdown of the Scheduler component, and every workspace run by the Scheduler.

fmesharedresource.log

This log records activity that affects any shared resource directories.

FME Engine Logs

Location:

<LogDir>\engine\current|old\<fmeEngine_Engine#>.log

This log provides information about startup and translation processes of FME Engines. By default, every time you restart the FME Server service this log file is re-created.

In general, FME Engine logs are not used for testing and troubleshooting. However, you can view this log to see:

  • Which jobs were processed by a specific engine.
  • The FME command line that was run and the sub-section used to run the command. If a translation fails, you can run it from the FME Server Console using this command. The Console removes a layer of processing, which is good practice when debugging.
  • The parameters an Engine uses to process workspaces.

fmeprocessmonitorengine.log

This log shows:

  • The build number of the engines running the FME Server.
  • If an FME Engine fails to start and an error message indicating why, such as a licensing issue.
  • Any debugging information generated by a Python shutdown script.

Services Logs

Location:

<LogDir>\service\current|old\

This directory provides logs for each of the Web Services supported by FME Server.

Installation Logs

Location:

<FMEServerDir>\Logs\installation

These logs contain information about the installation of FME Server. It is only necessary to read them if you have had a problem installing FME Server.

CreateDatabase.log/CreateSchema.log/CreateUser.log

These logs contain information about initializing the FME Server Database.

Web Application Server Logs

Location:

<FMEServerDir>\Utilities\tomcat\logs

The Web Application Server is a third-party application used to run FME Server Web Services. The default application server is Apache Tomcat, but others can be configured. Application servers generally do their own logging and these logs can be helpful in troubleshooting problems with services.