Is it possible that you have ceph-crash installed (non-cephadm)? Maybe
other ceph packages as well? I recommend to remove all ceph packages
except ceph-common if you intend to use cephadm. But ceph-crash is not
the reason for the failing mon, not sure if you tried to connect those
two things.
Zitat von lejeczek <pelj...@yahoo.co.uk>:
Hi guys.
I'm missing:
/var/lib/ceph/crash/posted
on each node, one node where 'mon' fails:
-> $ ceph health detail
HEALTH_WARN 1 failed cephadm daemon(s); 1/3 mons down, quorum
podster3,podster2
[WRN] CEPHADM_FAILED_DAEMON: 1 failed cephadm daemon(s)
daemon mon.podster1.mine.priv on podster1.mine.priv is in error state
[WRN] MON_DOWN: 1/3 mons down, quorum podster3,podster2
mon.podster1.mine.priv (rank 0) addr
[v2:10.1.1.61:3300/0,v1:10.1.1.61:6789/0] is down (out of quorum)
started logging:
ERROR:ceph-crash:directory /var/lib/ceph/crash/posted does not
exist; please create
Is this expected - on newly deployed cluster with 'cephadm' - that
this path does not exist, with 'crash' module already enabled?
Is this the SOP that user creates (also perhaps do other necessary)
this path manually in order for 'crash' to be functional?
many thanks, L.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
