Bug #3135
closed
mon_host without ports leads to failure
Added by Anonymous over 11 years ago.
Updated over 11 years ago.
Description
ceph-mon should default to :6789 if port is not mentioned, however using just
[global]
mon host = 1.2.3.4 5.6.7.8
in ceph.conf, and letting ceph-mon choose its identity based on that, seems to lead to it binding to port :6800, and that confuses clients a lot.
I don't have logs handy, let me know if this doesn't reproduce trivially and I'll recreate the setup.
the code appears to set it to 6789. is it easy for you to reproduce? this must be some strange interaction with the mon bootstrapping..
- Status changed from New to Can't reproduce
I swear this failed for me when I was at a customer site in NYC. That may have been when they were still using the older debs from ubuntu 12.04, though. I can't reproduce this on current stable. Sorry for the noise.
I stumbled on this again. The trigger is this:
- no mon hosts or mon addr specified
- mon finds its own ip via public_network
ubuntu@tvdep01:~$ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 10.214.140.167:6800 0.0.0.0:* LISTEN 16088/ceph-mon
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 766/sshd
tcp6 0 0 :::22 :::* LISTEN 766/sshd
ubuntu@tvdep01:~$
- Status changed from Can't reproduce to New
- Status changed from New to 12
- Assignee set to Sage Weil
- Priority changed from Normal to High
- Status changed from 12 to Resolved
Also available in: Atom
PDF