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.

So you say you've upgraded all nodes to 0.61.7 and then restarted one, and this happened?

Have you restarted the other mons after you upgraded to 0.61.7, or are they still running an older version?

It could be you simply need to restart the two other mons to fix the problem.

--
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