geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
Date Thu, 14 Jul 2016 22:51:20 GMT

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

ASF GitHub Bot commented on GEODE-746:
--------------------------------------

GitHub user kjduling opened a pull request:

    https://github.com/apache/incubator-geode/pull/208

    GEODE-746: When starting a locator using --bind-address, gfsh prints …

    …incorrect connect message
    
    Respect the bind address flag when launching the locator.
    Added clarification to logging message.

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

    $ git pull https://github.com/kjduling/incubator-geode feature/GEODE-746

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

    https://github.com/apache/incubator-geode/pull/208.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 #208
    
----
commit e5a2692b418a108ecbc648e475edee083f1e446a
Author: Kevin J. Duling <kduling@pivotal.io>
Date:   2016-07-14T22:48:27Z

    GEODE-746: When starting a locator using --bind-address, gfsh prints incorrect connect
message

----


> When starting a locator using --bind-address, gfsh prints incorrect connect message
> -----------------------------------------------------------------------------------
>
>                 Key: GEODE-746
>                 URL: https://issues.apache.org/jira/browse/GEODE-746
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Jens Deppe
>            Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1 --port=19991 --bind-address=192.168.103.1}},
the output from gfsh looks like this:
> {noformat}
> ..............................
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 is currently
online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind address.



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

Mime
View raw message