Tim, not everything is a double osd ;-) The message is about a stray mon daemon on a host called ceph-osd3. Check out ‘ceph orch ls mon --export’ to see where the monitors are supposed to be running. Was that an adopted cluster or freshly built with cephadm? Is a different mon daemon running somewhere else? So do you have 3 in total? Maybe it’s a leftover from a failed test? In that case you can just clean it up and remove /var/lib/ceph/{FSID}/mon.ceph-osd3 If the mon is actually supposed to run there, check logs to find out why it’s not running. Zitat von Tim Holloway <timh@mousetech.com>:

Check the /var/lib/ceph directory on host ceph-osd3. If there is an osd.3 directory there, and a /var/lib/ceph/{fsid}/osd.3 directory then you are a member of the schizophrenic OSD club. Congratulations, your membership badge and certificate of Membership will be arriving shortly.

I think you CAN get this problem without having a double-definition of the OSD, but that's always a good place to start looking.

Look at my postings in this forum from back around June-July of this year and you may find some useful information.

   Regards,

     Tim

On 11/7/24 10:13, Michel Niyoyita wrote:

...

Hello team,

I have run a ceph cluster using cephadm Reef , on ubuntu 22.04 , the cluster is composed by 3 mons and 3 hosts running OSDs, after deployment my cluster is in warning state with : [WRN] CEPHADM_STRAY_DAEMON: 1 stray daemon(s) not managed by cephadm . I have run ceph heath detail and the out put is : HEALTH_WARN 1 stray daemon(s) not managed by cephadm [WRN] CEPHADM_STRAY_DAEMON: 1 stray daemon(s) not managed by cephadm stray daemon mon.ceph-osd3 on host ceph-osd3 not managed by cephadm

could you please help to solve this problem?

Best regards

Michel _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io

---

ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io