...
The active node should be restarted first. The passive node should detect this and take over the active role. Wait for the restarted node to enter the
PASSIVE-STANDBY state before proceeding. If it has a problem recovering state, it is likely due to corrupted data; check the server log for errors. In this case, it will not enter the STANDBY state, and manual intervention will be needed. First, try removing the terracotta server's "dirty" saved object data, e.g.:
| No Format |
|---|
# /etc/init.d/terracotta stop
# rm -rf /usr/local/shibboleth-idp/cluster/server/data/dirty-objectdb-backup/*
# /etc/init.d/terracotta start
|
If it still fails to recover to STANDBY state, stop the server again, and remove the object data, e.g.:
| No Format |
|---|
# /etc/init.d/terracotta stop
# rm -rf /usr/local/shibboleth-idp/cluster/server/data/objectdb/*
# /etc/init.d/terracotta start
|
Once this node reaches the PASSIVE-STANDBY state, you can proceed to restart the other node (newly active).
If both nodes are restarted at the same time, e.g. after a power failure, it is likely that manual intervention will be required, to clean up the data directories.