Oh, I see that this is probably a bug:
http://tracker.ceph.com/issues/21260
I also noticed following error in mgr logs:
2017-09-06 16:41:08.537577 7f34c0a7a700 1 mgr
send_beacon active
2017-09-06 16:41:08.539161 7f34c0a7a700 1 mgr[restful]
Unknown request ''
2017-09-06 16:41:08.543830 7f34a77de700 0 mgr[restful]
Traceback (most recent call last):
File "/usr/lib64/ceph/mgr/restful/module.py", line 248,
in serve
self._serve()
File "/usr/lib64/ceph/mgr/restful/module.py", line 299,
in _serve
raise RuntimeError('no certificate configured')
RuntimeError: no certificate configured
Probably not related, but what kind of certificate it might refer
to ?
W dniu 06.09.2017 o 16:31, Piotr
Dzionek pisze:
Hi,
I ran a small test two node ceph cluster - 12.2.0 version. It
has 28 osds, 1 mon and 2 mgr. It runs fine, however I noticed
this strange thing in output of ceph versions command:
# ceph versions
{
"mon": {
"ceph version 12.2.0
(32ce2a3ae5239ee33d6150705cdb24d43bab910c) luminous (rc)": 1
},
"mgr": {
"ceph version 12.2.0
(32ce2a3ae5239ee33d6150705cdb24d43bab910c) luminous (rc)": 1,
"unknown": 1
},
"osd": {
"ceph version 12.2.0
(32ce2a3ae5239ee33d6150705cdb24d43bab910c) luminous (rc)": 28
},
"mds": {},
"overall": {
"ceph version 12.2.0
(32ce2a3ae5239ee33d6150705cdb24d43bab910c) luminous (rc)": 30,
"unknown": 1
}
}
As you can see one ceph manager is in unknown state. Why is
that ? FYI, I checked rpms versions and did a restart of all mgr
and I still get the same result.
Kind regards,
Piotr Dzionek
--
Piotr Dzionek
System Administrator
SEQR Poland Sp. z o.o.
ul. Łąkowa 29, 90-554 Łódź, Poland
Mobile: +48 796555587
Mail: piotr.dzionek@xxxxxxxx
www.seqr.com | www.seamless.se
