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 cluster is able to pick the OSD portion up but not the MON.
Regards, Luke -----Original Message----- From: Jens Kristian Søgaard [mailto:[email protected]] Sent: Wednesday, 31 July, 2013 6:27 PM To: Luke Jing Yuan Cc: [email protected]; [email protected] Subject: Re: [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 version of Ceph do you run on each server? -- Jens Kristian Søgaard, Mermaid Consulting ApS, [email protected], http://www.mermaidconsulting.com/ -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
