GFSH command failed with "Command 'XXXX' was found but is not currently available"
search cancel

GFSH command failed with "Command 'XXXX' was found but is not currently available"

book

Article ID: 294424

calendar_today

Updated On:

Products

VMware Tanzu Gemfire

Issue/Introduction

When running a gfsh command or gfsh script, you may encounter a failure message like "Command 'XXXX' was found but is not currently available."
 

Example1:

    _________________________     __
   / _____/ ______/ ______/ /____/ /
  / /  __/ /___  /_____  / _____  / 
 / /__/ / ____/  _____/ / /    / /  
/______/_/      /______/_/    /_/    9.10.9

Monitor and Manage VMware Tanzu GemFire
gfsh>list members
Command 'list members' was found but is not currently available (type 'help' then ENTER to learn about this command)

Example2:

User1$ ./gfsh run --file=/Users/User1/gfshrunningtest.sh
1. Executing - start locator --name=locator1 --locators=localhost[10334] --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.jmx-manager-password-file=********
................................
Locator in /Users/User1/products/pivotal-gemfire-9.10.9/bin/locator1 on 192.168.0.8[10334] as locator1 is currently online.
Process ID: 72704
Uptime: 18 seconds
Geode Version: 9.10.9
Java Version: 11.0.11
Log File: /Users/User1/products/pivotal-gemfire-9.10.9/bin/locator1/locator1.log
JVM Arguments: -Dgemfire.locators=localhost[10334] -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.jmx-manager-start=true -Dgemfire.jmx-manager-password-file=******** -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/User1/products/pivotal-gemfire-9.10.9/lib/geode-core-9.10.9.jar:/Users/User1/products/pivotal-gemfire-9.10.9/lib/geode-dependencies.jar

Unable to auto-connect (Security Manager may be enabled). Please use "connect --locator=192.168.0.8[10334] --user --password" to connect Gfsh to the locator.

Authentication required to connect to the Manager.

2. Executing - configure pdx --read-serialized=true --auto-serializable-classes=".*" --disk-store

Jan 11, 2022 5:22:28 PM org.springframework.shell.core.SimpleParser parse
WARNING: Command 'configure pdx --read-serialized true --auto-serializable-classes ".*" --disk-store' was found but is not currently available (type 'help' then ENTER to learn about this command)
************************* Execution Summary ***********************
Script file: /Users/User1/gfshrunningtest.sh

Command-1 : start locator --name=locator1 --locators=localhost[10334] --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.jmx-manager-password-file=/Users/User1/password.properties
Status    : PASSED

Command-2 : configure pdx --read-serialized=true --auto-serializable-classes=".*" --disk-store
Status    : FAILED


Environment

Product Version: 9.10

Resolution

This message "Command 'XXXX' was found but is not currently available" generally means gfsh was not connected to the locators (or jmx managers) when it tried to run an "online" gfsh command.
Such commands require that gfsh be connected with the locators, via the "connect" command, prior to executing.

Example:

User1$ ./gfsh run --file=/Users/User1/gfshrunningtest.sh
1. Executing - start locator --name=locator1 --locators=localhost[10334] --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.jmx-manager-password-file=********
................................
Locator in /Users/User1/products/pivotal-gemfire-9.10.9/bin/locator1 on 192.168.0.8[10334] as locator1 is currently online.
Process ID: 72704
Uptime: 18 seconds
Geode Version: 9.10.9
Java Version: 11.0.11
Log File: /Users/User1/products/pivotal-gemfire-9.10.9/bin/locator1/locator1.log
JVM Arguments: -Dgemfire.locators=localhost[10334] -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.jmx-manager-start=true -Dgemfire.jmx-manager-password-file=******** -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/User1/products/pivotal-gemfire-9.10.9/lib/geode-core-9.10.9.jar:/Users/User1/products/pivotal-gemfire-9.10.9/lib/geode-dependencies.jar

Unable to auto-connect (Security Manager may be enabled). Please use "connect --locator=192.168.0.8[10334] --user --password" to connect Gfsh to the locator.

Authentication required to connect to the Manager.

2. Executing - connect --locator=localhost[10334] --user=admin --password=********

Connecting to Locator at [host=localhost, port=10334] ..
Connecting to Manager at [host=192.168.0.8, port=1099] ..
Successfully connected to: [host=192.168.0.8, port=1099]

You are connected to a cluster of version: 9.10.9

3. Executing - configure pdx --read-serialized=true --auto-serializable-classes=".*" --disk-store
read-serialized = true
ignore-unread-fields = false
persistent = true
disk-store = DEFAULT
PDX Serializer = org.apache.geode.pdx.ReflectionBasedAutoSerializer
Non Portable Classes = [.*]
Cluster configuration for group 'cluster' is updated.
************************* Execution Summary ***********************
Script file: /Users/User1/gfshrunningtest.sh

Command-1 : start locator --name=locator1 --locators=localhost[10334] --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.jmx-manager-password-file=/Users/User1/password.properties
Status    : PASSED

Command-2 : connect --locator=localhost[10334] --user=admin --password=admin
Status    : PASSED

Command-3 : configure pdx --read-serialized=true --auto-serializable-classes=".*" --disk-store
Status    : PASSED


Powered by Wolken Software