[ceph-users] Re: CEPHADM_STRAY_DAEMON

I did find this question: https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/XGLIXRMA5YUVG6P2W6WOQVTN4GJMX3GI/#XGLIXRMA5YUVG6P2W6WOQVTN4GJMX3GI Seems "ceph mgr fail" worked for me in this case. ___ ceph-users mailing list -- ceph-users@ceph.

[ceph-users] Re: CEPHADM_STRAY_DAEMON

Hi, after you added the labels to the MONs, did the orchestrator (re)deploy MONs on the dedicated MON hosts? Are there now 5 MONs running? If the orchestrator didn't clean that up by itself (it can take up to 15 minutes, I believe) you can help it by removing a daemon manually [1]: ceph

[ceph-users] Re: CEPHADM_STRAY_DAEMON does not exist, how do I remove knowledge of it from ceph?

Thanks Adam, 'ceph mgr fail' didn't end up working for me, but it did lead down the path to getting it working. It looks like one of the managers was borked somehow. Although it wasn't the manager that looked to have a stray host, it was the other one. And there also seems to be an issue with ru

[ceph-users] Re: CEPHADM_STRAY_DAEMON does not exist, how do I remove knowledge of it from ceph?

I know there's a bug where when downsizing by multiple mons at once through cephadm this ghost stray mon daemon thing can end up happening (I think something about cephadm removing them too quickly in succession, not totally sure). In those cases, just doing a mgr failover ("ceph mgr fail") always

[ceph-users] Re: CEPHADM_STRAY_DAEMON with iSCSI service

https://tracker.ceph.com/issues/5 -Paul Sent from my iPhone On Dec 8, 2021, at 8:00 AM, Robert Sander wrote: Hi, i just upgraded to 16.2.7 and deployed an iSCSI service. Now I get for each configured target three stray daemons (tcmu-r