When end user want to use non-gpadmin OS user to install gpcc, it will report error :
no pg_hba.conf entry for host "127.0.0.1"
gpcc 6.x , 7.x
Currently the gpccinstall script has a condition of gpadmin OS user. It means non-gpadmin OS user will report error when run gpccinstall.
As R&D team is considering add the support for non-gpadmin OS user in future release. Currently when install gpcc with non-gpadmin OS user, we can use below workaround:
Prerequisites (perform as a database superuser, typically matching your installing OS user)
Create gpperfmon database:
createdb gpperfmon
Create the gpmon role (skip if it already exists). Use a strong password; if the password contains single quotes, escape them appropriately in SQL.
CREATE ROLE gpmon WITH SUPERUSER CREATEDB LOGIN PASSWORD 'your_secure_password';
If gpmon already exists, set a known password instead:
ALTER ROLE gpmon PASSWORD 'your_secure_password';
Update pg_hba.conf on all Greenplum hosts (coordinator, standby, and every segment) so gpmon can connect. Example entries:
local gpperfmon gpmon md5
host all gpmon 127.0.0.1/32 md5
host all gpmon ::1/128 md5
host all gpmon samenet md5
Reload the configuration so pg_hba.conf is active:
gpstop -u
Add a ~/.pgpass entry for the user that runs gpccinstall (recommended format uses your real coordinator port, not necessarily 5432):
*:5432:gpperfmon:gpmon:your_secure_password
Then
chmod 600 ~/.pgpass
Now run
./gpccinstall