Ims-ms channel debugging and error logging

Channel debugging output for the  channel goes to two (or three) places, the    file, and the    file, which is an NSLOG file, and as of MS 6.2, if message tracing is enabled (if the    option  in Unified Configuration or  the   configutil parameter in  legacy configuration is set to  ), then message tracing  will also be written to the   file.

MTA processing debugging, including but not limited to the generation of nondelivery notifications, enabled for instance via the   channel option, goes to a    file. (Note that setting  also forces the debug level controlled by   to at least 4, and as of MS 8.0.2, forces the   option setting to "debug".)

All  channel level processing goes to the   file. In general, the level of detail recorded in the   file is  controlled by the   option in Unified  Configuration or the   parameter    in legacy configuration; it can be  set to any of the values ,  ,   ,  ,  , or.

In order for the debug output generated due to a non-zero     -channel-specific option setting  (  in Unified Configuration, or   option in the in the   channel option file in legacy configuration) to in fact get  included in the   log file,    (Unified Configuration) or   (legacy  configuration) must hence be set to.

As of 8.0.1.2 the  option value defaults to 2. In earlier 8.0 versions the value is forced to 10 and the option setting is ignored. In 7.0.5 and earlier the default is 0, so either the channel-specific option or the  channel option must be set in addition to   for debug output to appear.

A number of conditions can cause the ims-ms channel to fail to initialize. When this happens a critical error is sent to the   file  and the process exits with a nonzero status. Possible initialization failures include, but are not limited to:



 PMDF_CHANNEL environment variable not defined 

 The  environment variable is used by the job controller to communicate the channel whose messages are to be processed. This error indicates that the variable is not set. This is usually an indication that the program has been run manually. 

 Failed to initialize the MTA 

 The MTA failed to initialized. This is usually the result of a configuration error of some sort 

 ims_master requires store.enable = 1 

 Self-explanatory. 

 ims_master requires store.dbtype = "bdb" 

 Self-explanatory. </dd>

 inetu_uginit failed </dt>

 The process was unable to initialize the LDAP client subsystem. </dd>

 Failed to initialize the store API </dt>

 The store failed to initialize. Additional errors may be logged providing more specific information </dd>

</dl>

See also:
 * activate Option
 * master_debug Option
 * DEBUG ims-ms-channel-specific option
 * loglevel Option
 * activate Option
 * ims-ms channels