Error starting server process: No available status when starting GemFire XD

Products

• Pivotal GemFire XD

Issue/Introduction

Symptoms:

Issue

When starting GemFire XD it throws the following error:

root@phd1 server1]# gfxd server start -dir=/opt/pivotal/gemfirexd/server1/ -client-port=1528
Starting GemFireXD Server using locators for peer discovery: testing[10334]
Starting network server for GemFireXD Server at address localhost/127.0.0.1[1528]
java.lang.Exception: No available status. Either status file ".gfxdserver.ser" is not readable or reading the status file timed out.
at com.gemstone.gemfire.internal.cache.CacheServerLauncher.waitForRunning(CacheServerLauncher.java:1429)
at com.gemstone.gemfire.internal.cache.CacheServerLauncher.start(CacheServerLauncher.java:622)
at com.pivotal.gemfirexd.tools.internal.GfxdServerLauncher.run(GfxdServerLauncher.java:724)
at com.pivotal.gemfirexd.tools.internal.GfxdServerLauncher.main(GfxdServerLauncher.java:702)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.gemstone.gemfire.internal.GemFireUtilLauncher.invoke(GemFireUtilLauncher.java:167)
at com.pivotal.gemfirexd.tools.GfxdUtilLauncher.invoke(GfxdUtilLauncher.java:228)
at com.pivotal.gemfirexd.tools.GfxdUtilLauncher.main(GfxdUtilLauncher.java:160)
Error starting server process: No available status. Either status file ".gfxdserver.ser" is not readable or reading the status file timed out.

Environment

Cause

1. There is already a .gfxdserver.ser file in the directory form a previous failed start
2. The user GemFire XD runs under doesn´t have permissions to the directory or the .gfxdserver.ser file
3. There is already a process running using the same port
4. There isn´t sufficient memory for the server to start up

Resolution

Check the startserver.log in the GemFire XD working directory. This will normally indicate which of the above causes were encountered.