Configure logging on Linux

Log messages are categorized into four "channels" containing information that may be of interest in different situations. You can enable or disable these logs to keep the size of the log manageable.

Logging Channel	Environment Variable	Purpose	Enabled by default
Operational	MFSYN_LOG_CHANNEL_OPERATIONAL	Start/stop of Job Manager daemon and other user-level events	Yes
Analytics	MFSYN_LOG_CHANNEL_ANALYTICS	Client connections and job information	No
Licensing	MFSYN_LOG_CHANNEL_LICENSING	Licensing checkin/checkout and errors	No
Debug	MFSYN_LOG_CHANNEL_DEBUG	Low-level events for troubleshooting job problems	No

To change the enabled status of a channel, run the /opt/Autodesk/moldflow/ami2016/sbin/reconfigure script to set the new value, then restart the Job Manager.

# /opt/Autodesk/moldflow/ami2016/sbin/reconfigure MFSYN_LOG_CHANNEL_LICENSING=yes
# /etc/init.d/ami2016jm restart

Tip: Within each channel, each log message has an associated severity. Most syslog implementations can control which messages are logged, and which are discarded, according to their severity. Look for a file syslog.conf or rsyslog.conf or syslog-ng.conf on your system.

Log messages are sent to the USER logging facility by default. If you wish to use another facility (SYSLOG or DAEMON or LOCAL0 through LOCAL7 are supported) you can set this with the MFSYN_LOG_FACILITY variable. Restart the Job Manager after you change the facility.

# /opt/Autodesk/moldflow/ami2016/sbin/reconfigure MFSYN_LOG_FACILITY=LOCAL4
# /etc/init.d/ami2016jm restart