Hi,
I found this blog post [1] which reports the same error message. It
seems a bit misleading because it appears to be about DNS. Can you check
cephadm check-host --expect-hostname
Or is that what you already tried? It's not entirely clear how you
checked the hostname.
Regards,
Eugen
I have verified the server's expected hostname (with `hostname`) matches
the hostname I am trying to use.
Just to be sure, I also ran:
cephadm check-host --expect-hostname
and it returns:
Hostname "" matches what is expected.
On the current admin server where I am trying to add the host
I don't use rocky, so stab in the dark and probably not the issue, but
could selinux be blocking the process? Really long shot, but python3 is in
the standard location? So if you run python3 --version as your ceph user it
returns?
Probably not much help, but figured I'd throw it out there.
On Mo
I confirmed selinux is disabled on all existing and new hosts. Likewise,
python3.6 is installed on all as well. (3.9.16 on RL8, 3.9.18 on RL9).
I am running 16.2.12 on all containers, so it may be worth updating to
16.2.14 to ensure I'm on the latest Pacific release.
Gary
On 2024-02-05 08:
Just FYI, I've seen this on CentOS systems as well, and I'm not even
sure that it was just for Ceph. Maybe some stuff like Ansible.
I THINK you can safely ignore that message or alternatively that it's
such an easy fix that senility has already driven it from my mind.
Tim
On Tue, 2024-02-06
I still don't have an explanation or other ideas, but I was able to
add a Rocky Linux 9 host to my existing quincy cluster based on
openSUSE (don't have pacific in this environment) quite fast and easy.
It is a fresh Rocky Install, only added cephadm and podman packages,
copied the ceph.pub
Just wanted to follow up on this to say that it is now working.
After reviewing the configuration of the new host many times, I did a
hard restart of the active mrg container.
The command to add the new host proceeded without error.
Thanks everyone.
Gary
On 2024-02-06 16:01, Tim Holloway wr
Oh really? That seems rather trivial but alright. :-D
Zitat von Gary Molenkamp :
Just wanted to follow up on this to say that it is now working.
After reviewing the configuration of the new host many times, I did
a hard restart of the active mrg container.
The command to add the new host pr
Hi everyone.
I had the very same problem, and I believe I've figured out what is happening.
Many admins advise using "ufw limit ssh" to help protect your system against
brute-force password guessing. Well, "ceph orch host add" makes multiple ssh
connections very quickly and triggers the ufw l
