Hi Tim
Thank you for suggestion.
We solved our issue by reboot the _admin node,
Regards
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
I have seen instances where the crash daemon is running under a
container (using /var/lib/cep/{fsid}/crash), but the daemon is trying to
use the legacy location (/varlib/ceph/crash). This can result in file
access violations or "file not found" issues which should show up in the
system logs (jo
and a new issue
when we try to rm and add the crash daemon on already-running host, ceph orch
return them
NAMEHOST PORTSSTATUSREFRESHED
AGE VERSIONIMAGE ID CONTAINER ID
crash.cephgw03 cephgw03starting -
