HCLSoftware Business Partner
Domino Consulting Services
CRUCIAL Notes Tools
+1 212-599-2048

Domino Consulting Services
CRUCIAL Notes Tools
Domino administration
Notes development

Facebook Twitter YouTube
Chat now       
.
ProductsDownloadsNewsAbout usContact


Need a Domino Consultant? Call NotesMail +1 212-599-2048 - HCLSoftware Business Partner

ADMINISTERING

Setting up automatic diagnostic data collection on the server

Use the Server Configuration document to set up automatic diagnostic data collection on the server. You can also enable or disable Fault Analyses from this same tab in the Server Configuration Settings document.

Procedure

1. From the Domino® Administrator, click the Configuration tab.

2. Click Server -> Configurations.

3. Select the Server Configuration document you want to edit and click Edit Configuration.

4. Click the Diagnostics tab and complete these fields.


    Table 1. Diagnostics tab
    FieldAction
    Mail-in Database for diagnostic reportsSelect the mail-in database to which you want the diagnostic report for server crashes mailed. Click OK.
    Maximum size of diagnostic message including attachments (in MB)Enter the maximum size of the entire message that automatic diagnostic data collection will create, including all attachments -- NSD, console output, user defined files, and so forth.
    Maximum size of NSD output to attach (in MB)Enter the maximum size of the Notes® System Diagnostics (NSD) log that can be attached to the document created by automatic diagnostic data collection. (Automatic diagnostic data collection collects data and then creates documents in a mail-in database.)
    Maximum amount of console output file to attach in (KB)Use the default value of 10240 (10MB), or enter another value between 1 and 10240. 10240 is the maximum value. This value represents the portion of the CONSOLE.LOG file to be sent, beginning with the end of the file and moving toward the beginning.
    Diagnostic file patternsEnter a file name pattern that Domino will search for. If the pattern is located and it is listed in the file DIAGINDEX.NBF, the file will be attached to the message that is sent to the mail-in database. DIAGINDEX.NBF contains all the files associated with the crashing instance of the client or server. For example, the following is a file pattern: addin_log*.txt. These files would be located based on that pattern:

      addin_log1.txt

    ,

      addin_log_2004_11_23@16_21_20.txt
    Remove diagnostic files after a specified number of daysChoose one of these:
    • No -- (Default) Choose No to accept the default of never automatically deleting the diagnostic files created on the server.
    • Yes -- Choose Yes to enter the number of days after which the diagnostic files on the server are to be deleted. Displays the field Number of days to keep diagnostic files.
    Number of days to keep diagnostic filesAccept the default value of 365 days, or enter another value representing the number of days after which the diagnostic files are to be deleted from the server. (This field displays only if you selected Yes for Remove diagnostic files after a specified number of days.)

5. Save and close the document.

Related concepts
Collecting diagnostic information after a server or client crash

Related tasks
Setting up automatic diagnostic data collection on clients