LATEST VERSION: 8.2.8 - CHANGELOG
Pivotal GemFire® v8.2

status

status

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

status cluster-config-service

Displays the status of the cluster configuration service.

Displays the status of cluster configuration service on all the locators where enable-cluster-configuration is set to true.

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

Syntax:
status cluster-config-service
Example Commands:
status cluster-config-service

Sample Output:

gfsh>status cluster-config-service
Status of shared configuration on locators

  Name   | Status
-------- | -------
locator8 | RUNNING

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]
Table 1. Parameters
Name Description
--group Group(s) of Gateway Receivers for which to display status.
--member Name or 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]
Table 2. Parameters
Name Description
--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. If you want to obtain the status of a locator while you are offline, use the --dir or the --pid parameter.

Syntax:
status locator [--name=value] [--host=value] [--port=value] 
[--pid=value] [--dir=value]
Table 3. Parameters
Name Description Default Value
--name Name/ID of the locator for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote locators. See Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS.  
--host Hostname or IP address on which the Locator is running.  
--port Port on which the locator is listening. 10334
--pid Process ID (PID) of the running locator.  
--dir Directory in which the locator was started. current directory
Example Commands:
status locator
status locator --name=locator1
Sample Output:
gfsh>status locator --name=locator1
Locator in /home/stymon/gemfire/locator1 on ubuntu.local[10334] as locator1 is currently online.
Process ID: 2401
Uptime: 12 minutes 3 seconds
GemFire Version: 8.0.0
Java Version: 1.7.0_65
Log File: /home/stymon/gemfire/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /home/stymon/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar:/usr/local/java/lib/tools.jar

Cluster configuration service is up and running.

status server

Display the status of the specified GemFire cache server.

Availability: Online or offline. If you want to obtain the status of a server while you are offline, use the --dir or the --pid parameter.

Syntax:
status server [--name=value] [--pid=value] [--dir=value]
Table 4. Parameters
Name Description Default Value
--name Name or ID of the Cache Server for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote servers. See Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS.  
--pid Process ID (PID) of the running GemFire Cache Server.  
--dir Directory in which the GemFire Cache Server was started. current directory
Example Commands:
status server
status server --name=server1
Sample Output:
gfsh>status server --name=server1
Server in /home/stymon/gemfire/server1 on ubuntu.local[40404] as server1 is currently online.
Process ID: 2726
Uptime: 1 minute 3 seconds
GemFire Version: 8.0.0
Java Version: 1.7.0_65
Log File: /home/stymon/gemfire/server1/server1.log
JVM Arguments: -Dgemfire.default.locators=192.168.129.145[10334] -Dgemfire.use-cluster-configuration=true
 -XX:OnOutOfMemoryError="kill -9 %p" -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /home/stymon/Pivotal_GemFire_800_b48319_Linux/lib/server-dependencies.jar:/usr/local/java/lib/tools.jar