[
https://issues.apache.org/jira/browse/GEODE-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-2364:
--------------------------------
Description:
*Environment*
locator running on Ubuntu 64-bit (192.168.1.45)
server running on OSX (192.168.1.187)
*Steps to Reproduce*
1. Start locator on ubuntu:
{noformat}gfsh start locator --name=locator1
--bind-address=192.168.1.45{noformat}
2. Start server on Mac:
{noformat}gfsh start server --name=server1
--locators=192.168.1.45[10334]{noformat}
3. Start gfsh on Mac and try to connect to the locator:
{noformat}
> gfsh
gfsh> connect --locator=192.168.1.45[10334]{noformat}
*Validate*
{noformat}
gfsh>list members
Name | Id
-------- | -------------------------------------------------
server1 | 192.168.1.187(server1:4242)<v1>:1024
locator1 | 192.168.1.45(locator1:12646:locator)<ec><v0>:1024
{noformat}
*Result*
{code}
gfsh>connect --locator=192.168.1.45[10334]
Connecting to Locator at [host=192.168.1.45, port=10334] ..
Connecting to Manager at [host=192.168.1.45, port=1099] ..
Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
host: 127.0.1.1; nested exception is:
java.net.ConnectException: Operation timed out
Input/output error
Exiting...
Exception in thread "main" java.lang.NullPointerException
at
org.apache.geode.management.internal.cli.Launcher.parseOptions(Launcher.java:252)
at
org.apache.geode.management.internal.cli.Launcher.parseCommandLine(Launcher.java:260)
at
org.apache.geode.management.internal.cli.Launcher.main(Launcher.java:107)
Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
host: 127.0.1.1; nested exception is:
java.net.ConnectException: Operation timed out
{code}
*Work Around*
Start the locator up with additional flags to return the correct address of the
JMX server.
{noformat}
gfsh start locator --name=locator1 --bind-address=192.168.1.45
--J=-Dgemfire.jmx-manager-hostname-for-clients=192.168.1.45
{noformat}
The error should be more informative, guiding the user to these parameters that
need to be specified on startup of the locator. Or the locator should bind to
the JMX port, honoring the {{--bind-address}} flag.
was:
*Environment*
locator running on Ubuntu 64-bit (192.168.1.45)
server running on OSX (192.168.1.187)
*Steps to Reproduce*
1. Start locator on ubuntu:
{noformat}gfsh start locator --name=locator1
--bind-address=192.168.1.45{noformat}
2. Start server on Mac:
{noformat}gfsh start server --name=server1
--locators=192.168.1.45[10334]{noformat}
3. Start gfsh on Mac and try to connect to the locator:
{noformat}
> gfsh
gfsh> connect --locator=192.168.1.45[10334]{noformat}
*Validate*
{noformat}
gfsh>list members
Name | Id
-------- | -------------------------------------------------
server1 | 192.168.1.187(server1:4242)<v1>:1024
locator1 | 192.168.1.45(locator1:12646:locator)<ec><v0>:1024
{noformat}
*Result*
{code}
gfsh>connect --locator=192.168.1.45[10334]
Connecting to Locator at [host=192.168.1.45, port=10334] ..
Connecting to Manager at [host=192.168.1.45, port=1099] ..
Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
host: 127.0.1.1; nested exception is:
java.net.ConnectException: Operation timed out
Input/output error
Exiting...
Exception in thread "main" java.lang.NullPointerException
at
org.apache.geode.management.internal.cli.Launcher.parseOptions(Launcher.java:252)
at
org.apache.geode.management.internal.cli.Launcher.parseCommandLine(Launcher.java:260)
at
org.apache.geode.management.internal.cli.Launcher.main(Launcher.java:107)
Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
host: 127.0.1.1; nested exception is:
java.net.ConnectException: Operation timed out
{code}
*Work Around*
Start the locator up with additional flags to return the correct address of the
JMX server.
{noformat}
gfsh start locator --name=locator1 --bind-address=192.168.1.45
--J=-Dgemfire.jmx-manager-hostname-for-clients=192.168.1.45
--J=-Djava.rmi-server.hostname=192.168.1.45
{noformat}
The error should be more informative, guiding the user to these parameters that
need to be specified on startup of the locator. Or the locator should bind to
the JMX port, honoring the {{--bind-address}} flag.
> gfsh cannot connect to a remote locator
> ---------------------------------------
>
> Key: GEODE-2364
> URL: https://issues.apache.org/jira/browse/GEODE-2364
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Kevin Duling
> Priority: Minor
>
> *Environment*
> locator running on Ubuntu 64-bit (192.168.1.45)
> server running on OSX (192.168.1.187)
> *Steps to Reproduce*
> 1. Start locator on ubuntu:
> {noformat}gfsh start locator --name=locator1
> --bind-address=192.168.1.45{noformat}
> 2. Start server on Mac:
> {noformat}gfsh start server --name=server1
> --locators=192.168.1.45[10334]{noformat}
> 3. Start gfsh on Mac and try to connect to the locator:
> {noformat}
> > gfsh
> gfsh> connect --locator=192.168.1.45[10334]{noformat}
> *Validate*
> {noformat}
> gfsh>list members
> Name | Id
> -------- | -------------------------------------------------
> server1 | 192.168.1.187(server1:4242)<v1>:1024
> locator1 | 192.168.1.45(locator1:12646:locator)<ec><v0>:1024
> {noformat}
> *Result*
> {code}
> gfsh>connect --locator=192.168.1.45[10334]
> Connecting to Locator at [host=192.168.1.45, port=10334] ..
> Connecting to Manager at [host=192.168.1.45, port=1099] ..
> Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
> host: 127.0.1.1; nested exception is:
> java.net.ConnectException: Operation timed out
> Input/output error
> Exiting...
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.geode.management.internal.cli.Launcher.parseOptions(Launcher.java:252)
> at
> org.apache.geode.management.internal.cli.Launcher.parseCommandLine(Launcher.java:260)
> at
> org.apache.geode.management.internal.cli.Launcher.main(Launcher.java:107)
> Could not connect to : [host=192.168.1.45, port=1099]. Connection refused to
> host: 127.0.1.1; nested exception is:
> java.net.ConnectException: Operation timed out
> {code}
> *Work Around*
> Start the locator up with additional flags to return the correct address of
> the JMX server.
> {noformat}
> gfsh start locator --name=locator1 --bind-address=192.168.1.45
> --J=-Dgemfire.jmx-manager-hostname-for-clients=192.168.1.45
> {noformat}
> The error should be more informative, guiding the user to these parameters
> that need to be specified on startup of the locator. Or the locator should
> bind to the JMX port, honoring the {{--bind-address}} flag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
