geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Duling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
Date Thu, 18 Aug 2016 17:12:20 GMT

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

Kevin Duling commented on GEODE-746:
------------------------------------

[~swapnil.bawaskar], can you try this again?  I just tried it with my 10.x address and did
not get the {{Connection refused}} message.

{code}
    _________________________     __
   / _____/ ______/ ______/ /____/ /
  / /  __/ /___  /_____  / _____  / 
 / /__/ / ____/  _____/ / /    / /  
/______/_/      /______/_/    /_/    1.0.0-incubating-SNAPSHOT

Monitor and Manage Apache Geode (incubating)
gfsh>start locator --name=l1 --bind-address=10.118.33.209 --J=-Dgemfire.jmx-manager-bind-address=10.118.33.209
--J=-Dgemfire.jmx-manager-hostname-for-clients=10.118.33.209
Starting a Geode Locator in /Users/kduling/Dev/geode/tmp/l1...
.....
Locator in /Users/kduling/Dev/geode/tmp/l1 on 10.118.33.209[10334] as l1 is currently online.
Process ID: 7625
Uptime: 3 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /Users/kduling/Dev/geode/tmp/l1/l1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.jmx-manager-bind-address=10.118.33.209 -Dgemfire.jmx-manager-hostname-for-clients=10.118.33.209
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/kduling/Dev/geode/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/kduling/Dev/geode/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar

Successfully connected to: JMX Manager [host=10.118.33.209, port=1099]

Cluster configuration service is up and running.
{code}

> 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