gpupgrade : Greenplum 6.x is failing to start when upgrading from Greenplum 5.x
search cancel

gpupgrade : Greenplum 6.x is failing to start when upgrading from Greenplum 5.x

book

Article ID: 296572

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

Using gpupgrade to upgrade from Greenplum 5.x to Greenplum 6.x and running the "upgrade initialize" command, the new Greenplum 6.x cluster is failing to start:
20220611:10:04:57:169367 gpstart:mdw:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait...
20220611:10:04:57:169367 gpstart:mdw:gpadmin-[INFO]:-Process results...
20220611:10:04:57:169367 gpstart:mdw:gpadmin-[CRITICAL]:-gpstart failed. (Reason='') exiting...
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:-Failed to start Greenplum instance; review gpstart output to
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:- determine why gpstart failed and reinitialize cluster after resolving
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:- issues. Not all initialization tasks have completed so the cluster
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:- should not be used.
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:-gpinitsystem will now try to stop the cluster
20220611:10:04:57:152140 gpinitsystem:mdw:gpadmin-[WARN]:
20220611:10:04:57:169444 gpstop:mdw:gpadmin-[INFO]:-Starting gpstop with args: -a -l /home/gpadmin/gpAdminLogs -i -d /data/master/gpseg.VQ3XlU2yHNk.-1
20220611:10:04:57:169444 gpstop:mdw:gpadmin-[INFO]:-Gathering information and validating the environment...
20220611:10:04:57:169444 gpstop:mdw:gpadmin-[ERROR]:-gpstop error: postmaster.pid file does not exist. is Greenplum instance already stopped?
20220611:10:04:58:152140 gpinitsystem:mdw:gpadmin-[WARN]:-Failed to stop new Greenplum instance Script Exiting!
INIT_TARGET_CLUSTER took 57s


Environment

Product Version: 5.28

Resolution

Ensure the Greenplum 5.x environment is not sourced when logging into any of the segment servers.
Check the ~gpadmin/.bashrc and ~gpadmin/.bash_profile on the segment servers for lines like:

source /usr/local/greenplum-db-5.28.0/greenplum_path.sh

If the environment is being sourced on login, then remove or comment out the linr in the file