Hey there Lyndon,

You can try using `jmx-manager-bind-address`, as there seems to be some 
hostname resolution contentions. Also, `jmx-manager-hostname-for-clients` might 
need to be set.

Also, if you intend to use the HTTP services, `http-service-bind-address` might 
need to be set as well.

--Udo


From: Lyndon Adams <lyndon.ad...@gmail.com>
Reply-To: "user@geode.apache.org" <user@geode.apache.org>
Date: Wednesday, February 24, 2021 at 11:14 AM
To: "user@geode.apache.org" <user@geode.apache.org>
Subject: Re: Connecting remotely to Geode on Raspberry Pi 4

So switched off ipv6 and did a reboot of raspberry pi

I can telnet to locator and manager. The netstat output is:

pi@raspberrypi:~/fractalworks/stuff-example-1.0 $ !netstat
netstat -a | grep 41111
tcp        0      0 0.0.0.0:41111           0.0.0.0:*               LISTEN




I them try a remote gfsh session and cannot connect:


gfsh>connect --locator=192.168.86.27[41111]
Connecting to Locator at [host=192.168.86.27, port=41111] ..
Connecting to Manager at [host=raspberrypi.lan, port=1099] ..
Could not connect to : [host=raspberrypi.lan, port=1099]. Connection refused to 
host: 127.0.1.1; nested exception is:
    java.net.ConnectException: Operation timed out




GemFire.properties on pi is:


log-level=INFO
conserve-sockets=false
mcast-port=0
locators=192.168.86.27[41111]
bind-address=192.168.86.27
distributed-system-id=10




Any ideas? Am I missing a key property when starting up gfsh locally, btw I 
don’t pass anything in to gfsh when trying to connect remotely?




Cheers



On 23 Feb 2021, at 21:21, Lyndon Adams 
<lyndon.ad...@gmail.com<mailto:lyndon.ad...@gmail.com>> wrote:

Ah let me see how I change that, thanks. Basically not errors are thrown other 
than a connection timeout
Sent while on the move.


On 23 Feb 2021, at 18:22, Dan Smith 
<dasm...@vmware.com<mailto:dasm...@vmware.com>> wrote:
pi@raspberrypi:~/fractalworks/example-1.0 $ netstat -a | grep 41111
tcp6       0      0 [::]:41111              [::]:*                  LISTEN

Does this mean that geode is only listening for IPV6 traffic? That might 
explain it since you are trying to connect using the IPv4 address.

-Dan

Reply via email to