How to prevent the OS from killing the SpectroSERVER process when the SpectroSERVER system is rebooted before gracefully shutting the SpectroSERVER processes
search cancel

How to prevent the OS from killing the SpectroSERVER process when the SpectroSERVER system is rebooted before gracefully shutting the SpectroSERVER processes

book

Article ID: 216636

calendar_today

Updated On:

Products

Spectrum

Issue/Introduction

During a system reboot, processd allows a limited window of time for the Spectrum processes to shut down gracefully before forcibly terminating them along with the reboot itself. By default, this timeout is set to 20 seconds on both Linux and Windows — which may not always be sufficient for the SpectroSERVER and Archive Manager processes to complete a clean shutdown.  Rebooting the SpectroSERVER system without first gracefully shutting down the SpectroSERVER and Archive Manager processes can result in database corruption.

This article explains how to increase that timeout value to help prevent database corruption during system reboots.

Environment

Release : Any

Component : Spectrum Core / SpectroSERVER

Resolution

Windows:

1. Open the Registry Editor

2. Go to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control

3. Click the Control key

4. Double-click the WaitToKillServiceTimeout value in the right pane

5. In the window, change the value to 600,000 milliseconds (10 minutes)

6. Click OK

7. Reboot the system for the change to take affect. Make sure to shutdown the SpectroSERVER and Archive Managers gracefully before rebooting because the settings are not applied yet. They will be applied after the first reboot.

 

Linux:

1. Log into or su to the root user

2. cd to the /opt/SPECTRUM directory

3. Make a backup of the spectrum80.env file

4. Edit the spectrum80.env file and add the following line:

PROCESSD_SHUTDOWN_TIMEOUT=60000

5. Save the change

6. Reboot the system for the change to take affect. Make sure to shutdown the SpectroSERVER and Archive Managers gracefully before rebooting because the settings are not applied yet. They will be applied after the first reboot.