Domino server has crashed and the NSD file reports "nntask" within the faulting thread.
Moreover, the SMSDOM log shows a number of "unable to open container" scan errors before the time the server crashed.
The following lines (or similar) can be found in Symantec Mail Security for Domino (SMSDOM) debug log files (if debugging is enabled):
SMSDOM DEBUG [ Dec 10-5E5F-01:26:43 06/09/11 ] Create temprorary file for source file: [/savtmp/SMS3324880839.gif] SMSDOM DEBUG [ Scanner 01-5E5F-01:26:43 06/09/11 ] Unknown Exception caught while scanning the file. ... SMSDOM DEBUG [ nntask 02-5E5F-01:26:43 06/09/11 ] Scan of item ATT00004.gif failed with code 24 ... SMSDOM DEBUG [ nntask 02-5E5F-01:26:43 06/09/11 ] There were errors in scanning item: ATT00004.gif SMSDOM DEBUG [ nntask 05-5E5F-01:26:43 06/09/11 ] Opening item for scan: ATT00008.gif SMSDOM DEBUG [ nntask 05-5E5F-01:26:43 06/09/11 ] Unable to allocate memory in in-memory scanning
Other errors which can be found in SMSDOM debug log file:
SMSDOM DEBUG [ Scanner 01-7778-01:31:05 06/09/11 ] Unknown Exception caught while scanning the file.
SMSDOM DEBUG [ nntask 05-5556-01:03:55 06/09/11 ] Unable to allocate memory in in-memory scanning
In some cases, the available memory within the Domino system may no longer be enough for SMSDOM scanning activities, leading to the conditions for a crash.
This is due to the fact that the Domino server may sometimes use more system memory due to maintenance tasks, software upgrade.
A possible solution to excessive memory usage by SMSDOM (compared to a very low mail/writes load) is to change the number of SMSDOM scanning threads initialized at starting time.
For more information on how to do so, please refer to technote TECH146511, also referenced in the Related Articles section below.
- AIX 5.3 32-bit
- SMSDOM 8.0.8
- Domino 8.5.2
Imported Document Id