On 02/23/2010 02:04 PM, Jonathan Murray wrote:
after about 24 hours, we see the following in /var/log/messages (not in
order)
iscsid: connect failed (111)
iscsi: cmd 0x28 is not queued (8)
iscsi: cmd 0x2a is not queued (8)
iscsi: detected conn error (1011)
Kernel reported iSCSI connection 1:0 error (1011) state (3)
iscsid: connect failed (113)
In /var/log/messages or in the iscsid logs do you see something about a
ping/nop timing out and then see the 1011 conn errors? If so then you
should upgrade to 5.4.
It looks like what is happening is that the target is just dropping the
connection. The initiator tries to reconnect and in one case gets
iscsid: connect failed (111) ======> "Connection refused"
but then in another retry we get
iscsid: connect failed (113) ====> "No route to host".
Are you running with 1 session or multiple ones and are all sessions
going through the same network and to the same target portal?
--
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.
