Hi Mike, I changed the timeouts in the open-iscsi conf file node.session.timeo.replacement_timeout - changed from the 120 default) to 0 node.session.initial_login_retry_max - changed from 4 (default) to 40.
With these changes open-iscsi initiator logs back in but the session State is not correct and we could not send any I/O's over it. before deleting target > iSCSI Connection State: LOGGED IN > iSCSI Session State: LOGGED_IN > Internal iscsid Session State: NO CHANGE > > after target deleted > iSCSI Connection State: TRANSPORT WAIT > iSCSI Session State: FREE > Internal iscsid Session State: REPOEN Does this tell you anything? Thanks, Simone > -----Original Message----- > From: email@example.com [mailto:[EMAIL PROTECTED] On > Behalf Of Mike Christie > Sent: Monday, December 01, 2008 2:14 PM > To: firstname.lastname@example.org > Subject: Re: Open-iscsi version 2.0.870 doesn't reestablish connection > after a logout request > > > Mike Christie wrote: > > Simone Morellato wrote: > >>> Could you just send the log output? There should be a error about > iscsid > >>> not getting something it liked in the login response and it giving up > or > >>> something about a unknown error. It is normally in /var/log/messages. > If > >>> you can run iscsid by hand with debugging on > >>> > >>> iscsid -d 4 -f & > >>> > > > > After this: > > > > iscsid: re-opening session 2 (reopen_cnt 0) > > iscsid: deleting a scheduled/waiting thread! > > iscsid: disconnecting conn 0x8d28ab0, fd 6 > > iscsid: connection 2:0 is stopped for recovery > > > > Is there nothing else? > > > > Could you run iscisd with -d 8 and just send the iscsid.debug again. It > > looks like the state machine is not right. > > > > Does your target use login redirects? If after we logout, then retry the > > login will it redirect us to a new portal? > > > > Hmm, wierd, I just tried this with a equalogic box and it worked ok. I > think we had tested with that box when doing the last releases so that > is expected. > > The only difference may be that > > 1. We do a login redirect for those boxes so we might not be hitting the > same code paths. > > 2. I did not force the asyn logout by deleting a target. In my case, I > just forced a async logout so the re login retry worked right away. For > your test case, does iscsid have to continue retrying the > relogin/reconnect until you add the target back? How long is that? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to email@example.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 -~----------~----~----~----~------~----~------~--~---