I thought this had been fixed in recent releases but you might try adding the following option to the server startup: --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true
This seems to fix the hangs that occur on occasion. Mark On Tue, Dec 29, 2015 at 11:56 PM, sri man <manv...@gmail.com> wrote: > Shuvro/Jens/ > > Thanks for the reply. When I run the start server or start locator > command, the command does not return back to the prompt. As a result I > cannot do anything else on that command prompt and I am ending up starting > locator/server and trying to create region in different terminals as shown > below. > > *Command prompt 1:* > gfsh>start locator --name=loc2 --port=8000 > Starting a GemFire Locator in > C:\srikanth\incubator-geode\gemfire-assembly\build\install\apache-geode\bin\loc2... > ................................... > > *Command prompt 2:* > gfsh>start server --name=serv1 --locators=localhost[8000] > Starting a GemFire Server in > C:\srikanth\incubator-geode\gemfire-assembly\build\install\apache-geode\bin\serv1... > ........... > > I think locator and server are starting fine as I see line like "Admitting > member <Toshiba(serv1:5976)<v1>:52734>. Now there are 2 non-admin member(s)." > in the server logs. > > > *Command prompt 3:* > gfsh>create region --name=regionA > "*create region" is not available. Reason: Requires connection.* > > I guess as I am running create region command from a new command prompt I > am seeing the above error. > > Can you please clarify the below ? > > 1. Am I doing something wrong which is causing the start locator/server > commands to not return ? I am on Windows 10. > 2. Is there a way to connect to specific locator (or server?) when > creating region from a different terminal, something similar to > --locators=localhost[8000] ? Couldn't find it by running gfsh>help create > region. > > Greg, > > Sure, I will submit a pull request after resolving my issue. > > Thanks, > Srikanth > > On Tue, Dec 29, 2015 at 11:11 AM, Greg Chase <gch...@pivotal.io> wrote: > >> Please let us know if this works for you and feel free to improve the >> instructions on the wiki so others can know what you had to ask us and >> figure out for yourself. >> >> Thanks! >> >> Greg >> >> This email encrypted by tiny buttons & fat thumbs, beta voice >> recognition, and autocorrect on my iPhone. >> >> On Dec 29, 2015, at 6:49 AM, Jens Deppe <jde...@pivotal.io> wrote: >> >> Hi Srikanth, >> >> Make sure that your 'start locator' and 'start server' commands are run >> from the same gfsh session. If you want to invoke those commands separately >> or from a script you'll need to add '--locators=localhost[10334]' to the >> 'start server' command. >> >> --Jens >> >> On Tue, Dec 29, 2015 at 2:31 AM, Shuvro Das <s...@pivotal.io> wrote: >> >>> Hi Srikanth, >>> >>> Could you please confirm that you are able to see region and members >>> before start the client. >>> Please execute below command on gfsh window >>> 1. list regions >>> 2. list members >>> >>> Thanks and Regards, >>> Shuvro Das >>> >>> On Tue, Dec 29, 2015 at 12:32 PM, sri man <manv...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I am trying out Geode for the first time and having some troubles >>>> getting started. >>>> Any help is appreciated. >>>> >>>> I am following the article "Geode in 5 mins" from >>>> https://github.com/apache/incubator-geode >>>> After starting the locator(start locator --name=locator) and the >>>> server(start server --name=server), when I run the HelloWorld code, I see >>>> the below exception in the client log. >>>> I haven't changed any configurations, I have built the binaries from >>>> the source. >>>> >>>> >>>> [info 2015/12/29 01:46:14.477 EST <main> tid=0x1]* Running in local >>>> mode since mcast-port was 0 and locators was empty*. >>>> [info 2015/12/29 01:46:14.601 EST <main> tid=0x1] Pool DEFAULT started >>>> with multiuser-authentication=false >>>> [info 2015/12/29 01:46:14.622 EST <poolTimer-DEFAULT-2> tid=0x18] >>>> AutoConnectionSource discovered new locators [/192.168.1.103:10334] >>>> Exception in thread "main" >>>> com.gemstone.gemfire.cache.client.NoAvailableServersException >>>> at >>>> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:248) >>>> >>>> *Last few lines of Locator log:* >>>> >>>> [info 2015/12/29 01:15:32.377 EST locator <main> tid=0x1] Locator >>>> started on 192.168.1.103[10334] >>>> [info 2015/12/29 01:15:32.378 EST locator <main> tid=0x1] Starting >>>> server location for Distribution Locator on Toshiba[10334] >>>> [info 2015/12/29 01:15:32.416 EST locator <Pooled Message Processor 1> >>>> tid=0x56] Created disk store cluster_config with unique id >>>> 88d02d9511a746eb-a73bdb64adda8a7f >>>> [info 2015/12/29 01:15:32.427 EST locator <Pooled Message Processor 1> >>>> tid=0x56] recovery region initialization took 0 ms >>>> >>>> *Last few lines of Server log:* >>>> >>>> [info 2015/12/29 01:24:22.649 EST server <main> tid=0x1] *No >>>> locator(s) found with cluster configuration service* >>>> [info 2015/12/29 01:24:22.663 EST server <main> tid=0x1] Initializing >>>> region PdxTypes >>>> [info 2015/12/29 01:24:22.664 EST server <main> tid=0x1] Initialization >>>> of region PdxTypes completed >>>> [info 2015/12/29 01:24:22.675 EST server <main> tid=0x1] Bridge server >>>> connection listener bound to address 0.0.0.0/0.0.0.0:40404 with >>>> backlog 1,000. >>>> [info 2015/12/29 01:24:22.684 EST server <main> tid=0x1] >>>> ClientHealthMonitorThread maximum allowed time between pings: 60,000 >>>> [info 2015/12/29 01:24:22.695 EST server <main> tid=0x1] CacheServer >>>> Configuration: port=40404 max-connections=800 max-threads=0 >>>> notify-by-subscription=true socket-buffer-size=32768 >>>> maximum-time-between-pings=60000 maximum-message-count=230000 >>>> message-time-to-live=180 eviction-policy=none capacity=1 overflow >>>> directory=. groups=[] loadProbe=ConnectionCountProbe loadPollInterval=5000 >>>> tcpNoDelay=true >>>> >>>> Thanks, >>>> Srikanth Manvi >>>> >>>> >>> >> > -- *Mark Secrist | Sr Manager, **Global Education Delivery* msecr...@pivotal.io 970.214.4567 Mobile *pivotal.io <http://www.pivotal.io/>* Follow Us: Twitter <http://www.twitter.com/pivotal> | LinkedIn <http://www.linkedin.com/company/pivotalsoftware> | Facebook <http://www.facebook.com/pivotalsoftware> | YouTube <http://www.youtube.com/gopivotal> | Google+ <https://plus.google.com/105320112436428794490>
