DBService Failed to Start Due to the Loss of the DBService Configuration File

Symptom

The nodes are powered off unexpectedly, and the standby DBService node fails to be restarted.

Cause Analysis

1. The /var/log/Bigdata/dbservice/DB/gaussdb.log file is viewed, which contains no information.
2. The /var/log/Bigdata/dbservice/scriptlog/preStartDBService.log file is viewed. This file contains the following information, indicating that the configuration information is lost:

   The program "gaussdb" was found by "
   /opt/Bigdata/MRS_xxx/install/dbservice/gaussdb/bin/gs_guc)
   But not was not the same version as gs_guc.
   Check your installation.

   

3. The configuration file in the /srv/BigData/dbdata_service/data directory on the active DBServer node is compared with the configuration file in the /srv/BigData/dbdata_service/data directory on the standby DBServer node, which shows major difference.

   

   

Solution

1. Copy the content in the /srv/BigData/dbdata_service/data directory on the active node to the standby node and ensure that the file permission and owner group are the same as those on the active node.
2. Modify configuration in postgresql.conf. Set localhost to the IP of the local node and remotehost to the IP of the peer node.

   

3. Log in to Manager and restart the standby DBServer node.