Hello Kitada,
Apologies for the delayed response as I was on VAC!
I tried with your suggestion as well but I am not able to connect to
locator.
Could you please guide me ?
gfsh>start locator --name=locator1 --port=10334
--properties-file=locator1.properties --connect=false
Starting a Geode Locator in /home/dharam/Work/apache-geode-1.2.1/locator1...
........
Locator in /home/dharam/Work/apache-geode-1.2.1/locator1 on
192.168.1.12[10334] as locator1 is currently online.
Process ID: 3808
Uptime: 11 seconds
Geode Version: 1.2.1
Java Version: 1.8.0_151
Log File: /home/dharam/Work/apache-geode-1.2.1/locator1/locator1.log
JVM Arguments:
-DgemfirePropertyFile=/home/dharam/Work/apache-geode-1.2.1/locator1.properties
-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:
/home/dharam/Work/apache-geode-1.2.1/lib/geode-core-1.2.1.jar:/home/dharam/Work/apache-geode-1.2.1/lib/geode-dependencies.jar
gfsh>connect --locator=localhost[10334]
Connecting to Locator at [host=localhost, port=10334] ..
Connecting to Manager at [host=localhost, port=1099] ..
Could not connect to : [host=localhost, port=1099]. Connection refused to
host: 127.0.1.1; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)
*Properties:*
locators=localhost[10334],localhost[10335]
mcast-port=0
jmx-manager=true
jmx-manager-start=true
jmx-manager-port=1099
jmx-manager-ssl-enabled=false
jmx-manager-bind-address=localhost
enable-network-partition-detection=false
http-service-port=9201
http-service-bind-address=dharampc [Same error even if i give localhost]
log-level=debug
*/etc/hosts file >>*
dharam@dharampc :~/Work/apache-geode-1.2.1$ cat /etc/hosts
127.0.0.1 localhost dharampc
*>> hostname*
dharampc
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Thanks,
Dharam
- Dharam Thacker
On Mon, Nov 13, 2017 at 6:34 AM, Akihiro Kitada <[email protected]> wrote:
> Hello Dharam,
>
> As far as I know, it's a behavior brought from GemFire 8.x era somehow.
>
> The workarounds are below.
>
> * add "--connect=false" as parameters for "start locator" command
>
> * add host name (got by "host" command) with the entry for "localhost" in
> /etc/hosts like the following.
> ----
> 127.0.0.1 localhost myhost.mylocaldomain
> ----
>
> Thanks.
>
>
>
> --
> Akihiro Kitada | Staff Customer Engineer | +81 80 3716 3736
> <+81%2080-3716-3736>
> Support.Pivotal.io <http://support.pivotal.io/> | Mon-Fri 9:00am to
> 5:30pm JST | 1-877-477-2269 <(877)%20477-2269>
> [image: support] <https://support.pivotal.io/> [image: twitter]
> <https://twitter.com/pivotal> [image: linkedin]
> <https://www.linkedin.com/company/3048967> [image: facebook]
> <https://www.facebook.com/pivotalsoftware> [image: google plus]
> <https://plus.google.com/+Pivotal> [image: youtube]
> <https://www.youtube.com/playlist?list=PLAdzTan_eSPScpj2J50ErtzR9ANSzv3kl>
>
>
> 2017-11-13 1:31 GMT+09:00 Dharam Thacker <[email protected]>:
>
>> Hi Team,
>>
>> I see strange failure status on locator start up and still locator
>> actually starts up. But I am not able to connect to this locator ever via
>> GFSH/java. i don't see any error/exception in logs even after enabling
>> debug level.
>>
>> This is mainly due to highlighted properties without which it works fine.
>> Is that the correct usage of those ones?
>>
>> >> locator1.properties
>> locators=localhost[10334],localhost[10335]
>> mcast-port=0
>> jmx-manager=true
>> jmx-manager-start=true
>> jmx-manager-port=1098
>> *jmx-manager-ssl-enabled=false*
>> *jmx-manager-bind-address=localhost*
>> enable-network-partition-detection=false
>> http-service-port=9202
>> http-service-bind-address=localhost
>> log-level=config
>>
>>
>> gfsh>start locator --name=locator1 --port=10334 --properties-file=
>> locator1.properties
>> Starting a Geode Locator in /home/dharam/Work/apache-geode
>> -1.2.1/locator1...
>> .........
>> Locator in /home/dharam/Work/apache-geode-1.2.1/locator1 on
>> 192.168.1.12[10334] as locator1 is currently online.
>> Process ID: 16300
>> Uptime: 11 seconds
>> Geode Version: 1.2.1
>> Java Version: 1.8.0_151
>> Log File: /home/dharam/Work/apache-geode-1.2.1/locator1/locator1.log
>> JVM Arguments: -DgemfirePropertyFile=/home/dh
>> aram/Work/apache-geode-1.2.1/locator1.properties
>> -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: /home/dharam/Work/apache-geode-1.2.1/lib/geode-core-1.2.1.
>> jar:/home/dharam/Work/apache-geode-1.2.1/lib/geode-dependencies.jar
>>
>> *Please use "connect --locator=192.168.1.12[10334]" to connect Gfsh to
>> the locator.*
>>
>> *Failed to connect; unknown cause: Connection refused to host: 127.0.1.1;
>> nested exception is: *
>> * java.net.ConnectException: Connection refused (Connection refused)*
>>
>> Cluster configuration service is up and running.
>>
>> Thanks,
>> - Dharam Thacker
>>
>
>
