Project

General

Profile

Documentation #15888

Running monitors on non-std ports: doc mismatch

Added by Christian Sarrasin almost 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

It's impossible to properly operate monitors on a non-standard port by following official documentation.

http://docs.ceph.com/docs/master/rados/configuration/network-config-ref/#ceph-daemons says:

Tip: The host setting is the short name of the host (i.e., not an fqdn). It is NOT an IP address either. Enter hostname -s on the command line to retrieve the name of the host.

> [mon.a]
> host = {hostname}
> mon addr = {ip-address}:6789
> 

It was discovered (by trial and error and with Greg Farnum's help) that in order to run a monitor on a non standard port (say 1234 rather than 6789), the above setting needs to be:

[mon.a]
        host = {hostname}:1234
        mon addr = {ip-address}:1234

ie: the non-standard port also needs to be provided on the "host" config option. Failing this, clients cannot connect to the monitor as they attempt to use the standard port, as in:

ceph --cluster testcluster status
2016-05-12 13:31:12.246246 7f710478c700 0 -- :/2044977896 >> 192.168.10.201:6789/0 pipe(0x7f7100067550 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7f710005add0).fault
2016-05-12 13:31:15.247057 7f710468b700 0 -- :/2044977896 >> 192.168.10.201:6789/0 pipe(0x7f70f4000c00 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7f70f4004ef0).fault
.... etc ...
^CError connecting to cluster: InterruptedOrTimeoutError

More context: http://article.gmane.org/gmane.comp.file-systems.ceph.user/29489 (and follow-ups)

History

#1 Updated by Zac Dover about 4 years ago

  • Status changed from New to Closed

This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.

If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at .

Also available in: Atom PDF