Difference between revisions of "Ims-ms channel debugging and error logging"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (NedFreed moved page Ims-ms channel debugging to Ims-ms channel debugging and error logging: Page name change)
(No difference)

Revision as of 08:39, 20 February 2016


ims-mschannel debugging goes to two (or three) places, the channel-name_master.log-* file, and the imta file, which is an NSLOG file, and as of JES MS 6.2, if message tracing is enabled (if the messagetrace.activate option in Unified Configuration or the local.msgtrace.active configutil parameter in legacy configuration is set to yes), then message tracing will also be written to the msgtrace file.

MTA processing debugging, enabled for instance via the master_debug channel option, goes to an channel-name_master.log-* file.

ims-mschannel level processing goes to the imta file. In general, the level of detail recorded in the imta file is controlled by the mta.loglevel option in Unified Configuration or the configutil parameter logfile.imta.loglevel in legacy configuration; it can be set to any of the values critical, error, warning, notice, information, or debug. In order for the debug output generated due to a non-zero DEBUG ims-ms-channel-specific option setting (ims-ms.options.DEBUG in Unified Configuration, or DEBUG option in the in the ims-ms channel option file in legacy configuration) to in fact get included in the imta log file, mta.loglevel (Unified Configuration) or logfile.imta.loglevel (legacy configuration) must hence be set to debug.


See also: