Hi, At last, the problem fixed for now by adding cluster network IP to the second interface. But It looks weird why the client wants to communicate with Cluster IP. Does anyone have an idea? why we need to provide cluster IP to client mounting thru kernel. Initially, when the cluster was set up it had only public network. later added cluster with cluster IP and it was working fine until the restart of the entire cluster. regards Amudhan P On Fri, Nov 6, 2020 at 12:02 AM Amudhan P <amudhan83@xxxxxxxxx> wrote: > Hi, > I am trying to read file from my ceph kernel mount and file read stays in > bytes for very long and I am getting below error msg in dmesg. > > [ 167.591095] ceph: loaded (mds proto 32) > [ 167.600010] libceph: mon0 10.0.103.1:6789 session established > [ 167.601167] libceph: client144519 fsid f8bc7682-0d11-11eb-a332- > 0cc47a5ec98a > [ 272.132787] libceph: osd1 10.0.104.1:6891 socket closed (con state > CONNECTING) > > Ceph cluster status is healthy no error It was working fine until before > my entire cluster was down. > > Using Ceph octopus in debian. > > Regards > Amudhan P > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |