On Feb 13, 2013, at 1:23 PM, Gowrav Mahadevaiah <[email protected]> wrote:
> HI, > > I'm working on the a Software iSCSI configuration with IPv4 iSCSI session and > want to enable iscsi error handling debug flag for analyzing an issue. Here > is the steps i followed to enable error handling debug -- > > echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_eh > > The other 2 debug parameters "debug_libiscsi_conn" and > "debug_libiscsi_session" are at value '0'. But, after enable > "debug_libiscsi_eh" flag, I do not see the iscsi verbose error handling > messages in the /var/log/message file. Am I missing any other setting here? > That is all you have to do. How do you know you are running a test that exercises the scsi iscsi eh code paths? Are you seeing aborts/resets get sent by watching the wire with tcpdump/wrireshark or can you see them reach the target side? > If I enable "debug_libiscsi_conn" or "debug_libiscsi_session" flags I see its > corresponding verbose iSCSI messages. > > I even tried increasing the iscsid debug level (iscsid -d 8), but it did not > help either. Please let me know if I missed configuration. > > I'm using software iSCSI pkg -- iscsi-initiator-utils-6.2.0.872-41, on kernel > -- 2.6.32.279. Is that the kernel that comes with RHEL 6.3? If so, I just tried it here and it work ok for me. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
