You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@madlib.apache.org by "Ekta Khanna (Jira)" <ji...@apache.org> on 2019/11/26 18:35:00 UTC
[jira] [Comment Edited] (MADLIB-1396) Installing MADLib 1.16 Fails,
Reporting Already Installed
[ https://issues.apache.org/jira/browse/MADLIB-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982757#comment-16982757 ]
Ekta Khanna edited comment on MADLIB-1396 at 11/26/19 6:34 PM:
---------------------------------------------------------------
The issue is related to the way the team is setting segment configurations in {{gp_segment_configuration}} table.
In order to avoid installing the package on the same host gppkg installation [dedups the hostnames|https://github.com/greenplum-db/gpdb/blob/6X_STABLE/gpMgmt/bin/gppylib/programs/gppkg.py#L159-L161]. While the team is setting different hostnames referring to the same physical host, which is causing the gppkg installation to fail.
Updating {{gp_segment_configuration}} to reflect same hostnames for the same physical host should resolve the issue.
was (Author: khannaekta):
The issue is related to the way the team is setting segment configurations in {{gp_segment_configuration}} table.
In order to avoid installing the package on the same host gppkg installation [dedups the hostnames|https://github.com/greenplum-db/gpdb/blob/6X_STABLE/gpMgmt/bin/gppylib/programs/gppkg.py#L159-L161]. While the team is setting different hostnames referring to the same physical host, which is causing the gppkg installation to fail.
Resolution: Update {{gp_segment_configuration}} to reflect same hostnames for the same physical host.
> Installing MADLib 1.16 Fails, Reporting Already Installed
> ---------------------------------------------------------
>
> Key: MADLIB-1396
> URL: https://issues.apache.org/jira/browse/MADLIB-1396
> Project: Apache MADlib
> Issue Type: Bug
> Reporter: Stuart Pollock
> Priority: Major
> Fix For: v1.17
>
>
> Installing MADLib on our freshly installed two-node system (running RHEL 7.7 on bare metal) reports that MADLib is already installed, and the installation seems to have failed.
> {{[gpadmin@sdw5 ~]$ gppkg -i }}madlib-1.16+5-gp6-rhel7-x86_64/madlib-1.16+5-gp6-rhel7-x86_64.gppkg
> {{...}}
> {{stderr='warning: waiting for transaction lock on /usr/local/greenplum-db-6.1.0/share/packages/database/.rpm.lock package madlib-1.16-1.x86_64 is already installed}}
> Running the installation again also reports that MADLib is already installed, but the nature of the error is different:
> {{[gpadmin@sdw5 ~]$ gppkg -i }}{{madlib-1.16+5-gp6-rhel7-x86_64/madlib-1.16+5-gp6-rhel7-x86_64.gppkg}}
> {{20191119:08:50:05:105922 gppkg:sdw5:gpadmin-[INFO]:-Starting gppkg with args: -i }}{{madlib-1.16+5-gp6-rhel7-x86_64/madlib-1.16+5-gp6-rhel7-x86_64.gppkg}}
> {{20191119:08:50:05:105922 gppkg:sdw5:gpadmin-[INFO]:-Installing package madlib-1.16+5-gp6-rhel7-x86_64.gppkg}}
> {{20191119:08:50:05:105922 gppkg:sdw5:gpadmin-[INFO]:-Validating rpm installation cmdStr='rpm --test -i /usr/local/greenplum-db-6.1.0/.tmp/madlib-1.16-1.x86_64.rpm --dbpath /usr/lo$al/greenplum-db-6.1.0/share/packages/database --prefix /usr/local/greenplum-db-6.1.0'}}
> {{20191119:08:50:05:105922 gppkg:sdw5:gpadmin-[CRITICAL]:-gppkg failed. (Reason='madlib-1.16+5-gp6-rhel7-x86_64.gppkg is already installed.') exiting...}}
> Please note that .rpm.lock is an issue during the first invocation and not in the second.
> Frequency: This behavior happened two consecutive on clean installations on a system containing GPDB 6.1.0 with GPCC 6.0.0.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)