[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667453#comment-15667453 ] Jinmei Liao commented on GEODE-2076: [~jblum] I tried the following gfsh commands, it's working, please let me know what I need to do to reproduce the error. thanks! gfsh>start server --name=server1 --J=-Dgemfire.start-locator=localhost[10334] gfsh>start server --name=server2 --locators=localhost[10334] --server-port=40405 > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668214#comment-15668214 ] John Blum commented on GEODE-2076: -- [~jinmeiliao] - Hmmm Well, I cannot seem to reproduce this now {code} $ echo $GEMFIRE /Users/jblum/pivdev/apache-geode-1.0.0-incubating $ gfsh _ __ / _/ __/ __/ // / / / __/ /___ /_ / _ / / /__/ / / _/ / // / /__/_/ /__/_//_/1.0.0-incubating Monitor and Manage Apache Geode (incubating) gfsh>start server --name=ServerX --log-level=config --J=-Dgemfire.start-locator=localhost[10334] --J=-Dgemfire.enable-cluster-configuration=false --J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true Starting a Geode Server in /Users/jblum/pivdev/lab/ServerX... .. Server in /Users/jblum/pivdev/lab/ServerX on 10.99.199.3[40404] as ServerX is currently online. Process ID: 18873 Uptime: 5 seconds GemFire Version: 1.0.0-incubating Java Version: 1.8.0_72 Log File: /Users/jblum/pivdev/lab/ServerX/ServerX.log JVM Arguments: -Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080 -Dgemfire.start-dev-rest-api=false -Dgemfire.log-level=config -Dgemfire.start-locator=localhost[10334] -Dgemfire.enable-cluster-configuration=false -Dgemfire.jmx-manager=true -Dgemfire.jmx-manager-start=true -XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar gfsh>start server --name=ServerY --log-level=config --disable-default-server --locators=localhost[10334] Starting a Geode Server in /Users/jblum/pivdev/lab/ServerY... . Server in /Users/jblum/pivdev/lab/ServerY on 10.99.199.3 as ServerY is currently online. Process ID: 18916 Uptime: 3 seconds GemFire Version: 1.0.0-incubating Java Version: 1.8.0_72 Log File: /Users/jblum/pivdev/lab/ServerY/ServerY.log JVM Arguments: -Dgemfire.locators=localhost[10334] -Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080 -Dgemfire.start-dev-rest-api=false -Dgemfire.log-level=config -XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar gfsh>connect Connecting to Locator at [host=localhost, port=10334] .. Connecting to Manager at [host=10.99.199.3, port=1099] .. Successfully connected to: [host=10.99.199.3, port=1099] gfsh>list members Name | Id --- | --- ServerX | 10.99.199.3(ServerX:18873):1024 ServerY | 10.99.199.3(ServerY:18916):1025 gfsh> {code} I may have encountered an race condition or just a simple anomaly that last time I encountered this problem, but I did encounter it and the problem persisted through several attempts. Perhaps my _Gfsh_ session was corrupted; I am not sure what happened. Interestingly enough, I also did not encounter the problem with the cache server port, i.e. the {{--disable-default-server}} option worked as expected when starting the second server as well. I am baffled and not sure what was happening before, but, I did encounter those errors. I say close this bug for now and we can reopen it if someone encounters these problems again. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implem
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668227#comment-15668227 ] Jinmei Liao commented on GEODE-2076: Must be you are using an older version of gfsh. I'll close this for now. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668236#comment-15668236 ] Jinmei Liao commented on GEODE-2076: The error you encounter must be because of the gfsh parsing issue we've just discovered: GEODE-2104. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668473#comment-15668473 ] John Blum commented on GEODE-2076: -- No, I was using Gfsh from Apache Geode 1.0.0-incubating, as I demonstrated above. I am always careful to check and report the version I am using. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)