greenplum_path.sh doesn't appear to be setting GPHOME correctly in Red Hat Linux 9.6 (RHEL9)
search cancel

greenplum_path.sh doesn't appear to be setting GPHOME correctly in Red Hat Linux 9.6 (RHEL9)

book

Article ID: 412428

calendar_today

Updated On:

Products

VMware Tanzu Data Suite VMware Tanzu Greenplum VMware Tanzu Greenplum / Gemfire

Issue/Introduction

You installed GP (6.x or 7.x) cluster on Red Hat Linux 9.x (RHEL9)  OR  upgraded GP (6.x or 7.x) cluster to RHEL9.x.

gpstart is not able to start the cluster.

 

Environment

All Greenplum versions on Redhat Linux 9.x (RHEL9)

Cause

$GPHOME environment variable is incorrectly set to the greenplum-db-x.xx.x instead of complete path /usr/local/greenplum-db-x.xx.x

The problem is due to a change in the environment, the command flags used, or differences in how readlink is now expected to behave, especially with relative paths. 

Resolution

Workaround -

Replacing instances of readlink -f with realpath in greenplum_path.sh will fix the issue. 


if [ ! -L "${SCRIPT_DIR}" ]; then
    GPHOME=${SCRIPT_DIR}
else
    GPHOME=$(readlink "${SCRIPT_DIR}")
fi

Fix -

In progress.