Greg Chase Manager • almost 11 years ago

Greetings Haridarshan,
Thanks for joining into the Hackathon.

Please post your question to user@geode.incubator.apache.org with a description of the error you are seeing.

You may need to subscribe first: user-subscribe@geode.incubator.apache.org - send anything in subject and body. It will then email back a verification email which you reply to, and then you are subscribed.

Thanks!

-Greg

Haridarshan HS • almost 11 years ago

Hi greg,
I sent a mail to the subscription mail id,but havent got any reply yet

Thanks

Anthony Baker Manager • almost 11 years ago

What error are you seeing? Can you post more details?

Haridarshan HS • almost 11 years ago

objc[82833]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
Exception in thread "main" com.gemstone.gemfire.SystemConnectException: Attempt to connect to distributed system timed out
at com.gemstone.gemfire.distributed.internal.membership.jgroup.GFJGBasicAdapter.getSystemConnectException(GFJGBasicAdapter.java:510)
at com.gemstone.org.jgroups.protocols.pbcast.GMS.down(GMS.java:1880)
at com.gemstone.org.jgroups.stack.Protocol.passDown(Protocol.java:769)
at com.gemstone.org.jgroups.protocols.FC.down(FC.java:377)
at com.gemstone.org.jgroups.stack.Protocol.passDown(Protocol.java:769)
at com.gemstone.org.jgroups.protocols.FRAG2.down(FRAG2.java:210)
at com.gemstone.org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:637)
at com.gemstone.org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:471)
at com.gemstone.org.jgroups.JChannel.down(JChannel.java:1301)
at com.gemstone.org.jgroups.JChannel.connect(JChannel.java:509)
at com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager.createChannel(JGroupMembershipManager.java:1547)
at com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager.initialize(JGroupMembershipManager.java:1671)
at com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMemberFactory.newMembershipManager(JGroupMemberFactory.java:112)
at com.gemstone.gemfire.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89)
at com.gemstone.gemfire.distributed.internal.DistributionManager.(DistributionManager.java:1214)
at com.gemstone.gemfire.distributed.internal.DistributionManager.(DistributionManager.java:1266)
at com.gemstone.gemfire.distributed.internal.DistributionManager.create(DistributionManager.java:610)
at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:597)
at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:264)
at com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1571)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:227)
at com.gemstone.gemfire.distributed.ServerLauncher.startWithGemFireApi(ServerLauncher.java:790)
at com.gemstone.gemfire.distributed.ServerLauncher.start(ServerLauncher.java:692)
at com.gemstone.gemfire.distributed.ServerLauncher.run(ServerLauncher.java:622)
at com.gemstone.gemfire.distributed.ServerLauncher.main(ServerLauncher.java:192)

This is the error I am getting when i start the server

Greg Chase Manager • almost 11 years ago

Haridarshan,
It appears that Apache mail server is down at the moment. Sorry about that. My own subscription requests did not go through, and the Apache infrastructure team is looking into it.

Sorry for the inconvenience.

Hopefully Metatype will respond in a timely fashion. Otherwise, I will ask you to post your question to user@geode when the service becomes available again.

Anthony Baker Manager • almost 11 years ago

Thanks for posting the error. What command did you use to start the server? Did you start a locator first?

Haridarshan HS • almost 11 years ago

start locator --name=locator
start server --name=server

These are the commands i used in the gfsh console
I started the locator earlier.However,I am unable to do that now as i am getting the following error
gfsh>start locator --name=locator
Starting a GemFire Locator in /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/locator1...
An error occurred while attempting to start a Locator in /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/locator1 on 192.168.0.5[10334]: sun.tools.attach.MacosxVirtualMachine.isLinuxThreads()Z

Anthony Baker Manager • almost 11 years ago

Your commands look correct. Make sure that you don't have any stray locator processes still running (e.g. jps). You can also look at the log file in the .../locator1 directory for more details.

Haridarshan HS • almost 11 years ago

killed all locator processes and previous server processes.However I am facing the same issue.
Also could you be more specific about the log file location

Anthony Baker Manager • almost 11 years ago

The log files are located in the startup directory (given by the name). For example:

start locator --name=locator1

log files: /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/locator1

Greg Chase Manager • almost 11 years ago

This issue was also discussed in user@geode - you can find it here in the archive: http://mail-archives.apache.org/mod_mbox/incubator-geode-user/201507.mbox/%3C0F4DE596-2823-4D36-B7F0-03B810B95251%40gmail.com%3E

Haridarshan HS • almost 11 years ago

Thanks Greg and Anthony for resolving the issue

Compile failure

12 comments