I'm trying to debug the following open-iscsi initiator errors that are reported in /var/log/messages:
Mar 30 14:19:31 R415-08 kernel: [56802.859946] connection194:0: detected conn error (1010) Mar 30 14:19:34 R415-08 kernel: [56805.373323] connection194:0: detected conn error (1020) Mar 30 14:21:58 R415-08 kernel: [56949.620808] connection117:0: detected conn error (1010) Mar 30 14:22:01 R415-08 kernel: [56952.634359] connection117:0: detected conn error (1020) >From the investigation I've done so far, the "1010" error means ISCSI_ERR_BAD_ITT, which I assume means that the initiator received an iSCSI PDU that contained an ITT that was unexpected. The "1020" error always follows the 1010 error and it apparently means the initiator closed the connection, is that correct? Is there a way to get the unexpected ITT so I can compare it to the iSCSI target debug logs and a wireshark network trace? Would setting the iscsid debug level to a non-zero value help? If so, what's the proper way to do that? I'm running open-iscsi on Ubuntu 10.04 LTS, so it looks like I just need to edit the /etc/init.d/open-iscsi script to enable iscsid debug output. # dpkg -l | grep iscsi ii open-iscsi 2.0.871-0ubuntu4 High performance, transport independent iSCS ii open-iscsi-utils 2.0.871-0ubuntu4 iSCSI initiatior administrative utility # iscsid --version iscsid version 2.0-871 # iscsiadm --version iscsiadm version 2.0-871 Thanks, iscsi developer man -- 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 open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
