Node in VMware Identity Manager will not start Postgres.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

The /db/data directory is empty or has just a recovery.conf and serverlog files.

Environment

vIDM 3.3.7

Resolution

1. Stop the pgPool service starting with the nodes first and primary last:  

/etc/init.d/pgService stop

2. On the replica nodes remove any files under /db/data.  Do not remove any files on the primary node. 

rm -rf /db/data/*

3. This should trigger a pg_basebackup that will copy data from primary to the nodes.  Wait for about 5 minutes to check if /db/data is populated.

4. If there is no data skip to step 6 in running a pg_basebackup manually to copy data over to the node.  If data is populated you can start vpostgres on the replica nodes:  

/etc/init.d/vpostgres start

5. Start up pgpool starting with master and then the replica nodes:  

/etc/init.d/pgService start

6. Run a pg_basebackup to copy files to /db/data on the replica nodes:  

 /opt/vmware/vpostgres/current/bin/pg_basebackup -h master -D /db/data -U repl -P -Xs

7. This will prompt for a password.  You can find the password on the primary node in the /db/data/recovery.done file in the "password=" field.

8. Check the /db/data directory on the replica nodes after the pg_basebackup has completed.

9. Make sure the file recovery.conf exists, if not, copy the file recovery.done to recovery.conf:

cp /db/data/recovery.done /db/data/recovery.conf

10. Make sure all files in the /db/data directory are owned by postgres:users, if not, run:

chown -R postgres:users /db/data

11. Return to step 4 and 5 to start vpostgres and pgPool.