Debug logging can be enabled for the mc Jobserver and/or adapters, and is useful for fme Product Support to track down errors customers may run into during their projects.
Debug logging should only be enabled when fme Product Support asks the customer to do so in order to generate a set of log files containing debug information, after which logging should be reset to the default (ERROR) level.
It is not recommended to enable debug logging permanently, as large amounts of information will be generated in the log files which are generally not useful to end-users working with migration-center, and would complicate parsing of the log files for meaningful messages for the end-user.
NOTE: logging configuration has been simplified starting with mc 3.2.4 Update 2 and as a result differs from previous versions of mc. Please follow the below steps when instructed to enable debug logging in mc 3.2.4 Update 2 or higher.
- Stop the Jobserver (let any running jobs finish first, or stop them from the Jobs window in mc Client)
- Backup/move/rename your existing logs folder (which may or may not be in the Server Components installation folder, depending on the log file location set during installation of the mc Server Components)
- Go to your mc Server Components installation folder, and open the file log4j.properties in the folder lib/mc-server or lib/mc-core (for MC version 3.13 and later) with a text editor (back the file up first if you want to)
- locate the following entries at the beginning of the log4j.properties file
- stop the Jobserver
- revert the changes done to the log4j.properties configuration file in steps 3-6
- delete/move/rename the newly created logs folder containing the debug logs
- restore your original logs folder backed up in step 2
- restart the Jobserver and continue using mc normally.