Thanks for taking the trouble to respond I noticed some xfs error on the /var partition so I have rebooted the server in order to force xfs_repair to run
It is now working Steven On Wed, 5 Dec 2018 at 11:47, Mike Christie <mchri...@redhat.com> wrote: > On 12/05/2018 09:43 AM, Steven Vacaroaia wrote: > > Hi, > > I have a strange issue > > I configured 2 identical iSCSI gateways but one of them is complaining > > about negotiations although gwcli reports the correct auth and status ( > > logged-in) > > > > Any help will be truly appreciated > > > > Here are some details > > > > ceph-iscsi-config-2.6-42.gccca57d.el7.noarch > > ceph-iscsi-cli-2.7-54.g9b18a3b.el7.noarch > > tcmu-runner-1.4.0-1.el7.x86_64 > > python-rtslib-2.1.fb67-10.g7713d1e.noarch > > > > no errors in rbd-target-gw or api logs > > > > /var/log/messages > > Dec 2 03:46:10 osd01 kernel: iSCSI Login timeout on Network Portal > > 10.10.35.201:3260 <http://10.10.35.201:3260> > > Dec 2 03:46:10 osd01 kernel: tx_data returned -32, expecting 48. > > Dec 2 03:46:10 osd01 kernel: iSCSI Login negotiation failed > > > > Is this just on the initial discovery and login with vmware initiators > or does it happen repeatedly? Is 10.10.35.201 also the IP address you > set for the discovery address in the vsphere gui? > > If you are seeing this error over and over and also around the same time > in /var/log/tcmu-runner.log or the /var/log/messages on the target side > logs you are seeing cmd timeout errors or something about disabling > iscsi tpgs/ports then this means tcmu-runner is not able execute > commands within 30 seconds. That is normally due to a bad connection to > the cluster, something going wrong on the OSD/Mons, or some big slowdown > on the OSDs or runner not detecting they went down quick enough. >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
