Connection to the server fails or hangs forever. Servers are in PRIMARY ACTIVE, and SECONDARY ACTIVE state, but clients cannot connect to the servers to execute transactions.

Regardless of the state of unresponsive server, HAC executes a script as configured in the solidhac.ini configuration file with the LocalDB.UnresponsiveActionScript parameter. The script is started with single parameter including the process id (pid) of unresponsive solidDB process.

The typical solution is to terminate the process that is identified by the process id. In such a case, the recovery proceeds automatically depending on the role of the unresponsive server.

If the unresponsive server the primary server, see Primary server (or computer) fails.

If the unresponsive server was the secondary server, see Secondary server (or node) fails.