When attempting to install Greenplum Command Center (GPCC) with an internal deployment (gpcc_external set to false or left empty), the following error is encountered:
config 'gpcc_host' must be of coordinator or standby when 'gpcc_external=<false/empty>'All versions of Greenplum Command Center
Internal (non-external) GPCC deployment
Greenplum Database cluster with a defined coordinator and optional standby
The error typically occurs when the hostname specified in the GPCC configuration (app.conf) does not resolve to the coordinator or standby host. Possible causes include:
Mismatched hostnames between app.conf, /etc/hostname, and /etc/hosts
Hostname resolving to an external or non-cluster IP address
Misconfigured DNS or host resolution
Inconsistent entries in the gp_segment_configuration table
gpcc_host value in app.conf is set to the coordinator or standby hostname.Check Hostname Consistency
Confirm the hostname listed in:
/etc/hostname
/etc/hosts
app.conf
All should match and refer to the same node that serves as the coordinator or standby.
Validate Hostname Resolution
Run:
or
and confirm that the IP address resolves internally to the cluster's coordinator or standby node.
Check gp_segment_configuration
Ensure the hostname and address fields in gp_segment_configuration include the coordinator and/or standby, and match the value used in gpcc_host.
/etc/hostname traditionally only includes a machine (or short) name. For example:
'gp1'
Instead of:
'gp1.organization.com'