How to determine time necessary to complete an sdconnect shutdown in RSA ACE/Server
Originally Published: 2004-04-22
Article Number
Applies To
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.
Issue
Veritas operation failed to complete due to extended time involved in terminating Progress database connections
Resolution
Related Articles
Web Server certificate verification failed with RSA Authentication Agent 8.0 for Web for Apache Number of Views Reboot the Appliance Number of Views RSA Authentication Manager 7.1 to 8.1 - Migrating to a New Hardware or Virtual Appliance Number of Views During an upgrade of RSA Identity Governance and Lifecycle from 6.9.0 to 6.9.1 the following error is seen: ORA-00904: "… Number of Views RSA Authentication Manager Web Tier installation fails with the following error: The directory already exists! Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes: Cloud Access Service and RSA Authenticators RSA Release Notes for RSA Authentication Manager 8.8 RSA-2026-04: RSA Governance and Lifecycle Security Update for SUSE Linux Enterprise Server Vulnerabilities
Don't see what you're looking for?
