Common causes for Domino crashing/no NSD running

Hi everyone,

I recently started as our company’s Notes admin and am trying to determine why one of our servers is behaving less than ideally.

Over the past couple of weeks, I’ve noticed that I cannot access the server. When I log into the server through VNC, I see that the Domino window is not up and is no longer running as a service. When I start the service, it then begins performing consistency checks on the DBs.

I did not see the message that says something like “NSD is running. File will be created in *** of this event”.

I am trying to determine some common causes of why this may be happening.

Here the the server specs, and what is installed on it:

  • Dell PowerEdge 4600 Dual 2.2GHz Xeon processors

  • 3.5GB RAM

  • ~300GB hard drive space in RAID 5 array

  • Windows 2000 Server SP3

  • Domino 6.5.4 FP2, hosting about 180 mail files. Sizes range from 50MB to 6.2GB

  • Symantec Mail Security 4.0 for Domino

  • VERITAS Backup Exec Remote Agent for Windows Servers

Is there a list of common causes I can go through to determine what may be causing this? In addition, do any of you know if the extra apps we have installed may be causing server instability?

I am more than happy to provide additional information for you.

Thanks.

Subject: Common causes for Domino crashing/no NSD running

The nsd file is the basic to understand why the domino server crashes, look at the dir IBM_TECHNICAL_SUPPORT under the domino data directory, by default the nsd file is created there. Open the nsd and look for the callstack with the FATAL string, you can paste that fatal callstack here to have some help.

Subject: Common causes for Domino crashing/no NSD running

We had similar problems. I found that my http threads were too high. Changed the (server Document) | InterNet Protocols | Basics tab | Number ActiveThreads from 256 to 128.

This setting in the server document should prevent the Domino service from crashing every couple of weeks. “show stat domino.threads.active.peak” command shows the max # of threads used.

You can also run from a command window “nsd -monitor” if an nsd file is not created. You may want to increase your buffer size in the cmd window. Next time the server fails, select all and paste into wordpad.