Page Comparison

Log file management

The Domino log file may be monitored in VitalSigns for the occurrence of certain words or phrases. While there are multiple error messages that the log file may produce, experience shows the following to be the most popular. Within VitalSigns configure log file monitoring documents related to these messages:

1. When the Domino server encounters corruption in a DAOS enabled database, an error similar to the following will be reported:

The database <data\mail\mailfilename.nsf> has the incorrect DAOS object count, you should run fixup on this database. Using this database in this condition will cause the DAOS catalog to go into the 'Needs Resync' state

2. When the DAOS catalog cannot be resynchronized the following will be seen in the log file:

DAOS deletions will be postponed

3. If DAOS enablement fails on excessively large databases, the following will be reported:

Memory allocation request exceeded 65,000 bytes

4. If a DAOS enabled database goes over the defined quota, the following will be written to the log:

DAOS error decrementing reference count for shared object

5. In the event a NLO file cannot be found, the following will be seen in the log:

The database C:\IBM\Domino\data\mail\mailfilename.nsf attempted to access a missing file d:\daos\xxx.nlo

That database C:\IBM\Domino\data\mail\mailfilename.nsf was unable to open or read the file d:\daos\xxx.nlo: Entry not found in index

6. The following error messages are reported for problems regarding the DAOS catalog:

RPR Wyatt - A Microsoft & IBM Advanced Business Partner http://www.rprwyatt.com http://www.rprvitalsigns.com

Informational - The DAOS catalog is not synchronized. Deletions will be postponed. Please run 'tell daosmgr resync' at the next convenient opportunity to resynchronize.

The DAOS catalog cannot be updated. Entry not found in index

7. When performing Domino mail file archiving with the DAOS flag enabled, the following archive error may appear:

Error archiving documents from mail\mailfilename.nsf: Informational, DAOS is already enabled in database

8. If the criteria for attachments is not properly configured, the following error will be reported:

Warning: DAOS object minimum participation size = 0, which is below the minimum recommended value of 64000

9. If the transaction logs cause the respective disk drive to run out of space the following error will be found in the log file:

Recovery Manager: Log File is full

DAOS Server Task monitoring

If The DAOS Manager is not running or is in a hung state, the DAOS process will fail to properly function. Use VitalSigns to create a server task monitor to ensure DAOSMgr is optimal.

DAOS Statistics Monitoring

Natively, Domino creates statistics regarding DAOS’ health. Create statistics monitors in VitalSigns to report if any of the following conditions are met.

DAOS.Engine.Status = Disabled

DAOS.Engine.Catalog = Unavailable

DAOS.Engine.Catalog = Needs Resync RPR Wyatt - A Microsoft & IBM Advanced Business Partner http://www.rprwyatt.com http://www.rprvitalsigns.com

DAOS Database monitoring

While the DAOS Catalog database cannot be read, its availability is vital to the functionality of DAOS. DAOS Database. Create a Database Monitoring document in VitalSigns to ensure the existence of the DAOSCAT.NSF. To scan the servers log.nsf and search for DAOS related keywords:

• Go to Servers & Devices -> IBM Domino -> Log File Scanning
• Click the New (Image Added)  button
• Enter a name for the Event Definition
• Enter a keyword to search for in the log file
• Enter a keyword to exclude in the search of the log file (optional)
• Select the checkbox next to Scan log.nsf
• You can also select to scan the agentlog.nsf and/or limit the keywords to one alert per day (optional)
• Click the Update (Image Added) button to save the changes
• Select the server(s) where you want to search the log file for the specified keyword

• Click OK to save the changes