[jira] [Commented] (BROOKLYN-108) Postgres entity fails on rebind: serviceUp=false

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BROOKLYN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258166#comment-14258166 ] 

ASF GitHub Bot commented on BROOKLYN-108:
-----------------------------------------

GitHub user aledsage opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/426

    Fix BROOKLYN-108 (correct installDir after rebind)

    

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

    $ git pull https://github.com/aledsage/incubator-brooklyn fix/brooklyn-108

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

    https://github.com/apache/incubator-brooklyn/pull/426.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 #426
    
----
commit c0e49b24080569e579b74adc6ce3cdb09765d2b8
Author: Aled Sage <al...@gmail.com>
Date:   2014-12-24T10:33:52Z

    BROOKLYN-108: use right installDir on rebind

commit 8095ecbccfd5fa48e9ebd3a843331d694dd1a732
Author: Aled Sage <al...@gmail.com>
Date:   2014-12-24T10:34:14Z

    SshMachineLocation: include port in toString

----


> Postgres entity fails on rebind: serviceUp=false
> ------------------------------------------------
>
>                 Key: BROOKLYN-108
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-108
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.7.0-SNAPSHOT
>         Environment: CentOS 6.4
>            Reporter: Aled Sage
>            Assignee: Aled Sage
>
> I deployed Postgres to aws-ec2 successfully (with persistence enabled in Brooklyn). I then stopped and restarted Brooklyn. The rebind to Postgres was successful, but the entity showed as serviceUp=false due to repeated:
> {noformat}
> 2014-12-23 21:48:38,321 DEBUG b.u.task.BasicExecutionManager [brooklyn-execmanager-VcUs2dBg-166]: Exception running task Task[ssh: check-running PostgreSqlNodeImpl{id=bFSjnbH9}:X2rPfdeN] (rethrowing): Execution failed, invalid result 126 for check-running PostgreSqlN
> odeImpl{id=bFSjnbH9}
> {noformat}
> This is happening because postgres `$INSTALL_DIR` is `/home/users/compose/brooklyn-managed-processes/installs/PostgreSqlNode_9.3-1`, which is not visible to the postgres user.
> The command be executed periodically is:
> {noformat}
> export RUN_DIR="/opt/brooklyn/postgres/apps/CUnY9qiv/bFSjnbH9" ; mkdir -p $RUN_DIR ; cd $RUN_DIR ; test -f /opt/brooklyn/postgres/apps/CUnY9qiv/bFSjnbH9/postgresql.pid || exit 1 ; ps -p `cat /opt/brooklyn/postgres/apps/CUnY9qiv/bFSjnbH9/postgresql.pid` ; { sudo -E
>  -n -u postgres -s -- /home/users/compose/brooklyn-managed-processes/installs/PostgreSqlNode_9.3-1/bin/pg_ctl -D /opt/brooklyn/postgres/apps/CUnY9qiv/bFSjnbH9/data -l /opt/brooklyn/postgres/apps/CUnY9qiv/bFSjnbH9/postgresql.log status ; }
> {noformat}
> What I don't understand is why the Postgres entity didn't show as on-fire before Brooklyn was restarted!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)