Hi Mike, Well, the log above was just a sample. The underlying 1011 error sometimes appears without a ping error, for example:
Nov 27 17:11:47 hv4 kernel: connection4:0: detected conn error (1011) Nov 27 17:11:48 hv4 iscsid: Kernel reported iSCSI connection 4:0 error (1011) state (3) Nov 27 17:11:54 hv4 iscsid: connection4:0 is operational after recovery (1 attempts) Nov 27 17:11:54 hv4 kernel: connection2:0: detected conn error (1011) Nov 27 17:11:55 hv4 iscsid: Kernel reported iSCSI connection 2:0 error (1011) state (3) Nov 27 17:11:56 hv4 kernel: nfs: server 10.0.43.30 not responding, still trying Nov 27 17:11:59 hv4 iscsid: connection2:0 is operational after recovery (1 attempts) [root@hv4 log]# uname -r 2.6.18-274.7.1.el5xen The connections just fall off the face of the earth at random, and then are picked up a few seconds later. I was thrown into this project so I am not sure where nops/pings are set or unset. Kind Regards, Matt On Tue, Nov 22, 2011 at 5:33 PM, Mike Christie <[email protected]> wrote: > On 11/21/2011 08:48 PM, Matt wrote: > > > > Greetings, > > > > I have seen this error covered in other places in this group but none > > of the solutions I have found seem to be the issue I am facing. > > > > I get errors like the one below at random. As you can see, almost > > immediately the system says it is back up. > > > > This causes any virtual machines attached to go read only. > > > > Nov 21 09:16:13 hv1 kernel: connection4:0: ping timeout of 5 secs > > expired, recv timeout 5, last rx 4393885396, last ping 4393886646, now > > 4393887896 > > Nov 21 09:16:13 hv1 kernel: connection4:0: detected conn error (1011) > > Nov 21 09:16:13 hv1 iscsid: Kernel reported iSCSI connection 4:0 error > > (1011) state (3) > > Nov 21 09:16:14 hv1 kernel: connection3:0: ping timeout of 5 secs > > expired, recv timeout 5, last rx 4393885656, last ping 4393886906, now > > 4393888156 > > Nov 21 09:16:14 hv1 kernel: connection3:0: detected conn error (1011) > > Nov 21 09:16:14 hv1 multipathd: sda: readsector0 checker reports path > > is down > > Nov 21 09:16:14 hv1 multipathd: checker failed path 8:0 in map mpath5 > > Nov 21 09:16:14 hv1 kernel: device-mapper: multipath: Failing path > > 8:0. > > Nov 21 09:16:14 hv1 multipathd: mpath5: remaining active paths: 0 > > Nov 21 09:16:14 hv1 multipathd: dm-2: add map (uevent) > > Nov 21 09:16:14 hv1 multipathd: dm-2: devmap already registered > > Nov 21 09:16:14 hv1 iscsid: Kernel reported iSCSI connection 3:0 error > > (1011) state (3) > > Nov 21 09:16:17 hv1 iscsid: connection4:0 is operational after > > recovery (1 attempts) > > Nov 21 09:16:18 hv1 iscsid: connection3:0 is operational after > > recovery (1 attempts) > > Nov 21 09:16:29 hv1 multipathd: sda: readsector0 checker reports path > > is up > > Nov 21 09:16:29 hv1 multipathd: 8:0: reinstated > > Nov 21 09:16:29 hv1 multipathd: mpath5: remaining active paths: 1 > > Nov 21 09:16:29 hv1 multipathd: dm-2: add map (uevent) > > Nov 21 09:16:29 hv1 multipathd: dm-2: devmap already registered > > > > I am running the following kernel: > > Linux hv1 2.6.18-238.9.1.el5xen > > > > This is CentOS 5.6 64 bit. > > > > Can someone point me in the right direction? Perhaps the ping timeout > > need to be adjusted but I have a feeling this is software related. > > > > If you just turn nops/pings off do you still see the conn error and is > operational messages in the logs. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
