Knowledgebase

Server Shutdown Hangs or Takes Excessive Time

The FairCom DB shutdown process may take a long time for the following reasons:

• The server must write all updated data and index cache pages to disk before shutdown completes. If the server is configured to use a large cache, there can be many updated cache pages that must be written to disk at shutdown, which increases the shutdown time.
• The server processes entries in the delete node queue at shutdown. The presence of many entries in the delete node queue can lead to increased server shutdown time.
• The server allows clients time to recognize that the server is shutting down and to disconnect from the server. The shutdown time can be long if many clients are connected or if the server is not able to terminate connected clients.

In This Section Monitoring FairCom DB Shutdown Progress Forcibly Terminating FairCom DB During Shutdown

Monitoring FairCom DB Shutdown Progress

The progress of FairCom DB shutdown can be monitored in the following ways:

• Monitoring messages FairCom DB writes to the server status log during shutdown.
• Monitoring messages FairCom DB writes to its console or standard output during shut
• Monitoring system resource usage by FairCom DB during shutdown.

FairCom DB shutdown is normally accompanied by messages in the server status log such as the following:

- User# 13 Process delete node Q....

- User# 13 Clients still active.....

- User# 13 Clients shutting down....

These messages indicate the current operation FairCom DB is performing, such as processing delete node queue entries, terminating connected clients, and allowing clients time to shut down.

The server also writes shutdown messages to its console window or standard output. These messages provide more detailed information than the status log entries, including the remaining number of delete node queue entries, and the current number of active client threads:

Process delete node Q.......<num_queue> entries.

Clients still active........<num_active>

Clients shutting down.......<num_active>

where <num_queue> is the current number of entries in the delete node queue and <num_active> is the current number of client threads that are still active.

System utilities can also provide insight into FairCom DB’s progress during shutdown. Monitor disk activity on the FairCom DB data and index files to determine if the server is taking a long time to shut down because it is flushing data and index cache buffers. Monitor the number of active server threads to determine how many client threads are still active. See the “Monitoring FairCom DB Process State” section of this document for additional ways to monitor the state of theFairCom DB process.

Forcibly Terminating FairCom DB During Shutdown

If FairCom DB is taking a long time to shut down or if the server appears to hang during shutdown, the server process can be terminated using system utilities but be aware of the effect on FairCom DB data and index files. Forcibly terminating a FairCom DB process at shutdown effectively causes an abnormal server termination, which means that unwritten updates for PREIMG and non-transaction files may be lost and that the server will perform automatic recovery on its next startup in order to ensure TRNLOG files are in a consistent transaction state. For details on the state of FairCom DB data and index files in the event of an abnormal server termination, see the topic “Server Terminates Abnormally” in the “Failures During FairCom DB Operation” section of this document.