Sorry, the prints were in the syslog. The kernel is version 2.6.24-rc7bidi_02 #5 Fri Jun 6 13:12:08 EDT 2008 i686 i686 i386 GNU/Linux. The open-iscsi is version iscsiadm version 2.0-869. The code came from a 3rd party who supposedly got it from open-iscsi.org.
Here is a snip from syslog (note that Wireshark shows that the connection is not failing ... I get a FIN from open-iscsi): Jun 16 08:41:28 localhost iscsid: connect failed (113) Jun 16 08:42:33 localhost iscsid:last message repeated 11 times Jun 16 08:42:47 localhost iscsid:last message repeated 2 times Jun 16 08:42:47 localhost kernel: session4: iscsi: session recovery timed out after 120 secs Jun 16 08:43:20 localhost iscsid: connect failed (111) Jun 16 08:44:17 localhost iscsid:last message repeated 14 times Jun 16 08:44:17 localhost iscsid: received iferror -38 Jun 16 08:44:17 localhost iscsid: connection4:0 is operational after recovery (34 attempts) Jun 16 08:46:36 localhost kernel: ping timeout of 5 secs expired, last rx 3649030, last ping 3650280, now 3651530 Jun 16 08:46:36 localhost kernel: connection4:0: iscsi: detected conn error (1011) Jun 16 08:46:37 localhost iscsid: Kernel reported iSCSI connection 4:0 error (1011) state (3) Jun 16 08:47:07 localhost iscsid: connect failed (113) Jun 16 08:48:11 localhost iscsid:last message repeated 11 times Jun 16 08:48:36 localhost iscsid:last message repeated 4 times Jun 16 08:48:36 localhost kernel: session4: iscsi: session recovery timed out after 120 secs Jun 16 08:48:36 localhost kernel: iscsi: cmd 0x7f is not queued (8) Jun 16 08:48:42 localhost iscsid: connect failed (113) Jun 16 08:49:43 localhost iscsid:last message repeated 10 times Jun 16 08:50:49 localhost iscsid:last message repeated 11 times Jun 16 08:51:50 localhost iscsid:last message repeated 10 times Jun 16 08:52:51 localhost iscsid:last message repeated 10 times Jun 16 08:53:52 localhost iscsid:last message repeated 10 times Jun 16 08:54:53 localhost iscsid:last message repeated 10 times Eddy -----Original Message----- From: Eddy Quicksall [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2008 4:24 PM To: 'open-iscsi@googlegroups.com' Subject: RE: Dropping the connection There is no prints when it closes the connection. Looking at a wireshark trace, I can see that it just suddenly sends a FIN. Directly after that it logs in again. I have forwarded this message and will get you the answers to your questions. Eddy -----Original Message----- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Mike Christie Sent: Friday, June 13, 2008 4:05 PM To: open-iscsi@googlegroups.com Subject: Re: Dropping the connection Eddy Quicksall wrote: > The iscsi initiator keeps closing the connection (with a FIN) while I'm > testing my target. My target will run real slow because I have lots of > prints. Does the initiator have a timeout such that if it does not receive a > response in time then it will close the connection? If so is there a way to > disable it? > It just has the nop timers you asked about before, and the scsi command timers. If you set the nop timers to zero then we will not drop the connection if we do not get a response in time. If we do drop the connection because of a nop timing out, we spit out a error message about the nop timing out and that we are dropping the connection so you would know that is the reason. The scsi command timer is set by the scsi layer. If the scsi command does not complete in that time, the scsi layer can start its error handler and that can result in us dropping the connection in some kernel/driver versions, if all else fails. The setting is under /sys/block/sdaX/device/timeout and you can change it in the udev rule for scsi devices (see the README for scsi command timer) It is normally 60 seconds. You can write to that file to increase it. If we drop the connection because this you would see a lot of host reset succeeded messages in the log too. What kernel are you using? And what iscsi modules are you using (the ones that come with the kernel or the open-iscsi.org modules)? And what version of open-iscsi? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
