Lotus Domino Administrator 8.5 Help - How to troubleshoot server crashes

TROUBLESHOOTING

How to troubleshoot server crashes
The most common causes of server crashes are the following:

Low or depleted system resources
High server workload
Software problems
Network problems
Changes to network or operating system environments
Changes in hardware configuration -- for example, upgraded NICs -- or software configuration

Use these steps to troubleshoot a server crash. If, after completing these steps, you haven't resolved the problem, consult your technical support representative.

1. Collect system information:

Domino server version
Operating system version
Network type and version; network protocol(s) and version(s) (including file dates)
System level patches
Server hardware
Names of API programs and tasks, gateways, backup programs, executable scripts, third-party programs, and so on.

2. Note any changes to these elements of the Domino environment. If possible, revert to the previous configuration to determine if the problem still occurs.

Operating system changes -- for example, did you upgrade the operating system or apply a new patch?
Network changes -- for example, did you add a new router or upgrade the network software or firmware?
Network interface card (NIC) changes -- for example, is the NIC new, or is the NIC software driver old and the operating system new?
Domino changes -- for example, did you upgrade to a new release of Domino or migrate new users?
Other hardware or software changes.

3. If the last message on the console starts with the word "Panic," record the entire message.

4. If possible, capture the last screen displayed on the console or save the Console Log file.

5. Stop all tasks running on the Domino server, and then stop the Domino server.

6. If an NSD log file was created, verify the time and date of the file, which should coincide with the time and date of the crash. If necessary, Lotus Support Services will use this file to identify where the crash occurred.

Note

If a crash doesn't produce an NSD log file, the server may be out of disk space or memory.

7. Restart the server.

8. Check the Miscellaneous Events view in the log. Record all entries that occurred immediately before and after the crash. To do this, double-click the appropriate entry to open it. In particular, look for an NSF file in the entry, which may indicate where the crash occurred. If a particular database appears to have caused the crash, check the replication history of that database for additional information.

9. Collect these configuration files:

NOTES.INI -- All platforms
Microsoft® Windows® diagnostics file

Related topics

Server crashes -- Troubleshooting

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary