Could it be possible that you have some misconfiguration in the name
resolution and IP mapping? I've never heard or experienced that a
client requires a cluster address, that would make the whole concept
of separate networks obsolete which is hard to believe, to be honest.
I would recommend to double-check your setup.
Zitat von Amudhan P <amudhan83@xxxxxxxxx>:
Hi Nathan,
Kernel client should be using only the public IP of the cluster to
communicate with OSD's.
But here it requires both IP's for mount to work properly.
regards
Amudhan
On Mon, Nov 9, 2020 at 9:51 PM Nathan Fish <lordcirth@xxxxxxxxx> wrote:
It sounds like your client is able to reach the mon but not the OSD?
It needs to be able to reach all mons and all OSDs.
On Sun, Nov 8, 2020 at 4:29 AM Amudhan P <amudhan83@xxxxxxxxx> wrote:
>
> Hi,
>
> I have mounted my cephfs (ceph octopus) thru kernel client in Debian.
> I get following error in "dmesg" when I try to read any file from my
mount.
> "[ 236.429897] libceph: osd1 10.100.4.1:6891 socket closed (con state
> CONNECTING)"
>
> I use public IP (10.100.3.1) and cluster IP (10.100.4.1) in my ceph
> cluster. I think public IP is enough to mount the share and work on it
but
> in my case, it needs me to assign public IP also to the client to work
> properly.
>
> Does anyone have experience in this?
>
> I have earlier also mailed the ceph-user group but I didn't get any
> response. So sending again not sure my mail went through.
>
> regards
> Amudhan
> _______________________________________________
> 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
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
