Hi! Thank you for the pointers. Unfortunately restarting the active mgr daemon didn't help. However looking at cephadm.log gave me at least a clue what was going on. It seems that installing and deinstalling systemd-firewalld has completely messed up the firewall rules. And restarting one of the nodes has made things even worse. The osd's on that node died after a few minutes. I had to restart the osd's systemd services, only to see them tumbling down a few minutes later. Only after I finally flushed all the firewall rules from every single node things went back to "normal". However, orchestrator is still out of sync with reality. So a few more questions: Where does orchestrator store its state information? Is firewalld required for tentacle? I didn't need it for squid, but It sure is now required for the nfs module.Do the other modules also use it to control the firewall? With firewalld installed, would restarting the nodes help to restore the firewall rules? What ports have to be open in the firewall? So far I have: 3000, 3300, 5666, 6789, 6800:7568, 8443, 9093, 9094, 9095, 9100. Anything else? Would it be safe to downgrade to squid again? With best regards Carsten Götze

Am 16.12.2025 um 14:10 schrieb Robert Sander via ceph-users <ceph-users@ceph.io>:

Hi,

Am 16.12.25 um 2:03 PM schrieb Carsten Götze via ceph-users:

...

Is there a way to force the orchestrator to sync its state information with the nodes?

Try to restart the active MGR daemon with systemctl on its node.

...

Where do I find meaningful logs for the orchestrator?

The journal of the active MGR contains cephadm output

Regards -- Robert Sander Linux Consultant

Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: +49 30 405051 - 0 Fax: +49 30 405051 - 19

Amtsgericht Berlin-Charlottenburg - HRB 220009 B Geschäftsführer: Peer Heinlein - Sitz: Berlin _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io