status

Check the status of GemFire member processes, including gateway receivers, gateway senders, locators, and servers.

status gateway-receiver

Display the status of the specified gateway receiver.

Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.

Syntax:
status gateway-receiver [--group=value(,value)*] [--member=value]
group Group(s) of Gateway Receivers for which to display status.
member Name/Id of the Gateway Receiver for which to display status.
Example Commands:
status gateway-receiver --group=LN-Group1
status gateway-receiver --member=server1
Sample Output:
gfsh>status gateway-receiver
Member               | Port  | Status
---------------------| ------| -------
pc13(8151)<v2>:26518 | 26837 | Running
pc13(8175)<v4>:53787 | 23753 | Running
pc13(8164)<v3>:24081 | 25457 | Running

Member                       | Error
-----------------------------| ---------------------------------------------------
pc13(Manager:8124)<v1>:52410 | GatewayReceiver is not available or already stopped
pc13(8130):8180              | GatewayReceiver is not available or already stopped


gfsh>status gateway-receiver --member=pc13(8151)<v2>:50130
Member               | Port  |  Status
-------------------- | ----- | --------
pc13(8151)<v2>:50130 | 28592 | Running

gfsh>status gateway-receiver --group=RG1
Member                 | Port  | Status
-----------------------| ------| -------
pc13(8151)<v2>:19450   | 27815 | Running
pc13(8175)<v4>:14139   | 27066 | Running
pc13(8164)<v3>:45150   | 29897 | Running

status gateway-sender

Display the status of the specified gateway sender.

Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.

Syntax:
status gateway-sender --id=value [--group=value(,value)*] 
[--member=value]
id Required. ID of the Gateway Sender.
group Group(s) of Gateway Senders for which to display status. Comma separated list for multiple member groups.
member Name/Id of the Gateway Sender for which to display status.
Example Commands:
status gateway-receiver receiver1-LN --group=LN-Group1;
Sample Output:
gfsh>status gateway-sender --id=ln_Serial
Member                 |  Type  | Runtime Policy | Status
-----------------------| -------| -------------- | -----------
 pc13(8175)<v4>:21449  | Serial | Secondary      | Not Running
 pc13(8151)<v2>:40761  | Serial | Secondary      | Not Running
 pc13(8164)<v3>:33476  | Serial | Secondary      | Not Running

Member                         | Error
------------------------------ | ------------------------------
 pc13(8130):2365               | GatewaySender is not available
 pc13(Manager:8124)<v1>:43821  | GatewaySender is not available

gfsh>status gateway-sender --id=ln_Serial --member=pc13(8151)<v2>:7411
Member               |  Type  | Runtime Policy | Status
-------------------  | ------ | -------------- | -----------
 pc13(8151)<v2>:7411 | Serial | Secondary      | Not Running

gfsh>status gateway-sender --id=ln_Serial --member=pc13(8151)<v2>:7411
Member               |  Type  | Runtime Policy | Status
------------------- -| ------ | -------------- | -------
 pc13(8151)<v2>:7411 | Serial | Primary        | Running

gfsh>status gateway-sender --id=ln_Serial --group=Serial_Sender
==>
Member                 |  Type  | Runtime Policy | Status
---------------------- | -------| -------------- | -----------
 pc13(8151)<v2>:44396  | Serial | Secondary      | Not Running
 pc13(8164)<v3>:29475  | Serial | Secondary      | Not Running
Member                 | Error
---------------------- | ------------------------------
 pc13(8186)<v5>:45840  | GatewaySender is not available

status locator

Displays the status of the specified locator. The status will be one of the following:
  • started
  • online
  • offline
  • not responding

Availability: Online or offline.

Syntax:
status locator [--name=value] [--host=value] [--port=value] 
[--pid=value] [--dir=value]
name Name/Id of the locator for which to display status.
host Hostname or IP address on which the Locator is running.
port Port on which the locator is listening. The default is 10334.
pid Process ID (PID) of the running locator.
dir Directory in which the locator was started. The default is the current directory.
Example Commands:
status locator
status locator --name=locator1
Sample Output:
gfsh>status locator --dir=locator1
Locator in C:\PivotalGemFire70\Latest\locator1 on GemFireStymon[10334] as locator1 
is currently online.
Process ID: 3336
Uptime: 2 hours 15 seconds
GemFire Version: 7.0
Java Version: 1.6.0_26
Log File: C:\PivotalGemFire70\Latest\locator1\locator1.log
JVM Arguments: -Dgemfire.launcher.registerSignalHandlers=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: ;C:\PivotalGemFire70\Latest\lib\gfsh-dependencies.jar;
C:\PivotalGemFire70\Latest\lib\gemfire.jar;C:\PivotalGemFire70\Latest\lib\antlr.jar;
C:\PivotalGemFire70\Latest\lib\mail.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-core.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-logging-juli.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-jasper.jar;
C:\PivotalGemFire70\Latest\lib\ecj-3.7.2.jar;
C:\PivotalGemFire70\Latest\lib\spring-asm-3.1.1.RELEASE.jar;
C:\PivotalGemFire70\Latest\lib\gemfire.jar;C:\PivotalGemFire70\Latest\lib\antlr.jar;
C:\PivotalGemFire70\Latest\lib\gfsh-dependencies.jar;
C:\PivotalGemFire70\Latest\lib\gfSecurityImpl.jar;
C:\PivotalGemFire70\Latest\SampleCode\tutorial\classes;
C:\PivotalGemFire70\Latest\SampleCode\quickstart\classes;
C:\Program Files\Java\jdk1.6.0_26\lib\tools.jar

status server

Display the status of the specified GemFire cache server.

Availability: Online or offline.

Syntax:
status server [--name=value] [--pid=value] [--dir=value]
name Name/Id of the Cache Server for which to display status.
pid Process ID (PID) of the running GemFire Cache Server.
dir Directory in which the GemFire Cache Server was started. The default is the current directory.
Example Commands:
status server
status server --name=server1
Sample Output:
gfsh>status server --name=server1
Server in C:\PivotalGemFire70\Latest\server1 on GemFireStymon[40404] as server1
is currently online.
Process ID: 3828
Uptime: 3 hours 23 seconds
GemFire Version: 7.0
Java Version: 1.6.0_26
Log File: C:\PivotalGemFire70\Latest\server1\server1.log
JVM Arguments: -Dgemfire.launcher.registerSignalHandlers=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: ;C:\PivotalGemFire70\Latest\lib\gfsh-dependencies.jar;
C:\PivotalGemFire70\Latest\lib\gemfire.jar;C:\PivotalGemFire70\Latest\lib\antlr.jar;
C:\PivotalGemFire70\Latest\lib\mail.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-core.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-logging-juli.jar;
C:\PivotalGemFire70\Latest\lib\tomcat-embed-jasper.jar;
C:\PivotalGemFire70\Latest\lib\ecj-3.7.2.jar;
C:\PivotalGemFire70\Latest\lib\spring-asm-3.1.1.RELEASE.jar;
C:\PivotalGemFire70\Latest\lib\gemfire.jar;C:\PivotalGemFire70\Latest\lib\antlr.jar;
C:\PivotalGemFire70\Latest\lib\gfsh-dependencies.jar;
C:\PivotalGemFire70\Latest\lib\gfSecurityImpl.jar;
C:\PivotalGemFire70\Latest\SampleCode\tutorial\classes;
C:\PivotalGemFire70\Latest\SampleCode\quickstart\classes;
C:\Program Files\Java\jdk1.6.0_26\lib\tools.jar