gpstop reports "fe_sendauth: no password supplied"

Products

• VMware Tanzu Greenplum

Issue/Introduction

gpstop (or possibly any other greenplum utility)

$ gpstop -a
20240305:11:28:19:017096 gpstop:mdw-lab1:gpadmin-[INFO]:-Starting gpstop with args: -a
20240305:11:28:19:017096 gpstop:mdw-lab1:gpadmin-[INFO]:-Gathering information and validating the environment...
20240305:11:28:19:017096 gpstop:mdw-lab1:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20240305:11:28:19:017096 gpstop:mdw-lab1:gpadmin-[INFO]:-Obtaining Segment details from master...
20240305:11:28:19:017096 gpstop:mdw-lab1:gpadmin-[CRITICAL]:-gpstop failed. (Reason='fe_sendauth: no password supplied
') exiting...

Environment

Product Version: 6.23

Resolution

The ${COORDINATOR_DATA_DIRECTORY}/pg_hba.conf file is not allowing the gpadmin user to log into the database without a password.
The gpadmin user needs to be a "trusted" user when logging in from the coordinator or standby coordinator host.

Modify the pg_hba.conf file and ensure the first lines in the file allow the gpadmin user to be trusted when logging from the coordinator host. Example:

local   all     gpadmin ident
host    all     gpadmin 127.0.0.1/28    trust
host    all     gpadmin <COORDINATOR IP ADDRESS>/32 trust
host    all     gpadmin <STANDBY COORDINATOR IP ADDRESS>/32 trust
local   replication     gpadmin ident
host    replication     gpadmin samehost        trust
host    replication     gpadmin <COORDINATOR IP ADDRESS>/32 trust

Then stop the master with pg_ctl command:

pg_ctl -D ${COORDINATOR_DATA_DIRECTORY} stop -m fast

Start the master in utility mode:

gpstart -ma

Then stop the complete database:

gpstop -af

It should now be possible to stop/start the database normally.