Problem

Stopping the ST services out of order and force-stopping the embedded PostgreSQL database can result in data corruption or loss.

Resolution

Step 1: Stop ST Services on the Secondary node

• Open a terminal to the Secondary node

• Navigate to the ST bin directory: cd <FILEDRIVEHOME>/bin

• Run ./stop_all

Important: You will see a warning message:

WARNING: Database is currently in use and it will not be stopped. In order to stop the database forcefully execute "stop_db -f"

Do NOT run the stop_db -f command, as this may lead to data loss.

Step 2: Stop ST Services on the Primary node

• Open a terminal to the Primary node

• Navigate to the ST bin directory: cd <FILEDRIVEHOME>/bin

• Run ./stop_all

This time you will not receive a warning - the database on the Primary node will shut down cleanly, along with the ST services.

Step 3: Stop the Database on the Secondary node

• Return to the terminal for the Secondary node

• Run ./stop_db

The database will now stop without a warning, as the Primary node's services have been shut down. At this point, all ST services and the database are safely stopped on both nodes.