Re: Problem with MON after reboot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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:jens@xxxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, 31 July, 2013 6:27 PM
To: Luke Jing Yuan
Cc: ceph-devel@xxxxxxxxxxxxxxx; ceph-users@xxxxxxxxxxxxxx
Subject: Re:  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, jens@xxxxxxxxxxxxxxxxxxxx, http://www.mermaidconsulting.com/
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com





[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux