Octopus mgr doesn't resume after boot
Dear all, I have a two hosts setup, and I recently rebooted a mgr machine without "set noout" and "set norebalance" commands. The "darkside2" machine is the cephadm machine, and "darkside3" is the improperly rebooted mgr. Now the darkside3 machine does not resume ceph configuration: [root@darkside2 ~]# ceph orch host ls HOST ADDR LABELS STATUS darkside2 darkside2 darkside3 172.22.132.189 Offline If I understood the docs correctly, I should [root@darkside2 ~]# ceph orch host add darkside3 But this fails because darkside3 doesn't accept root ssh connnections. I presume this has been discussed before, but I couldn't find the correct thread. Could someone please point me in the right direction? Cordially, Renata.
Hi all! I want to register in this thread the debug and solution of this problem, for future reference. Thanks to Murilo Morais who did all the debugging! The issue happened because when the machine rebooted, it applied a new sshd configuration that prevented root ssh connections. Specifically, I had added an "AllowGroups" line on /etc/ssh/sshd_config to prevent my users from ssh'ing into this machine. For root to continue to be allowed to ssh login with this parameter, I added the "root" group in the "AllowGroups" variable. Perhaps there better solutions, but this works. After fixing this, I restarted ceph.target on the problematic host and did "ceph orch host add darkside3" on the main mgr. Now everything works. Cordially, Renata. On 24/01/2023 14:31, Renata Callado Borges wrote:
Dear all,
I have a two hosts setup, and I recently rebooted a mgr machine without "set noout" and "set norebalance" commands.
The "darkside2" machine is the cephadm machine, and "darkside3" is the improperly rebooted mgr.
Now the darkside3 machine does not resume ceph configuration:
[root@darkside2 ~]# ceph orch host ls HOST ADDR LABELS STATUS darkside2 darkside2 darkside3 172.22.132.189 Offline
If I understood the docs correctly, I should
[root@darkside2 ~]# ceph orch host add darkside3
But this fails because darkside3 doesn't accept root ssh connnections.
I presume this has been discussed before, but I couldn't find the correct thread. Could someone please point me in the right direction?
Cordially,
Renata.
-- Renata Callado Borges Senior Systems Analyst - InCor +55 (11) 2661-4283
participants (1)
-
Renata Callado Borges