Mike, there is the log, it's create by foreground with debug level 8: (This log iscsid verison is 2.0.869)
iscsid: get conn context 0x63c050 iscsid: message real length is 120 bytes, recv_handle 0x63d950 iscsid: in nlpayload_read iscsid: sched conn context 0x63c050 event 1, tmo 0 iscsid: thread 0x63c050 schedule: delay 0 state 3 iscsid: exec thread 0063c050 callback iscsid: in krecv_pdu_begin iscsid: recv PDU began, pdu handle 0x0x63d988 iscsid: in kread iscsid: read 48 bytes of PDU header iscsid: read 48 PDU header bytes, opcode 0x20, dlength 0, data 0x637af0, max 8192 iscsid: in krecv_pdu_end iscsid: recv PDU finished for pdu handle 0x0x63d988 iscsid: put conn context 0x63c050 iscsid: sending Nop-out pdu with ttt 420002, CmdSN 0: iscsid: in ksend_pdu_begin iscsid: send PDU began for hdr 48 bytes and data 0 bytes iscsid: in kwritev iscsid: wrote 48 bytes of PDU header iscsid: in ksend_pdu_end iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read ***iscsid: can not send nopin response iscsid: thread removed ... ... iscsid: login response status 0101 iscsid: login_rsp ret (8) iscsid: login redirect ... iscsid: re-opening session 1 (reopen_cnt 1) ... ... iscsid: set operational parameter 25 to: iscsid: iscsid: in kset_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: expecting event 16, got 103, handling... iscsid: in nlpayload_read iscsid: received iferror -38 iscsid: set operational parameter 26 to: iscsid: 1 iscsid: in kset_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read ***iscsid: expecting event 16, got 103, handling... iscsid: in nlpayload_read iscsid: received iferror -38 iscsid: set operational parameter 27 to: iscsid: 15 iscsid: in kset_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: expecting event 16, got 103, handling... iscsid: in nlpayload_read iscsid: received iferror -38 iscsid: set operational parameter 28 to: iscsid: 20 iscsid: in kset_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: expecting event 16, got 103, handling... iscsid: in nlpayload_read iscsid: received iferror -38 iscsid: set operational parameter 30 to: iscsid: 5 iscsid: in kset_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: expecting event 16, got 103, handling... iscsid: in nlpayload_read iscsid: received iferror -38 iscsid: set operational parameter 31 to: iscsid: 5 iscsid: in kset_host_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: set operational parameter 1 to: iscsid: iqn.2005-03.org.open-iscsi:3f5b812c71dd iscsid: in kset_host_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: set operational parameter 2 to: iscsid: default iscsid: in kset_host_param iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: set operational parameter 0 to: iscsid: default iscsid: in kstart_conn iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: online device using /sys/bus/scsi/devices/6:0:0:0/state iscsid: mgmt_ipc_write_rsp: rsp to fd -1 iscsid: connection1:0 is operational after recovery (1 attempts) iscsid: thread 0x639f38 schedule: delay 20 state 3 iscsid: noop out timer 0x639f38 start On Oct 4, 9:56 pm, Richard <[EMAIL PROTECTED]> wrote: > Thanks,I think need use it. > On Oct 3, 1:42 am, Mike Christie <[EMAIL PROTECTED]> wrote: > > > Richard wrote: > > > 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) > > > I am sorry to make this difficult, but I need a little before this. > > > I am looking for the, "can not send nopin respons" message and then the > > stuff before that. There might be something like: > > > expecting event %d, got %d, handling... > > > (here %d is some num) > > > or: > > > Recieved iferror %d: %s", > > > where %d is a error and %s is message like no mem or invalid param. > > > or you might see soemthing like: > > > send's begin state machine bug? > > or > > send's end state machine bug?" > > or > > send's end state machine corruption? > > or > > bad event: bug on send_pdu_end? > > > Are you comfortatble applying patches? If so I can send a patch to just > > print exactly what I need, > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
