You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Steve Varnau (JIRA)" <ji...@apache.org> on 2017/04/14 15:26:41 UTC

[jira] [Resolved] (TRAFODION-1989) after uninstall, and reinstall again, dcscheck report dcs master not up

     [ https://issues.apache.org/jira/browse/TRAFODION-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Varnau resolved TRAFODION-1989.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2-incubating

Ambari install portion of the fix is in 2.2
python install was fixed in earlier release

> after uninstall, and reinstall again, dcscheck report dcs master not up
> -----------------------------------------------------------------------
>
>                 Key: TRAFODION-1989
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1989
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: installer
>            Reporter: liu ming
>            Assignee: Steve Varnau
>             Fix For: 2.2-incubating
>
>
> in the same cluster, one install a trafodion version.
> then use trafodion_uninstaller to remove the installation.
> later at same cluster, install again via trafodion_install
> after the new installation, dcscheck fail.
> jps cannot show related DCS java processes, but those processes are up and running.
> It is due to a legacy /tmp/hsperfdata_trafodion direcotry belong to the previous trafodion user. The new user cannot write into this folder, but jps rely on it to work correct. And dcscheck rely on jps to work correctly.
> Either installer remove that legacy directory, or uninstaller remove it. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)