You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/03/06 18:54:00 UTC
[jira] [Resolved] (GEODE-4774) When starting second locator without
Security Manager, displaying incorrect status message
[ https://issues.apache.org/jira/browse/GEODE-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barbara Pruijn resolved GEODE-4774.
-----------------------------------
Resolution: Cannot Reproduce
Tried to reproduce on develop on 3/6/18 to update the text for clearer description and cannot reproduce anymore. Closing for now unless it comes back up again.
> When starting second locator without Security Manager, displaying incorrect status message
> ------------------------------------------------------------------------------------------
>
> Key: GEODE-4774
> URL: https://issues.apache.org/jira/browse/GEODE-4774
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Barbara Pruijn
> Priority: Major
>
> When I start a second locator without a Security Manager (inside a gfsh shell), I get the following output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use "connect --locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
> However, the output should state:
> {code:java}
> Cluster configuration service is up and running.{code}
> How to reproduce:
> {code:java}
> gfsh> start locator --name=locator1
> gfsh> start locator --name=locator2 --port=13489
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)