Hi
I'm new to ceph and have been following the Manual Deployment document [1]. The
process seems to work correctly until step 18 ("Verify that the monitor is
running"):
[centos@cnode-01 ~]$ uname -a
Linux cnode-01 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017
x86_64 x86_64 x86_
loadedactive activeceph target allowing to start/stop all
ceph-mon@.service instances at once
ceph.target
loadedactive activeceph target allowing to start/stop all
ceph*@.service instances at once
c/ceph/ceph.client.admin.keyring:key =
AQC6v5lgi0JBAhAAJ9Duj11SufIKidydIgO82Q==
/tmp/ceph.mon.keyring: key = AQC6v5lgi0JBAhAAJ9Duj11SufIKidydIgO82Q==
[centos@cnode-01 ~]$
From: Eugen Block
Sent: Thursday, May 13, 2021 12:37 AM
To: Tuffli, Chuck
Cc: ceph-users@ceph.io
Subject: Re: [ceph-user
: Thursday, May 13, 2021 9:15 AM
To: Tuffli, Chuck
Cc: ceph-users@ceph.io
Subject: Re: [ceph-users] Re: monitor connection error
Sorry, hit the send the send button too early. Could you try and
rename the keyring file like this?
es-c1.client.admin.keyring:
Zitat von Eugen Block :
> I think you n
^CCluster connection aborted
real6m33.555s
user0m0.140s
sys 0m0.041s
From: Eugen Block
Sent: Thursday, May 13, 2021 9:15 AM
To: Tuffli, Chuck
Cc: ceph-users@ceph.io
Subject: Re: [ceph-users] Re: monitor connection error
Sorry, hit the send the send button
I found a warning in Red Hat documentation regarding OSD and RBD:
Ceph Block Devices must be deployed on separate nodes from the Ceph Monitor and
OSD nodes. Running kernel clients and kernel server daemons on the same node
can lead to kernel deadlocks. [1]
It was hard to tell from the documenta
