Hi Kamila, Thank you for your response. I think we solved it yesterday. I simply removed the mon again and this time I also removed all references to it in ceph.conf (had some remnants there). After that I ran ceph-deploy and after that it haven’t crashed again so far. So in this case it was most likely some leftovers from the old mon in the config that fscked up things. (don’t get why
though, but since it works after I removed all traces of it first and then recreated it). (before that I had removed it, recreated it a bunch of times aswell, but with some leftovers I ceph.conf, that was when it didn’t work) //Anders Från: Kamila Součková [mailto:kamila@xxxxxx]
Hi, I am not sure if this is the same issue as we had recently, but it looks a bit like it -- we also had a Luminous mon crashing right after syncing was done. Turns out that the current release has a bug which causes the mon to crash if it cannot find a mgr daemon. This should be fixed in the upcoming release. In our case we "solved" it by moving the active mgr to the mon's host. (I am not sure how to activate a specific mgr, but it appears that the mgrs get activated in FIFO order -- so just keep killing and re-starting the active one until
a mgr on the mon's host is active). Hope this helps! Kamila On Mon, Nov 6, 2017 at 12:44 PM Anders Olausson <anders@xxxxxxxxxxxx> wrote:
|
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com