My understanding is that MONs only configure themselves from the config file at first startup. After that all MONs use the monmap to learn about themselves, and their peers. As such; adding an address to the config file for a running MON, even if you restart / reboot, would not achieve the expect changes, as it doesn't modify the monmap. Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International, Inc. DHilsbos@xxxxxxxxxxxxxx www.PerformAir.com -----Original Message----- From: mafonso@xxxxxxxxx [mailto:mafonso@xxxxxxxxx] Sent: Thursday, June 18, 2020 12:56 AM To: ceph-users@xxxxxxx Subject: Re: Can't bind mon to v1 port in Octopus. After some more testing it seems that ceph just does no pickup on some of ceph.conf changes after bootstrapped. It was possible to bind to the v1 port using `ceph mon set-addrs aio1 [v2:172.16.6.210:3300,v1:172.16.6.210:6789]` It was defo not an issue with OS syscalls or permissions, just ceph not picking up on new config after a restart. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |