gprecoverseg Incremental Recovery Fails, pg_rewind logs report "parsed dbid (-10000) is out of valid range"

Products

• VMware Tanzu Greenplum

Issue/Introduction

Incremental run of gprecoverseg fails, and the error below appears in the pg_rewind logs:

parsed dbid (-10000) is out of valid range: [1, INT16_MAX]Failure, exiting

Environment

Product Version: 6.21

Resolution

This occurs when the failed segment has an empty postgresql.conf file.

Alternate version can be copied over from another segment, modifying the values below to match the failed segment values in gp_segment_configuration:

port=<failed segment "port" value in gp_segment_configuration>
gp_contentid=<failed segment "content" value in gp_segment_configuration>