Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Vincent Guo wrote: > Hi all: > > I have a problem with installing open-iscsi only by moving files: Huh? Does this have anything to do with the problem in the Subject? > > 1. I have a open-iscis version (2.0-870.1) already installed on a linux > system. > Now I want to move this version to another linux system(with same > configuration as the one already installed). > > I copied the 2 binary files : iscsid and iscsiadm to the folder /usr/sbin; > then copied the 3 ko files: iscsi_tcp.ko , libiscsi.ko and > scsi_transport_iscsi.ko to the folder //lib/modules/`uname > -r`/kernel/drivers/scsi/ > > but when I try to start the iscsid, it fails. > > What other files shold I copy, or do I need other configurations ? Why can't you just build and install on the new box? What was the error iscsid failed with (look in /var/log/messages for possibly more info)? You also need the /etc/iscsi dir, and the initiatorname.iscsi file in /etc/iscsi. You will also want /etc/iscsi/iscsid.conf. And if you want the portals that you already discovered you will basically just want everything in /etc/iscsi (there are some node and sendtargets dirs). You probably also need the init script (/etc/init.d/open-iscsi). --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Hi all: I have a problem with installing open-iscsi only by moving files: 1. I have a open-iscis version (2.0-870.1) already installed on a linux system. Now I want to move this version to another linux system(with same configuration as the one already installed). I copied the 2 binary files : iscsid and iscsiadm to the folder /usr/sbin; then copied the 3 ko files: iscsi_tcp.ko , libiscsi.ko and scsi_transport_iscsi.ko to the folder //lib/modules/`uname -r`/kernel/drivers/scsi/ but when I try to start the iscsid, it fails. What other files shold I copy, or do I need other configurations ? Thanks! Vincent Guo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Forgot to cc Janwar Dinata.
Mike Christie wrote:
> Simone Morellato wrote:
>> Hi,
>>
>> I saw this different behavior in open-iscsi version 2.0.870 compare with
>> 2.0.865
>>
>> Open-iscsi version 2.0.870 doesn't reestablish connection after a logout
>> request from the target.
>>
>> Anybody experience this problem?
>>
>> Is it the new behavior or is it a bug?
>>
>
> Ok it looks like a problem caused but this patch:
>
> 3be3994ae96e40a5a98bfc07450086693cc5cd65
> fix async logout time2wait handling and fix login error handling
>
> 1. if the target sent us an async logout request, then when we
> get the logout response we must use the time2wait value in the logout
> response.
>
> 2. we were skipping the login response parsing in initiator.c.
> If the target sent us a error that is retryable, we were just
> killing the session right away.
>
> I think there are two bugs.
>
> 1. we are using ntohl when converting and the field is only 16 bits.
>
> 2. It looks like your target is giving us something like 36 hours (this
> may be to #1) in the time2wait logout response and we are waiting that
> long to relogin (do connection reinstatement) because we think this
> counts as a implicit logout.
>
> If the Logout Response code is 0 and if the operational
> ErrorRecoveryLevel is 2, this is the minimum amount of time, in
> seconds, to wait before attempting task reassignment. If the Logout
> Response code is 0 and if the operational ErrorRecoveryLevel is less
> than 2, this field is to be ignored.
>
> This field is invalid if the Logout Response code is 1.
>
> If the Logout response code is 2 or 3, this field specifies the
> minimum time to wait before attempting a new implicit or explicit
> logout.
>
> If Time2Wait is 0, the reassignment or a new Logout may be attempted
> immediately.
>
> After the logout we would try Connection Reinstatement (implicit
> logout), and so that is why we were waiting time2wait before trying to
> log back in. But right now we always use the tim2wait but we should be
> checking the response code to see if it is 2 or 3.
>
> So the attached patch should hopefully fix the issue.
>
> >
>
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
--- open-iscsi-2.0-870.1/usr/initiator.c2008-11-22 11:06:46.0
-0600
+++ open-iscsi-2.0-870.1.work/usr/initiator.c 2008-12-02 13:19:21.0
-0600
@@ -1538,12 +1538,13 @@ static void iscsi_recv_nop_in(iscsi_conn
static void iscsi_recv_logout_rsp(iscsi_conn_t *conn, struct iscsi_hdr *hdr)
{
struct iscsi_logout_rsp *logout_rsp = (struct iscsi_logout_rsp *)hdr;
- log_debug(3, "Recv: logout response\n");
-
- conn->session->def_time2wait = ntohl(logout_rsp->t2wait);
- log_debug(4, "logout rsp returned time2wait %u",
- conn->session->def_time2wait);
+ log_debug(3, "Recv: logout response %d\n", logout_rsp->response);
+ if (logout_rsp->response == 2 || logout_rsp->response == 3) {
+ conn->session->def_time2wait = ntohs(logout_rsp->t2wait);
+ log_debug(4, "logout rsp returned time2wait %u",
+ conn->session->def_time2wait);
+ }
/* TODO process the hdr */
__conn_error_handle(conn->session, conn);
}
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote:
> Hi,
>
> I saw this different behavior in open-iscsi version 2.0.870 compare with
> 2.0.865
>
> Open-iscsi version 2.0.870 doesn't reestablish connection after a logout
> request from the target.
>
> Anybody experience this problem?
>
> Is it the new behavior or is it a bug?
>
Ok it looks like a problem caused but this patch:
3be3994ae96e40a5a98bfc07450086693cc5cd65
fix async logout time2wait handling and fix login error handling
1. if the target sent us an async logout request, then when we
get the logout response we must use the time2wait value in the logout
response.
2. we were skipping the login response parsing in initiator.c.
If the target sent us a error that is retryable, we were just
killing the session right away.
I think there are two bugs.
1. we are using ntohl when converting and the field is only 16 bits.
2. It looks like your target is giving us something like 36 hours (this
may be to #1) in the time2wait logout response and we are waiting that
long to relogin (do connection reinstatement) because we think this
counts as a implicit logout.
If the Logout Response code is 0 and if the operational
ErrorRecoveryLevel is 2, this is the minimum amount of time, in
seconds, to wait before attempting task reassignment. If the Logout
Response code is 0 and if the operational ErrorRecoveryLevel is less
than 2, this field is to be ignored.
This field is invalid if the Logout Response code is 1.
If the Logout response code is 2 or 3, this field specifies the
minimum time to wait before attempting a new implicit or explicit
logout.
If Time2Wait is 0, the reassignment or a new Logout may be attempted
immediately.
After the logout we would try Connection Reinstatement (implicit
logout), and so that is why we were waiting time2wait before trying to
log back in. But right now we always use the tim2wait but we should be
checking the response code to see if it is 2 or 3.
So the attached patch should hopefully fix the issue.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
--- open-iscsi-2.0-870.1/usr/initiator.c2008-11-22 11:06:46.0
-0600
+++ open-iscsi-2.0-870.1.work/usr/initiator.c 2008-12-02 13:19:21.0
-0600
@@ -1538,12 +1538,13 @@ static void iscsi_recv_nop_in(iscsi_conn
static void iscsi_recv_logout_rsp(iscsi_conn_t *conn, struct iscsi_hdr *hdr)
{
struct iscsi_logout_rsp *logout_rsp = (struct iscsi_logout_rsp *)hdr;
- log_debug(3, "Recv: logout response\n");
-
- conn->session->def_time2wait = ntohl(logout_rsp->t2wait);
- log_debug(4, "logout rsp returned time2wait %u",
- conn->session->def_time2wait);
+ log_debug(3, "Recv: logout response %d\n", logout_rsp->response);
+ if (logout_rsp->response == 2 || logout_rsp->response == 3) {
+ conn->session->def_time2wait = ntohs(logout_rsp->t2wait);
+ log_debug(4, "logout rsp returned time2wait %u",
+ conn->session->def_time2wait);
+ }
/* TODO process the hdr */
__conn_error_handle(conn->session, conn);
}
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote: > Hi, > > I saw this different behavior in open-iscsi version 2.0.870 compare with > 2.0.865 > Was this 2.0.865.0 or was it 2.0.865.15? Could you also try: http://www.open-iscsi.org/bits/open-iscsi-2.0-869.2.tar.gz so we can try to narrow down when it was introduced? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote: > 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? > Something is horribly wrong. The node.session.timeo.replacement_timeout does not come into play here really. It just deals with when we fail SCSI IO in the kernel. If setting node.session.initial_login_retry_max works that could mean the state machine is out of wack which makes sense if you see >> iSCSI Connection State: TRANSPORT WAIT >> iSCSI Session State: FREE >> Internal iscsid Session State: REPOEN and you are logged back in. There also was a code change in that path in the 870 release. How do you know you are logged back in btw? Do you see this on the target side? For some reason in the ethereal traces I cannot see the iscsi packets. Is there any argument I have to run wireshark with? If you could send the iscsid log with -d 8, it would be helpful. With that I should hopefully see where iscsid is taking a bad turn. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
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: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Mike Christie > Sent: Monday, December 01, 2008 2:14 PM > To: open-iscsi@googlegroups.com > 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 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 -~--~~~~--~~--~--~---
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 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
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? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Here the attachment again, I think I didn't add it. iscsiadm -m session -P3 on 2.0.870 Target: iqn.2005-03.com.astutenetworks:tar1 Current Portal: 10.0.5.103:3261,1 Persistent Portal: 10.0.5.103:3261,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.2005-03.com.redhat:01.computeB014a Iface IPaddress: 10.0.5.27 Iface HWaddress: default Iface Netdev: default SID: 6 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FREE Internal iscsid Session State: REPOEN Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 15360 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 28 State: running scsi28 Channel 00 Id 0 Lun: 0 Attached scsi disk sdc State: running > -Original Message- > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Mike Christie > Sent: Monday, December 01, 2008 12:40 PM > To: open-iscsi@googlegroups.com > Subject: Re: Open-iscsi version 2.0.870 doesn't reestablish connection > after a logout request > > > Simone Morellato wrote: > > Hi Mike, > > > > I am not using an Equalogic target but our own developed one. > > Astute Network makes an iscsi target for ATCA environments. > > > > I am not sending any iscsi traffic I am just logging in using open- > iscsi, then I go to our storage box and I delete a target ( when I delete > a target, our storage box sends out an logout request) and then I recreate > the same exact one. With open-iscsi version 865, I was seeing open-iscsi > re-logging in, with open-iscsi 871 I am not seeing open-iscsi re-login in > automatically. If I try to manually re login the login succeeds. > > > > Attached tarball has these files in it. > > > > [EMAIL PROTECTED] ~]# tar tvf /home/jdinata/myTraces/open- > iscsiTraces.tar.gz > > drwxr-xr-x root/root 0 2008-12-01 11:01:36 traces/ > > -rw-r--r-- root/root 19588 2008-12-01 10:56:42 traces/iscsid.debug > ---> stdout iscsid -d4 -f > > -rw-r--r-- root/root 2348 2008-12-01 10:59:18 traces/msg -- > -> /var/log/messages after I start iscsid > > -rw--- root/root298842 2008-12-01 10:59:50 traces/wireshark2.0- > 870.1 > > -rw-r--r-- root/root 8237 2008-12-01 11:01:36 traces/iscsid.conf -- > -> /etc/iscsi/iscsid.conf > > > > Did you attach open-iscsiTraces.tar.gz? I think the list might have > eaten it. > > If after the async logout, if you do > > iscsiadm -m session -P 3 > what is the output? Is the session listed still? Are the disks under the > session still listed or have they been removed? Could you send it? > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~--- open-iscsiTraces.tar.gz Description: open-iscsiTraces.tar.gz
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote: > Hi Mike, > > I am not using an Equalogic target but our own developed one. > Astute Network makes an iscsi target for ATCA environments. > > I am not sending any iscsi traffic I am just logging in using open-iscsi, > then I go to our storage box and I delete a target ( when I delete a target, > our storage box sends out an logout request) and then I recreate the same > exact one. With open-iscsi version 865, I was seeing open-iscsi re-logging > in, with open-iscsi 871 I am not seeing open-iscsi re-login in automatically. > If I try to manually re login the login succeeds. > > Attached tarball has these files in it. > > [EMAIL PROTECTED] ~]# tar tvf /home/jdinata/myTraces/open-iscsiTraces.tar.gz > drwxr-xr-x root/root 0 2008-12-01 11:01:36 traces/ > -rw-r--r-- root/root 19588 2008-12-01 10:56:42 traces/iscsid.debug > ---> stdout iscsid -d4 -f > -rw-r--r-- root/root 2348 2008-12-01 10:59:18 traces/msg ---> > /var/log/messages after I start iscsid > -rw--- root/root298842 2008-12-01 10:59:50 traces/wireshark2.0-870.1 > -rw-r--r-- root/root 8237 2008-12-01 11:01:36 traces/iscsid.conf ---> > /etc/iscsi/iscsid.conf > Did you attach open-iscsiTraces.tar.gz? I think the list might have eaten it. If after the async logout, if you do iscsiadm -m session -P 3 what is the output? Is the session listed still? Are the disks under the session still listed or have they been removed? Could you send it? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Hi Mike, I am not using an Equalogic target but our own developed one. Astute Network makes an iscsi target for ATCA environments. I am not sending any iscsi traffic I am just logging in using open-iscsi, then I go to our storage box and I delete a target ( when I delete a target, our storage box sends out an logout request) and then I recreate the same exact one. With open-iscsi version 865, I was seeing open-iscsi re-logging in, with open-iscsi 871 I am not seeing open-iscsi re-login in automatically. If I try to manually re login the login succeeds. Attached tarball has these files in it. [EMAIL PROTECTED] ~]# tar tvf /home/jdinata/myTraces/open-iscsiTraces.tar.gz drwxr-xr-x root/root 0 2008-12-01 11:01:36 traces/ -rw-r--r-- root/root 19588 2008-12-01 10:56:42 traces/iscsid.debug ---> stdout iscsid -d4 -f -rw-r--r-- root/root 2348 2008-12-01 10:59:18 traces/msg ---> /var/log/messages after I start iscsid -rw--- root/root298842 2008-12-01 10:59:50 traces/wireshark2.0-870.1 -rw-r--r-- root/root 8237 2008-12-01 11:01:36 traces/iscsid.conf ---> /etc/iscsi/iscsid.conf iscsiadm -v or iscsid -V on 2.0-870.1 will return 2.0-870. Nothing says error/failed explicitly on the debug output 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 No debug output after above line until I logout or login again. Thanks, Simone > -Original Message- > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Mike Christie > Sent: Sunday, November 30, 2008 5:48 PM > To: open-iscsi@googlegroups.com > Subject: Re: Open-iscsi version 2.0.870 doesn't reestablish connection > after a logout request > > > Simone Morellato wrote: > > Hi Mike, > > > > We tried 2.0.870.1 but we are seeing the same behavior. > > > > I attached the new ethereal trace. > > > > Any other idea? > > > > I am not seeing any iscsi traffic in the trace. > > Is this a equalogic target? > > 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 & > > and send that. > > > > > Internal Virus Database is out-of-date. > Checked by AVG. > Version: 7.5.549 / Virus Database: 270.9.9 - Release Date: 11/20/2008 > 12:00 AM > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote: > Hi Mike, > > We tried 2.0.870.1 but we are seeing the same behavior. > > I attached the new ethereal trace. > > Any other idea? > I am not seeing any iscsi traffic in the trace. Is this a equalogic target? 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 & and send that. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Open-iscsi version 2.0.870 doesn't reestablish connection after a logout request
Simone Morellato wrote: > Hi, > > I saw this different behavior in open-iscsi version 2.0.870 compare with > 2.0.865 > > Open-iscsi version 2.0.870 doesn't reestablish connection after a logout > request from the target. > > Anybody experience this problem? > > Is it the new behavior or is it a bug? > Try 870.1. I think this should fix your problem. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
