t; connecting that monitor to one of the pools.
>>
>> I'm not sure what to try next in order to get ceph to forget about that
>> daemon.
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>>
--
Michael Baer
c...@mikesoffice.com
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
n cephadm shell to hang. And had to
restart managers. I'm not an expert and it could be something obvious,
but I haven't been able to figure out a solution. If anyone has any
suggestions, I would greatly appreciate them.
Thanks,
Mike
--
Michael Baer
c...@mikesoffice.com
_
#x27; is correct, the orchestrator should deploy
OSDs on the node.
FN> If it does not then look for the reason why in ceph -W cephadm
--watch-debug output.
FN> Regards,
FN> Frédéric.
FN> - Le 24 Avr 24, à 3:22, Michael Baer c...@mikesoffice.com a écrit :
&
would just be
c> another OSD. This time it appears to have no affect and similar to the
c> above, I wasn't able to find any obvious error feedback.
c> -Mike
c> _______
c> ceph-users mailing list -- ceph-users@ceph.io
