000025537 - How to determine time necessary to complete an sdconnect shutdown in RSA ACE/Server

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025537
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
RSA ACE/Server 5.1 (no longer supported as of 7-14-2006)
RSA ACE/Server 5.2
RSA Authentication Manager
Using Veritas control software to shut down applications and failover. Veritas configuration allows for configuration of a timeout or delay when waiting on a command to complete. In this particular case, it is the sdconnect shutdown for which Veritas is awaiting completion.
NOTE: An sdconnect shutdown executes "proshut -by"

PROGRESS SOLUTION, ID P3222 :

This is what happens when you do an unconditional batch Shtudown -by, proshut -by:

If there are any processes left after:

30 Secs. - wake up clients waiting for locks.
60 Secs. - wake up clients waiting for locks.
90 Secs. - wake up clients waiting on screen input.
5 Minutes - Resend the shutdown signal to remaining clients.
10 Minutes - Send a terminate (SIGTERM) signal to remaining clients.


NOTE: Changing the "proshut -by"  to "proshut -F" in the sdconnect script would not be recommended by RSA:

If you do an Emergency Shutdown with -by -F, then proshut:

- Sets the emergency shutdown flag in shared memory.
- Kills the broker (kill -9).
- Sends the shutdown signal to all connected processes and waits 10 seconds.
- Kills all remaining clients (kill -9).
- Removes shared memory, marks the database as crashed, and removes the dbname.lk file.
Progress performs normal crash recovery when you restart your database after the emergency shutdown and backs out any active transactions.
Note that the -F option in proshut is entirely different from the -F option in other modules. -F used with e.g truncate bi causes crash recovery to be skipped and this will cause damage to the database.
IssueHow to determine time necessary to complete an sdconnect shutdown in RSA ACE/Server
Veritas operation failed to complete due to extended time involved in terminating Progress database connections
ResolutionTo correct this issue, configure the delay or timeout in the Veritas configuration to be at least 11 minutes. This ensures the termination of client connections to the Progress database.
Legacy Article IDa21294

Attachments

    Outcomes