Download the Software

Obtain the Greenplum Command Center package from the official Pivotal or Broadcom download portal. Use the search bar to locate the correct version. Select the appropriate release and download the archive (requires a registered account).

Upload the downloaded archive to the /opt directory on the master node.

Installation Steps

Perform the installation as the root user on the master node.

# Extract the archive
[root@mdw opt]# unzip greenplum-cc-web-6.7.1-gp6-rhel7-x86_64.zip
Archive:  greenplum-cc-web-6.7.1-gp6-rhel7-x86_64.zip
   creating: greenplum-cc-web-6.7.1-gp6-rhel7-x86_64/
  inflating: greenplum-cc-web-6.7.1-gp6-rhel7-x86_64/gpccinstall-6.0.0
[root@mdw opt]# ls
greenplum-cc-web-6.7.1-gp6-rhel7-x86_64  greenplum-cc-web-6.7.1-gp6-rhel7-x86_64.zip  rh

# Change ownership to gpadmin
[root@mdw opt]# chown -R gpadmin:gpadmin /opt/greenplum-cc-web-6.7.1-gp6-rhel7-x86_64

# Switch to gpadmin and run the installer
[root@mdw greenplum-cc-web-6.7.1-gp6-rhel7-x86_64]# su - gpadmin
[gpadmin@mdw ~]$ cd /opt/greenplum-cc-web-6.7.1-gp6-rhel7-x86_64/
[gpadmin@mdw greenplum-cc-web-6.7.1-gp6-rhel7-x86_64]$ ./gpccinstall-6.0.0

The installer will prompt for several options. Provide the following answers:

• Accept the EULA: y
• Installation path: /greenplum
• Installation name: (default: gpcc)
• Webserver port: (default: 28080)
• Enable SSL: n
• Display language: 2 (Chinese)

After successful installation, you will see a confirmation message and the list of available gpcc commands.

Configure Environment Variables

Add the GPCC path source to the gpadmin user's bash profile and distribute it to all nodes.

# Append source line to .bash_profile
cat >> /home/gpadmin/.bash_profile << EOF
source /greenplum/greenplum-cc-web-6.0.0/gpcc_path.sh
EOF

# Reload the profile
source /home/gpadmin/.bash_profile

# Create a file listing standby and segment hosts (no extra spaces or blank lines)
vi /tmp/standby_seg_hosts
# Contents:
smdw
sdw1
sdw2

# Distribute the profile to those hosts
gpscp -f /tmp/standby_seg_hosts ~/.bash_profile =:~

Modify Database Configuration

Edit the master’s pg_hba.conf to allow the monitoring user access.

# Edit /data/master/gpseg-1/pg_hba.conf
# Add this line (anywhere before the end of file)
host    gpperfmon gpmon 0.0.0.0/0 md5

# Distribute pg_hba.conf to standby master if required (example uses scp)
scp pg_hba.conf gpadmin@192.168.0.113:/data/master/gpseg-1

Edit the master postgresql.conf to enable the performance monitoring extension.

cd /data/master/gpseg-1
vi postgresql.conf

# Add these parameters
gp_enable_gpperfmon=on
gpperfmon_port=8888
gp_external_enable_exec=on
gpperfmon_log_alert_level=warning

# Distribute the config to standby and all segments
gpscp -f /tmp/standby_seg_hosts /data/master/gpseg-1/postgresql.conf =/data/master/gpseg-1/postgresql.conf

Start the Command Center

As the gpadmin user on the master, reload the database configuration and start GPCC.

# Reload pg_hba.conf and postgresql.conf
gpstop -u

# Start GPCC agents and webserver
gpcc start
# Expected output:
# 2022-07-03 03:29:10 Agent successfully started on 4/4 hosts
# 2022-07-03 03:29:10 View Greenplum Command Center at http://mdw:28080

Access the web UI by replacing mdw with the master’s IP address. Example: http://192.168.0.110:28080

Set the gpmon Password and Credential File

Connect to the database and update the gpmon user password.

psql
ALTER USER gpmon WITH PASSWORD 'gpmon';
\q

Create or update the .pgpass file with the correct credentials.

# Format: hostname:port:database:username:password
# Edit /home/gpadmin/.pgpass
*:5432:gpperfmon:gpmon:gpmon

# Distribute to all segment hosts
gpscp -f /tmp/hostlist /home/gpadmin/.pgpass =~

Login to the web interface with username gpmon and password gpmon.

Troubleshooting: Password Authentication Failure

If you encounter the error password authentication failed for user "gpmon" when running gpcc stop or gpcc start, manually edit the .pgpass file as described above. After correcting the file, stop and start GPCC again:

gpcc stop
gpcc start

Verify the user exists and its password hash is stored correctly by querying pg_authid.

SELECT rolname, rolpassword FROM pg_authid WHERE rolname = 'gpmon';

The installation is complete once the web UI is accessible and all agents report success.