Hi,
However, in a previous situation I had (while all of them were still
running the older 0.61.4). Rebooting the same MON, did not restore
the quorum also, so I am not sure what may cause this but I supposed
it maybe some other reasons.
Actually it is the same reason.
When upgrading from a v
...@mermaidconsulting.dk]
Sent: Wednesday, 31 July, 2013 6:37 PM
To: Luke Jing Yuan
Cc: ceph-de...@vger.kernel.org; ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Problem with MON after reboot
Hi,
> This happened to me twice actually. Once before I upgraded, using
> 0.61.4 (I solved it by re
Hi,
This happened to me twice actually. Once before I upgraded, using
0.61.4 (I solved it by removing the MON and then recreating it) and
this time after upgrading all nodes to 0.61.7. The surprising thing
to me is that the node is also running OSD as well but after the
upgrade and reboot, the c
: [ceph-users] Problem with MON after reboot
Hi,
> I am having a issue with MON after reboot, I had originally 3 MONs but
> after rebooting one of them, the quorum cannot be established. Digging
Did you happen to upgrade Ceph at some time where you haven't restarted the
daemon?
Which
Hi,
I am having a issue with MON after reboot, I had originally 3 MONs but
after rebooting one of them, the quorum cannot be established. Digging
Did you happen to upgrade Ceph at some time where you haven't restarted
the daemon?
Which version of Ceph do you run on each server?
--
Jens Kr
Dear all,
I am having a issue with MON after reboot, I had originally 3 MONs but after
rebooting one of them, the quorum cannot be established. Digging through the
log of the problematic MON, I found the following messages:
2013-07-31 18:04:18.536331 7f4f41bfd700 0 -- 10.4.132.18:6804/0 >>
10
