Pivotal Knowledge Base

Follow

Pivotal Greenplum Command Center - frequently faced problems

Environment

Product Version
Pivotal Greenplum (GPDB) 4.3.x
Pivotal Greenplum Command Center (GPCC) 1.x

Summary

After the installation of Greenplum Command Center following problems have seen to resurface frequently -

1. gpcmdr --start fails. Please see sample error message below.

2015-11-10 14:04:49,545 - Error calling execute_query from getgpdbversion: 'Connection error for query: select version();'
2015-11-10 14:04:49,545 - Error from getapi WS: "Database error while fetching GDDB version info 'Connection error for query: select version();'"
2015-11-10 14:04:49,545 - Unknown exception in call to api web service: Exception encountered while fetching api strings "Database error while fetching GDDB version info 'Connection error for query: select version();'"
2015-11-10 14:05:04,709 - error connecting to GPDB: FATAL: password authentication failed for user "gpadmin" for query: select version();
2015-11-10 14:05:04,709 - dbname=gpperfmon, host=mdw, port=5432, user=
2015-11-10 14:05:04,709 - Error calling execute_query from getgpdbversion: 'Connection error for query: select version();'
2015-11-10 14:05:04,709 - Error from getapi WS: "Database error while fetching GDDB version info 'Connection error for query: select version();'"
2015-11-10 14:05:04,709 - Unknown exception in call to api web service: Exception encountered while fetching api strings "Database error while fetching GDDB version info 'Connection error for query: select version();'"

2. Greenplum Database is up and running, but the Greenplum Command Center (GPCC) user interface displays a message that the database is down.

Checklist

While facing any of the above two scenarios, ensure to check the following:

  • The .pgpass file needs to exist in the gpadmin home directory with the connection information for gpmon user, including password, to connect to  gpperfmon database. If gpcmdr can't access that file for the connection information, it throws the password authentication error. This file also has to be owned by gpadmin with 600 permissions on it. 
  • By default gpadmin does not have a password and therefore no external connections can authenticate when the client authentication requires the client to supply an MD5-encrypted password for authentication. Please ensure password for gpadmin is set into the database. 
  • Understand the network setup, in case Greenplum master is on remote host please ensure you can connect directly to the Command Center database (gpperfmon) using any Greenplum Database-compatible client program (such as psql). For example:
         psql -d gpperfmon -h master_host -p 5432 -U gpmon
  • Ensure that gpmon is a valid and a non-expired user. This can be done by querying pg_roles.
         select rolvaliduntil from pg_roles where rolname='gpmon'

         If the output returned by above query is date from the past, reset rolvaliduntil to a future date with alter role to overcome this scenario.

  • Some users have their own implementation of ssh command that suits their environment with their own code wrappers written around it. GPCC by default uses system provided ssh binary but since ssh on user's cluster only works when using their customized implementation, GPCC fails. To overcome this problem use --ssh_full_path while setting up GPCC, set the full path to override the system's implementation of ssh.

Additional Reference

Read more on gpcmdr and GPCC.

Comments

Powered by Zendesk