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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TRAFODION-1989:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/1064


> 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
>
> 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)

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TRAFODION-1989:
---

GitHub user svarnau opened a pull request:

https://github.com/apache/incubator-trafodion/pull/1064

[TRAFODION-1989] Add earlier fix to ambari installer



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/svarnau/incubator-trafodion master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafodion/pull/1064.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1064


commit 4ce851bceeb0906f34b17edcb245f7234a25fb19
Author: Steve Varnau 
Date:   2017-04-13T22:06:25Z

[TRAFODION-1989] Add earlier fix to ambari installer




> 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
>
> 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)

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

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1989:
-

thanks Amanda,
If there is already such a handling, then no need to do further. 
We installed the R2.0 build, still have this issue. So it is solved now in 
later version, is there any other JIRA related? So I can close this one.

> 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: Amanda Moran
>
> 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.4#6332)

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

[Amanda Moran (JIRA)]

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

Amanda Moran commented on TRAFODION-1989:
-

trafodion_install has a function fixPermissions


function fixPermissions {

#Change ownership of this file to be owned by traf user and traf group
#Errors with JPS will happen if not modified
if [[ -d /tmp/hsperfdata_trafodion ]]; then
   $TRAF_PDSH sudo chown -R $TRAF_USER.trafodion /tmp/hsperfdata_trafodion
fi

}


If the directory exists then it will changes the permissions of the directory. 
Should the uninstaller remove it if we have this function?

> 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: Amanda Moran
>
> 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.4#6332)