You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Brian Dunlap <bd...@gmail.com> on 2016/06/05 01:18:12 UTC
M2 - gfsh exception stack behavior
Using M2, I'm experimenting with configuring grids on AWS using Ansible.
Using gfsh, when joining node #2 from separate server, I made a mistake on
my locator name (localhost vs. the 1st locator running on box 1) and
received a stack.
In gfsh-land, does there need to be a tweak to catch every stack and only
display the error text?
:)
Here's an example:
gfsh>list members
Name | Id
-------- | -------------------------------------------------
locator1 | ip-10-0-0-171(locator1:9573:locator)<ec><v0>:1024
server1 | ip-10-0-0-171(server1:9783)<ec><v1>:1025
gfsh>start server --name=server2 --locators=localhost[10334]
Starting a GemFire Server in
/opt/geode/apache-geode-1.0.0-incubating.M2/bin/server2...
The Cache Server process terminated unexpectedly with exit status 1. Please
refer to the log file in
/opt/geode/apache-geode-1.0.0-incubating.M2/bin/server2 for full details.
Exception in thread "main" com.gemstone.gemfire.GemFireConfigException:
Unable to join the distributed system. Operation either timed out, was
stopped or Locator does not exist.
at
com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:679)
at
com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:765)
at
com.gemstone.gemfire.distributed.internal.membership.gms.Services.start(Services.java:174)
at
com.gemstone.gemfire.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:105)
at
com.gemstone.gemfire.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:92)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.<init>(DistributionManager.java:1158)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.<init>(DistributionManager.java:1210)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.create(DistributionManager.java:572)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:653)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:278)
at
com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1631)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226)
at
com.gemstone.gemfire.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:55)
at
com.gemstone.gemfire.distributed.ServerLauncher.createCache(ServerLauncher.java:806)
at
com.gemstone.gemfire.distributed.ServerLauncher.start(ServerLauncher.java:726)
at
com.gemstone.gemfire.distributed.ServerLauncher.run(ServerLauncher.java:656)
at
com.gemstone.gemfire.distributed.ServerLauncher.main(ServerLauncher.java:207)
Thanks!
Brian -
Re: M2 - gfsh exception stack behavior
Posted by Anthony Baker <ab...@pivotal.io>.
Thanks for the report Brian! I’ve created a JIRA to track this [1].
Anthony
[1] https://issues.apache.org/jira/browse/GEODE-1506 <https://issues.apache.org/jira/browse/GEODE-1506>
> On Jun 4, 2016, at 6:18 PM, Brian Dunlap <bd...@gmail.com> wrote:
>
> Using M2, I'm experimenting with configuring grids on AWS using Ansible.
>
> Using gfsh, when joining node #2 from separate server, I made a mistake on
> my locator name (localhost vs. the 1st locator running on box 1) and
> received a stack.
>
> In gfsh-land, does there need to be a tweak to catch every stack and only
> display the error text?
> :)
>
> Here's an example:
>
> gfsh>list members
> Name | Id
> -------- | -------------------------------------------------
> locator1 | ip-10-0-0-171(locator1:9573:locator)<ec><v0>:1024
> server1 | ip-10-0-0-171(server1:9783)<ec><v1>:1025
>
> gfsh>start server --name=server2 --locators=localhost[10334]
> Starting a GemFire Server in
> /opt/geode/apache-geode-1.0.0-incubating.M2/bin/server2...
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in
> /opt/geode/apache-geode-1.0.0-incubating.M2/bin/server2 for full details.
>
> Exception in thread "main" com.gemstone.gemfire.GemFireConfigException:
> Unable to join the distributed system. Operation either timed out, was
> stopped or Locator does not exist.
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:679)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:765)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.Services.start(Services.java:174)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:105)
> at
> com.gemstone.gemfire.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:92)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.<init>(DistributionManager.java:1158)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.<init>(DistributionManager.java:1210)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.create(DistributionManager.java:572)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:653)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:278)
> at
> com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1631)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226)
> at
> com.gemstone.gemfire.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:55)
> at
> com.gemstone.gemfire.distributed.ServerLauncher.createCache(ServerLauncher.java:806)
> at
> com.gemstone.gemfire.distributed.ServerLauncher.start(ServerLauncher.java:726)
> at
> com.gemstone.gemfire.distributed.ServerLauncher.run(ServerLauncher.java:656)
> at
> com.gemstone.gemfire.distributed.ServerLauncher.main(ServerLauncher.java:207)
>
>
> Thanks!
> Brian -