On 07/26/2010 05:37 PM, Sean S wrote:
Did you see anything from iscsid about why it could not log in? iscsid
writes to /var/log/messages by default.
Does the session/connection ever re-login (you would see some message in
/var/log/messages about connection X:Y is operational after recovery (Z
attempts)?
I'm unable to view /var/log/messages after the failure due to running
as iscsi root. Ulrich mentioned writing the log to a serial port, but
I haven't been able to set this up yet. Would there be an easier way
to get this info post failure?
I forgot you are doing root on iscsi.
How did you get those other kernel messages? If you can just get the
iscsid log info that is sent after lines like this
[<f8bf0876>] iscsi_conn_failure+0x10/0x69 [libiscsi]
[<f9bf202d>] iscsi_eh_abort+0x2f1/0x406 [libiscsi]
but before this line
session1: session recovery timed out after 400 secs
it would be helpful. I am just looking for something about iscsid
segfaulting or hanging or not being able to connect.
What version of open-iscsi-871 are you using is it 871.1 or .2 .3?
On the target box check out /var/log/messages. Is the target even up
still? Did it segfault?
I don't believe anything is going wrong on the target. The target
Do you see anything in /var/log/messages for the target though?
Something about aborts or lun resets completing?
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
