Thanks. Yes,I also do it. The parameter only turn off iSCSI pings test, log show error from kernel,iscsid can only response reopen action.The debug infomation show: 71686 Sep 26 22:36:47 linux-j2cx kernel: connection1:0: iscsi: detected conn error (1011) 71687 Sep 26 22:36:48 linux-j2cx iscsid: poll result 1 71688 Sep 26 22:36:48 linux-j2cx iscsid: in ctldev_handle 71689 Sep 26 22:36:48 linux-j2cx iscsid: in nl_read 71690 Sep 26 22:36:48 linux-j2cx iscsid: ctldev_handle got event type 102 71691 Sep 26 22:36:48 linux-j2cx iscsid: get conn context 0x63ad00 71692 Sep 26 22:36:48 linux-j2cx iscsid: message real length is 72 bytes, recv_handle 0x63c600 71693 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read 71694 Sep 26 22:36:48 linux-j2cx iscsid: sched conn context 0x63ad00 event 3, tmo 0 71695 Sep 26 22:36:48 linux-j2cx iscsid: thread 0x63ad00 schedule: delay 0 state 3 71696 Sep 26 22:36:48 linux-j2cx iscsid: exec thread 0063ad00 callback 71697 Sep 26 22:36:48 linux-j2cx iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) 71698 Sep 26 22:36:48 linux-j2cx iscsid: put conn context 0x63ad00 71699 Sep 26 22:36:48 linux-j2cx iscsid: re-opening session 1 (reopen_cnt 1) 71700 Sep 26 22:36:48 linux-j2cx iscsid: thread 00638db0 delete: state 3 71701 Sep 26 22:36:48 linux-j2cx iscsid: thread 00638de8 delete: state 1 71702 Sep 26 22:36:48 linux-j2cx iscsid: deleting a scheduled/waiting thread! 71703 Sep 26 22:36:48 linux-j2cx iscsid: in kstop_conn 71704 Sep 26 22:36:48 linux-j2cx iscsid: in __kipc_call 71705 Sep 26 22:36:48 linux-j2cx iscsid: in kwritev 71706 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read 71707 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read 71708 Sep 26 22:36:48 linux-j2cx iscsid: connection 1:0 is stopped for recovery 71709 Sep 26 22:36:48 linux-j2cx iscsid: disconnecting conn 0x636900, fd 9 71710 Sep 26 22:36:48 linux-j2cx iscsid: get conn context 0x63ad00 71711 Sep 26 22:36:48 linux-j2cx iscsid: set TCP recv window size to 524288, actually got 262142 71712 Sep 26 22:36:48 linux-j2cx iscsid: set TCP send window size to 524288, actually got 262142 71713 Sep 26 22:36:48 linux-j2cx iscsid: connecting to 192.168.1.80:3260 71714 Sep 26 22:36:48 linux-j2cx iscsid: sched conn context 0x63ad00 event 2, tmo 0 71715 Sep 26 22:36:48 linux-j2cx iscsid: thread 0x63ad00 schedule: delay 0 state 3 71716 Sep 26 22:36:48 linux-j2cx iscsid: Setting login timer 0x638db0 timeout 15 71717 Sep 26 22:36:48 linux-j2cx iscsid: thread 0x638db0 schedule: delay 60 state 3 71718 Sep 26 22:36:48 linux-j2cx iscsid: thread 0x681418 10172 10222 71719 Sep 26 22:36:48 linux-j2cx kernel: connection2:0: iscsi: detected conn error (1011) 71720 Sep 26 22:36:48 linux-j2cx iscsid: thread removed 71721 Sep 26 22:36:48 linux-j2cx iscsid: thread 0063ad00 removed from poll_list 71722 Sep 26 22:36:48 linux-j2cx iscsid: thread 00681418 wait some more 71724 Sep 26 22:36:48 linux-j2cx iscsid: exec thread 0063ad00 callback 71725 Sep 26 22:36:48 linux-j2cx iscsid: put conn context 0x63ad00 71726 Sep 26 22:36:48 linux-j2cx iscsid: connected local port 34276 to 192.168.1.80:3260 71727 Sep 26 22:36:48 linux-j2cx iscsid: in kbind_conn 71728 Sep 26 22:36:48 linux-j2cx iscsid: in __kipc_call 71729 Sep 26 22:36:48 linux-j2cx iscsid: in kwritev 71730 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read 71731 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read 71732 Sep 26 22:36:48 linux-j2cx iscsid: bound iSCSI connection 1:0 to session 1 71733 Sep 26 22:36:48 linux-j2cx iscsid: sending login PDU with current stage 1, next stage 3, transit 0x80, isid 0x00023d010000 exp_statsn 41145
On Sep 30, 12:36 am, [EMAIL PROTECTED] wrote: > On Sep 27, 9:26 am, iscsiFans <[EMAIL PROTECTED]> wrote: > > > Hi,all, > > I have install Opensuse 10sp3 (x86_64)+ Open-iscsi 2.865(iscsid) + > > Multipath-tools-0.4.7-80, Config and login is ok but I find /var/log/ > > messages have many conne error, so multipath is change-link many > > times, sometime when conn error, the server is hang, such as: > > iscsid v2.0.866 > > Sep 26 11:49:34 linux-j2cx iscsid: can not send nopin response > > I try to change the noop_timeout parameter, But it's no use: > > I do not think changing that value will help in this case, because > above the target is sending us a nop and we are trying to respond to > it. For some reason we are failing on sending a response the targets > nop. > > What target are you using btw? > > If you could run iscsid by hand with debugging by doing > > # iscsid -d 8 -f & > > we can see why it is failing. You might need to stop the iscsi > service, then run > > # iscsiad -d 8 -f & > # iscsiadm -m node -L automatic > > or instead of the last command you can log into a specific target by > doing > > iscsiadm -m node -T target -p ip -l > > Send all the out put from the iscsid. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
