I there Alan,
I'm not sure who is setting
*-Dgemfire.default.locators=192.168.20.109:192.168.20.109[10334],* but
could you use *--locators=192.168.20.109[10334]* when starting the server?
In addition to that you could start your servers with the following setup:
*
**start server --name=server2 --locators=192.168.20.109[10334]
--mcast-port=0 --server-port=0 --bind-address=192.168.20.100
--server-bind-address=192.168.20.100 --hostname-for-clients=192.168.20.100*
*start server --name=server1 --locators=192.168.20.109[10334]
--mcast-port=0 --server-port=0 --bind-address=192.168.20.109
--server-bind-address=192.168.20.109 --hostname-for-clients=192.168.20.109*
As for the setting --J=-Djava.rmi.server.hostname=192.168.20.109*, *I've
never had to set that before. Maybe you could create a properties file
with the following settings and start your locator with it*:
jmx-manager=true
jmx-manager-bind-address=192.168.20.109
jmx-manager-hostname-for-clients=192.168.20.109
jmx-manager-http-port=7070
jmx-manager-port=1099
jmx-manager-start=true
*
**
*
**start locator --name=locator --properties-file=*{properies file path}*
--port=10334 --bind-address=192.168.20.109
--hostname-for-clients=192.168.20.109*
What seems to be happening, in your set up, is that you have multiple
network interfaces set up on your local machine. Which ends up causing
some issues with Geode when it does not specifically get directed at an
interface.
The fallback is "hostname" which would most likely resolve to
"localhost" which in your case would be the wrong one.
--Udo
On 15/02/2016 5:53 am, Alan Kash wrote:
Hi,
Following this thread -
https://communities.vmware.com/thread/428088?start=0&tstart=0
"The error points to an RMI issue. When starting the locator, please
set the property *java.rmi.server.hostname"*
*
*
*gfsh>start locator --name=l1 --bind-address=192.168.20.109
--hostname-for-clients=192.168.20.109
--J=-Djava.rmi.server.hostname=192.168.20.109
*
*
*
*I was able to set the locator connection.*
*
*
*Starting a new server*
*
*
*
gfsh>start server --name=alps --bind-address=192.168.20.100
Starting a GemFire Server in /home/z/alps...
..............................
Server in /home/z/alps on alps[40404] as alps is currently online.
Process ID: 25858
Uptime: 16 seconds
GemFire Version: 1.0.0-incubating.M2-SNAPSHOT
Java Version: 1.8.0_66
Log File: /home/z/alps/alps.log
JVM Arguments:
-Dgemfire.default.locators=192.168.20.109:192.168.20.109[10334]
-Dgemfire.use-cluster-configuration=true
-Dgemfire.bind-address=192.168.20.100 -XX:OnOutOfMemoryError=kill
-KILL %p -Dgemfire.launcher.registerSignalHandlers=true
-Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/home/z/palindrome/store/geode/apache-geode/lib/gemfire-core-1.0.0-incubating.M2-SNAPSHOT.jar:/home/z/palindrome/store/geode/apache-geode/lib/gemfire-core-dependencies.jar
*
The ServerLauncher process started locally. But, my list member list
is not getting updated with the new server nodes. It always shows
locator address.
gfsh>list members;
Name | Id
---- | ---------------------------------------------
l1 | 192.168.20.109(l1:11926:locator)<ec><v0>:1024
*
*
I am suspecting -
*-Dgemfire.default.locators=192.168.20.109:192.168.20.109[10334] in
JVM Arguments is the issue ? *
*
*
*
*
On Sun, Feb 14, 2016 at 12:27 PM, Luke Shannon <[email protected]
<mailto:[email protected]>> wrote:
This might be easier to figure out if I could see your set up. If
you are interested email me directly and I could take a look in a
short screen share.
On Sun, Feb 14, 2016 at 12:22 PM, Luke Shannon
<[email protected] <mailto:[email protected]>> wrote:
Sorry, I should have been more clear. I was referring to the
Locator. Is it also a separate machine (ie: not the machine
you are working on)?
On Sun, Feb 14, 2016 at 11:42 AM, Alan Kash <[email protected]
<mailto:[email protected]>> wrote:
These are two different physical machines.
192.168.20.109 - Machine 1
192.168.20.100 - Machine 2
On Sun, Feb 14, 2016 at 11:20 AM, Luke Shannon
<[email protected] <mailto:[email protected]>> wrote:
I think this is happening because you are running and
connecting on the same machine, if the locator was on
a different machine you would use that IP. Try
connecting to your locator using 127.0.0.1 or updated
your host file so 192.168.20.109 points to localhost.
On Sun, Feb 14, 2016 at 11:02 AM, Alan Kash
<[email protected] <mailto:[email protected]>> wrote:
Hi,
I am creating a small 2 node distributed
prototype, I am getting locator "Connection
Refused" error.
Source - Build from develop branch - M2.SNAPSHOT
Here is the setup :
1. 192.168.20.109
2. 192.168.20.100
# NODE 1 - Start Locator & Server on - 192.168.20.109
gfsh>start locator --name=l1
gfsh>start server --name=l1s1
gfsh>list members;
Name | Id
---- | -------------------------------------------
l1 | 192.168.20.109(l1:948:locator)<ec><v0>:1024
l1s1 | 192.168.20.109(l1s1:1076)<ec><v1>:1025
# NODE 2 - Connect to Locator - 192.168.20.100
gfsh>connect --locator=192.168.20.109[10334]
Connecting to Locator at [host=192.168.20.109,
port=10334] ..
Connecting to Manager at [host=192.168.20.109,
port=1099] ..
Connection refused to host: 127.0.0.1; nested
exception is:
java.net.ConnectException: Connection refused
I went through the complete documentation there
are no examples of distributed setup/storage/queries.
What am I missing here?
Thanks,
Alan
--
Luke Shannon | Field Engineering | Pivotal
-------------------------------------------------------------------------
Mobile:416-571-9495 <tel:416-571-9495>
Join the Toronto Pivotal Usergroup:
http://www.meetup.com/Toronto-Pivotal-User-Group/
--
Luke Shannon | Field Engineering | Pivotal
-------------------------------------------------------------------------
Mobile:416-571-9495 <tel:416-571-9495>
Join the Toronto Pivotal Usergroup:
http://www.meetup.com/Toronto-Pivotal-User-Group/
--
Luke Shannon | Field Engineering | Pivotal
-------------------------------------------------------------------------
Mobile:416-571-9495 <tel:416-571-9495>
Join the Toronto Pivotal Usergroup:
http://www.meetup.com/Toronto-Pivotal-User-Group/
