Hi, there are several existing threads on this list, have you tried to apply those suggestions? A couple of them were: - ceph mgr fail - check time sync (NTP, chrony) - different weights for MONs - Check debug logs Regards, Eugen Zitat von faicker mo <faicker.mo@gmail.com>:
some logs here, 2024-03-13T11:13:34.083+0800 7f6984a95640 4 mon.memb4@3(probing) e6 probe_timeout 0x5650c19d6100 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 bootstrap 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 sync_reset_requester 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 unregister_cluster_logger - not registered 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 cancel_probe_timeout (none scheduled) 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 monmap e6: 5 mons at {memb1=[v2:10.0.4.111:3300/0,v1:10.0.4.111:6789/0],memb2=[v2: 10.0.4.112:3300/0,v1:10.0.4.112:6789/0],memb3=[v2: 10.0.4.113:3300/0,v1:10.0.4.113:6789/0],memb4=[v2: 10.0.4.114:3300/0,v1:10.0.4.114:6789/0],memb5=[v2: 10.0.4.115:3300/0,v1:10.0.4.115:6789/0]} removed_ranks: {} disallowed_leaders: {} 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 _reset 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing).auth v2121 _set_mon_num_rank num 0 rank 0 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 cancel_probe_timeout (none scheduled) 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 timecheck_finish 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 scrub_event_cancel 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 scrub_reset 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 cancel_probe_timeout (none scheduled) 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 reset_probe_timeout 0x5650bb5c9780 after 2 seconds 2024-03-13T11:13:34.083+0800 7f6984a95640 10 mon.memb4@3(probing) e6 probing other monitors 2024-03-13T11:13:34.399+0800 7f697fa05640 10 mon.memb4@3(probing) e6 ms_handle_reset 0x5650bd339800 - 2024-03-13T11:13:34.403+0800 7f697fa05640 10 mon.memb4@3(probing) e6 ms_handle_reset 0x5650c45e2800 -
faicker mo <faicker.mo@gmail.com> 于2024年3月13日周三 16:02写道：
Hello, The problem is a mon stucked in probing state. The env is ceph 18.2.1 on ubuntu22.04 with rdma, 5 mons. One mon memb4 is out of quorum. The debug log is attached. Thanks.
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io