You have to tell it which Locator, as in... gfsh>status locator --name=l1
Cheers, John On Fri, Feb 12, 2016 at 8:42 PM, Alan Kash <[email protected]> wrote: > Hello Geoders, > > I am creating a prototype for Geode. > > Once I start the locator > > gfsh>start locator --name=l1 > Starting a GemFire Locator in > /home/z/store/geode/apache-geode-1.0.0-incubating.M1/l1... > ...... > Locator in /home/z/store/geode/apache-geode-1.0.0-incubating.M1/l1 on > 192.168.20.109[10334] as l1 is currently online. > Process ID: 4854 > Uptime: 3 seconds > GemFire Version: 1.0.0-incubating.M1 > Java Version: 1.8.0_66 > Log File: /home/z/store/geode/apache-geode-1.0.0-incubating.M1/l1/l1.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/z/store/geode/apache-geode-1.0.0-incubating.M1/lib/gemfire-core-1.0.0-incubating.M1.jar:/home/z/store/geode/apache-geode-1.0.0-incubating.M1/lib/gemfire-core-dependencies.jar > > Successfully connected to: [host=192.168.20.109, port=1099] > > Cluster configuration service is up and running. > > But when I run the status command, it always throw null > > gfsh>status locator > null > > > Because of this, the server and pulse services are not running. > > My Environment > > OS: Fedora 22 > Kernel: 4.3.4-200.fc22.x86_64 > JVM: 1.8.0_66 > > I tested the GemFire 8.2 release, it is running fine. > > Please let me know. > > Thanks, > Aman > -- -John 503-504-8657 john.blum10101 (skype)
