About Log Files inFME Flow

FME Flowcreates log files for everyworkspaceit 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 Flowis configured, by default, to delete old log files. You can manage automatic log file cleanup on theSystem Cleanuppage of theFME FlowWeb User Interface.

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

基于t日志文件分组在子目录heir function, in either acurrentorolddirectory. Log files are auto-archived from thecurrentto theolddirectory 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 applicablemessagelogger.propertiesfile. For more information, seeMessage Logger Properties.

FME Job Logs

Location:

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

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

FME job logs can also be accessed from theJobspage of the Web User Interface.

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

\<number>\job_<value>.log

Wherevalueis the job ID andnumberis 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目前核心> \ \ |旧\出版商

This directory provides logs for each of theNotification Servicepublisher protocolssupported byFME Flow. 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 theNotification Servicesubscriber protocolssupported byFME Flow. Each file logs activities of any subscribers configured on the respective protocol.

Task Logs

Location:

<LogDir>\core\current|old\tasks

FME FlowconfigurationBackup & Restoreandproject export/importoperations.

Other Core Logs

Location:

<LogDir>\core\current|old\

fmeserver.log

This log is frequently used in testing and troubleshooting, and is created each time theFME Flowis started. It shows:

• Authentication and authorization information, including connecting toAuthentication Services, if applicable.
• Connection parameters relating to theFME FlowDatabase.
• Messages created byJob Directivesand theRepository 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 abackup and restore.

fmedirectoryserver.log

Logs activity about connecting and authenticating with an LDAP server.

fmeprocessmonitorcore.log

Process monitor logs are frequently used in testing and troubleshooting. A new process monitor log is created each time theFME Flowis started. This log details theFME Flowcomponents 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 theSchedulercomponent, and everyworkspacerun by the Scheduler.

fmesharedresource.log

This log records activity that affects anyResourcesdirectories.

FME Engine Logs

Location:

\engine\current|old\

fmeprocessmonitorengine.log

This log shows:

• The build number of the engines running theFME Flow.
• 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 byFME Flow. Login activity through aSAMLidentity provider is also recorded here.

Installation Logs

Location:

<FMEFlowDir>\Logs\installation

These logs contain information about the installation ofFME Flow. It is only necessary to read them if you have had a problem installingFME Flow.

CreateDatabase.log/CreateSchema.log/CreateUser.log

These logs contain information about initializing theFME FlowDatabase.

Web Application Server Logs

Location:

\Utilities\tomcat\logs

The Web Application Server is a third-party application used to runFME FlowWeb 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.