You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2017/07/12 15:17:00 UTC
[jira] [Closed] (GEODE-1515) Using --bind-address when starting a
locator causes problems
[ https://issues.apache.org/jira/browse/GEODE-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker closed GEODE-1515.
--------------------------------
> Using --bind-address when starting a locator causes problems
> ------------------------------------------------------------
>
> Key: GEODE-1515
> URL: https://issues.apache.org/jira/browse/GEODE-1515
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Jens Deppe
> Fix For: 1.2.0
>
>
> From a slack conversation:
> {noformat}
> start locator --name=locator --J=-Dgemfire.http-service-port=7575 --bind-address=192.168.11.1[10334]
> start server --name=server1 --cache-xml-file=src/main/resources/server-cache.xml --J=-Dgemfire.start-dev-rest-api=true --J=-Dgemfire.http-service-bind-address=192.168.11.1 --J=-Dgemfire.http-service-port=8888 --locators=192.168.11.1[10334] --hostname-for-clients=192.168.11.1 --server-bind-address=192.168.11.1
> fails to connect and gives up
> removing the —bind-address from locator works (but then it binds to all addresses)
> got what I needed with --hostname-for-clients on the locator (so changed bind-address to hostname-for-clients)
> {noformat}
> Original can possibly be found here: https://pivotal.slack.com/archives/gemfire/p1465422522000117
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)