31/03/2010

Hungry for Lotus Domino debug settings?


Amazing info you get sometime from unexpected sources ;-)

 I found a list of useful  debug settings for Domino from the the following IBM Redbooks:
 Implementing IBM Lotus Domino 7 for i5/OS

Take a look: (8.4 Additional troubleshooting parameters)

 Console_Log_Enabled=1 
This is Domino’s dynamic debug outfile for trapping error messages to a log file (other 
than the LOG.NSF). The console logging can be switched on and off with the start 
consolelog and stop consolelog commands.


 Console_Log_Max_kbytes=100000 
This parameter sets a size limit to the CONSOLE.LOG file. Setting the 
Console_Log_Max_kbytes to 100000 results in the CONSOLE.LOG file being limited to 
100 MB in size. On hitting that limit, it will wrap.


 Debug_Threadid=1 
Enabling this debug parameter provides more information about each entry posted to the 
Domino server console, including job number, process ID (PID), and thread number. This 
is extremely useful when combined with other utilities to determine the last activity by a 
thread prior to a crash, or what a particular thread was doing during a hang or slowdown 
situation.


 Log_View_Events=1 
This records to the console whenever views are rebuilt.
Following is a list of the hang debug parameters:


 Debug_Show_Timeout=1 
This parameter, combined with the Debug_Capture_Timeout=10 parameter, allows for the 
population of a file called SEMDEBUG.TXT, which exists in the 
IBM_TECHNICAL_SUPPORT subdirectory, and is vital to determine the root cause for 
server slowdowns or hangs.


 Debug_Capture_Timeout=10 
This parameter, combined with the Debug_Show_Timeout=1 parameter, allows for the 
population of a file called SEMDEBUG.TXT, which exists in the 
IBM_TECHNICAL_SUPPORT subdirectory, and is vital to determine the root cause for 
server slowdowns or hangs.
Following is a list of the Simple Mail Transfer Protocol (SMTP) debug parameters:


 SMTPDebug=4 
Enabling this debug parameter logs all the inbound SMTP protocol conversations to 
include commands and responses along with some of the text, but not the body of the 
messages.


 SMTPDebugIO=3 
This debug parameter is used to log all the data received by the SMTP listener task.
Attention: The debug parameters provided here must only be used if you are already 
familiar with them or if you have been advised to do so by Lotus Support. Also note that 
some additional levels of setting might be available for a given parameter.Chapter 8. Problem determination  351


 SMTPClientDebug=1 
This debug parameter is used to log all the outgoing SMTP protocol conversations for all 
the external messages transferred by the router task.


 SMTPDebugControls=3 
This assists in determining a variety of issues involving SMTP to include reverse DNS 
queries and blacklists.


 SMTPDebugDNSBL=1 
This assists in determining issues when utilizing the blacklists function.


 SMTPSaveImportErrors=3 
This provides the SMTP listener task to save all the inbound messages during import, and 
then delete all the messages that have successfully been received and written to mail.box. 
This leaves only the messages that fail to be imported in the mail.box. These messages 
are saved to a temp file for review.


 MIME_Save_Convert_Failures=1 
Enabling this setting results in the copying of messages that failed conversion, to a 
separate database called CFDB.NSF.
Following is a list of the mail routing debug parameters:


 Log_MailRouting=40 
This posts to the Domino console, all the transfer messages, message queues, and full 
document information involving mail.box.


 DebugRouter=3 
This debug parameter also increases the logging level for router activity.


 Debug_TCP_Resolver=1 
This debug parameter increases the logging of the TCP/IP name lookup function and 
assists in determining DNS issues.


 Debug_Directory_Assistance=1 
This provides for high-level logging of directory assistance activities.


 Debug_NameLookup=1 
This enhances the logging of the name lookup function.


 DebugRouterLookUp=3 
This displays how the router task resolves a name lookup.
Following is a list of the agent manager debug parameters:


 Debug_AMGR=* 
This increases all aspects of logging for the Agent Manager task.


 Log_AgentManager=1 
This specifies that the execution of partially and completely successful events are logged.
Following is a list of the update debug parameters:


 Log_Update=2 
Setting this debug parameter posts to the Domino console when the Indexer starts and 
stops and when the Indexer updates the views and full text indexes for specific databases. 
It also records the names of the views being updated.352  Implementing IBM Lotus Domino 7 for i5/OS


 Debug_NIF_Update=1 
Enabling this debug parameter provides for a report when an the Update task is started 
and stopped. This report includes the database name, the view name, and the user name 
of the update. Most importantly, if an error is encountered it prints out the error message 
during the rebuild or creation of the view involved.


 Debug_NIF=1 
This parameter prints out information concerning the opening, closing, and updating of 
significant indexing events and must be used rarely because of the excessive output.
Following is a list of the POP3 debug parameters:


 POP3Debug=4 
This serves the same purpose as the SMTPDebug parameter, except that it does so for 
the POP3 task.


 POP3DebugIO=3 
This serves the same purpose as the SMTPDebugIO parameter, except that it does so for 
the POP3 task.


 POP3ClientDebug=1 
This serves the same purpose as the SMTPClientDebug parameter, except that it logs the 
entire conversation for the POP3 task.
Following is a list of the LDAP debug parameters:


 LDAPDebug=7 
Increases whatever is reported by the LDAP task to assist in lookups, but will also have a 
potential performance impact on the LDAP server depending on usage.
Following is a list of the ADMINP debug parameters:


 Debug_ADMINP=1 
This debug parameter provides for the administration process to save its schedule 
information each time the schedule is updated.
Following is a list of the Network and connectivity debug parameters:


 Debug_TCP_All=1 
This provides low-level TCP/IP session information and must be used rarely because of 
the amount of logging and possible impact to Domino server performance.


 Debug_TCP_Errors=1 
This is similar to the Debug_TCP_All=1 parameter, in that, it provides low-level 
information about TCP-related errors that are encountered.


 Log_Connections=1 
When this debug parameter is set, the Domino server console displays the Notes network 
port, the network address of the requesting system, and the network address of the 
destination server.


 Log_Sessions=1 
Enabling this parameter posts each individual session to the Domino server console, and 
includes the user and the version of the Notes client being used.Chapter 8. Problem determination  353


 Debug_TCP_Session=1 
This enables debug information about when sessions are opened and closed to the 
Domino server console.
Following is a list of the full text index debug parameters:


 Debug_FTV_Search=1 
This displays information about full-text searches and statistics.


 Debug_FT_Stream=1 
This records every document that is full-text indexed by the Domino server.


 Debug_FTV_Index=1 
This displays debug information about the indexer when updating full-text indexes.
Following is a list of the replication debug parameters:


 Log_Replication=4 
This debug parameter specifies whether the start and the end of replication sessions are 
posted to the Domino server console. If using the value of 4, it reports replication all the 
way down to field-level replication. If set to 3, it records down to the note level, and if set to 
2, it reports activity at the database level.


 Debug_REPL_Time=1 
This parameter posts to the Domino server console the time a replication action took.


 Debug_REPL_All=2 
This parameter provides additional information about each document that is not 
replicating.
Following is a list of the HTTP debug parameters:


 HTTPAgentDebug=4 
This is used to help debug Java agents within HTTP.


 AgentThreadDebug=1 
This assists in determining which HTTP agent is being processed at the time of a server 
failure.


 HTTPEnableThreadDebug=1 
This generates htthr files detailing all the HTTP thread activity.


 HTTPLogFormatAscii=1
This allows the HTTP log files to be written in ASCII instead of Extended Binary Coded 
Decimal Interchange Code (EBCDIC).


 DebugShowJavaAgentTID=1 
This allows for determining which worker or control thread spawns which Java thread 
when executing a Java agent. It also prints out the agent name.
Following is a transaction logging debug parameter:


 Debug_RM_Debug=1 
This debug parameter reports high-level information about the actions that the recovery 
manager is taking against each database.354  Implementing IBM Lotus Domino 7 for i5/OS
Following is a memory overwrite debug parameter:


 Debug_Checkmarkers=1 
This debug parameter is used to help diagnose memory overwrites.
Following is a compact debug parameter:


 Debug_DBCompact=1 
This debug parameter provides additional high-level details about the compact task 
activity.
Following is a reports debug parameter:


 Debug_Reports=1 
This allows for additional logging of reports that are run from reports.nsf.
Following is a list of the memory-related debug parameters:


 Debug_Showleaks=2 
This enables memory usage tracking in conjunction with memory dump to help determine 
if a leak exists.


 Debug_TrapLeaks_ShowStack=1 
This assists in debugging potential memory leaks.


 NSD_RUN_MemCheck=1 
This provides for memory-related debug, and is described in 8.4.1, “MEMCHECK”.


No comments: