Martin wrote: > > > On Oct 20, 1:43 pm, Mike Christie <[EMAIL PROTECTED]> wrote: >> Martin wrote: >>> On Oct 20, 11:51 am, Mike Christie <[EMAIL PROTECTED]> wrote: >>>> Martin wrote: >>>>> Hi, >>>>> I'm trying to login to a linux-iscsi.org target. I issue the >>>>> following: >>>>> iscsiadm -m node -T iqn.2001-09.net.ketsds:keat.storage.fast3 -p >>>>> 10.1.206.2 -l >>>>> and after a long pause get the following error: >>>>> iscsiadm: initiator reported error (11 - iSCSI PDU timed out) >>>>> Any ideas how to diagnose? >>>>> Target is CentOS 5.2 (kernel 2.6.18-92.1.13.e15) running LIO >>>>> 2.9.0.384. I have been able to use the same targets from an MS >>>>> Windows 2008 initiator. >>>>> Initiator is CentOS 5.2 (not sure the kernel) with open-iscsi >>>>> 2.0-868. Discovery (iscsiadm -m discovery -t sendtargets -p >>>>> 10.1.206.2) worked fine. >>>> Are you using CHAP or does the target have some sort of initiator access >>>> list? >>>> Is there anything in /var/log/messages about a login error (and >>>> initiator dropping a pdu)? Is there anything in /var/log/messages from >>>> iscsid? >>>> Could you run iscsid with debugging by hand: >>>> iscsid -d 8 >>>> and send the output.- Hide quoted text - >>>> - Show quoted text - >>> Thanks for the quick response! >>> 1) I am not using CHAP. That is, the target supports CHAP but I did >>> not define any users/passwords and I was able to connect from another >>> initiator without specifying any authentication info. >>> 2) LIO does require me to specify the initiators allowed to use each >>> target. As far as I can tell I've configured that properly... >>> 3) This is what I find in /var/log/messages around the time of an >>> iscsid login attempt: >> Hmmm, maybe two problems. >> >>> Oct 20 12:39:15 ed3492-xen kernel: scsi5 : iSCSI Initiator over TCP/IP >>> Oct 20 12:39:15 ed3492-xen kernel: iscsi: dropping ctask with itt 0x0 >> This is really weird. It would normally only happen if we raced during >> scsi eh processing, but at this point we should not be able to run scsi >> eh processing. We might be getting a bad tag from the target or we might >> have sent the target a bad tag. >> >> What arch are you using? Is it a 64 bit one? Are you doing 64 bit >> kernels and 32 bit userspace by any chance? >> >> Are you using the kernel modules from Centos's kernel and the tools from >> open-iscsi.org's open-iscsi 2.0-868 tarball? Or are you using the >> iscsi-initiator-utils from Centos and the kernel modules from Cento's? >> If you are using a tarball from open-iscsi.org did you do a make and >> make isnstall? Did you install Centos's iscsi-initiator-utils then also >> install the open-iscsi.org tarball tools. >> >>> Oct 20 12:39:15 ed3492-xen iscsid: session [iqn. >>> 2001-09.net.ketsds:keat.storage.fast3,10.1.206.2,3260] already >>> running. >> This and this: >> >>> iscsiadm: Could not login to [iface: default, target: iqn. >>> 2001-09.net.ketsds:keat.storage.fast3, portal: 10.1.206.2,3260]: >>> iscsiadm: initiator reported error (11 - iSCSI PDU timed out) >>> iscsiadm: Could not login to [iface: default, target: iqn. >>> 2001-09.net.ketsds:keat.storage.fast3, portal: 10.1.206.2,3260]: >>> iscsiadm: initiator reported error (15 - already exists) >>> Logging in to [iface: default, target: iqn. >>> 2001-09.net.ketsds:keat.storage.fast3, portal: 10.1.206.2,3260] >>> Logging in to [iface: default, target: iqn. >>> 2001-09.net.ketsds:keat.storage.fast3, portal: 10.1.206.2,3260] >> is a little strange too. Some how you got multiple records with the same >> values. There is only one target and one portal right? Have you recently >> upgraded tools down graded? >> >> You might want to do a "whereis iscsid" and "whereis iscsiadm" and >> "rpm -q iscsi-initiator-utils". >> >> Could you also run >> >> iscsiadm -m node -P 1 >> >> and send the output- Hide quoted text - >> >> - Show quoted text - > > It's all 64-bit as far as I can tell. I should tell you that I've > installed the xen bits on this "client" system as well. > > I installed the open-iscsi bits from the CentOS repository (yum > install iscsi-initiator-utils) > > There are three targets set up on my target host, all via the same > portal and port. > > whereis says > > iscsid: /sbin/iscsid > iscsiadm: /sbin/iscsiadm > > rpm says > > iscsi-initiator-utils-6.2.0.868-0.7.el5 > > > isicsiadm -m node -P 1 says > > Target: iqn.2001-09.net.ketsds:keat.storage.fast1 > Portal: 10.1.206.2:3260,1 > Iface Name: default > Target: iqn.2001-09.net.ketsds:keat.storage.fast2 > Portal: 10.1.206.2:3260,1 > Iface Name: default > Target: iqn.2001-09.net.ketsds:keat.storage.fast3 > Portal: 10.1.206.2:3260,1 > Iface Name: default > Iface Name: default >
Let's try to start from scratch, because the above should not happen. Do rm -f -r /var/lib/iscsi/* Then redo discovery iscsiadm -m discovery -t st ..... -l -P 1 (send this outpout) Then do iscsiadm -m node -P 1 (send this too). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
