gpstart fails with error "could not access file "metrics_collector": No such file or directory" after upgrade
search cancel

gpstart fails with error "could not access file "metrics_collector": No such file or directory" after upgrade

book

Article ID: 296645

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

You have upgraded from Greenplum 6.11.2 to Greenplum 6.13.0. After upgrading, Greenplum is unable to start and in the MASTER_DATA_DIRECTORY/startup.log, you see the following error:
2021-01-13 12:02:32.161155 CET,,,p28227,th-1133602688,,,,0,,,seg-1,,,,,"FATAL","58P01","could not access file ""metrics_collector"": No such file or directory",,,,,,,,"internal_load_library","dfmgr.
c",202,1    0xbf0dac postgres errstart (elog.c:557)
2    0xbf5d9d postgres <symbol not found> (dfmgr.c:199)
3    0xbf6784 postgres load_file (dfmgr.c:156)
4    0xc09be4 postgres process_shared_preload_libraries (miscinit.c:1378)
5    0xa109b3 postgres PostmasterMain (postmaster.c:1151)
6    0x6b5f21 postgres main (main.c:205)
7    0x7f42b92c5555 libc.so.6 __libc_start_main + 0xf5
8    0x6c1c7c postgres <symbol not found> + 0x6c1c7c


Environment

Product Version: 6.12

Resolution

When checking for a metrics_collector.so, we can see that the file is missing:
ls $GPHOME/lib/postgresql/metrics_collector.so

In this situation, the reason why the file is missing is because the incorrect version of Greenplum is being used. Furthermore,  v6.13.0 was downloaded from "Greenplum® Database by VMware Tanzu™" instead of "VMware Tanzu™ Greenplum®".

To confirm what version you are downloading, you can check on the download page in the Release Details.

The documentation team has been informed that the naming should be changed to add open source to avoid confusion.

The fastest way in this situation to clarify the current downloaded version is checking the file size. The open source is 62MB and the full version is 192MB.

Remove the open source version and download and install the full version.