Re: iscsistart disconnect

2007-12-19 Thread mutsu 

Thank you, that worked.
I get a disconnect when iscsid runs, but it re-connects and everything
continues fine.
Everything is up and running.

John.
p.s. Silly me, wrong code base :-p

On Dec 11, 6:57 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
> mutsu wrote:
> > I'm running a vanilla 2.6.18 kernel with openvz patched in (stab039)
> > and using iscsi as root.
> > I have iscsistart in the initrd and it boots fine, but after a brief
> > period of time, it disconnects from the server. (under a minute.)
> > Using revision 866 from berlios
>
> Do not use that. It is old. Use what is on the open-iscsi page.
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git
>
>
>
> > When I run iscsistart for root, I get the following error:
> > 1316:913:demo01:MgmtExec: 7-Dec-2007 18:25:24.160914:targetAttr.cc:
> > 933:INFO:7.2.15:iSCSI session to target '10.1.13.21:3260, iqn.
> > 2001-05.com.equallogic:0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-
> > base' from initiator '10.1.4.24:49498, iqn.1997-01.net.verio:ut1-eris'
> > was closed.
> > iSCSI initiator connection failure.
> > No response on connection for 6 seconds.
>
> That is expected in old versions. The nop handling was always done in
> the kernel in old vresions. In new versions (what will be in 2.6.25 and
> in the open-iscsi git tree I linked to above) we handle them in the kernel.
>
>
>
> > I've tried running iscsid and when I do, it disconnects the iscsi root
> > drive and tties to reconnect, but attempts to do so with CHAP turned
> > on. (It is not set on in the configuration on the client or equallogic
> > server)
>
> That is an old bug in the berilos code. Use the git code I pointed to
> and that should be fixed.
>
> For boot you should just use iscsisgtart to start the session in the
> initrd. When the system comes up, you should then start iscsid, because
> that daemon handles error handling. That should all work in the git
> tree. In the berilos tree it should all be broken :)
--~--~-~--~~~---~--~~
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: iscsistart disconnect

2007-12-11 Thread Mike Christie 

mutsu wrote:
> I'm running a vanilla 2.6.18 kernel with openvz patched in (stab039)
> and using iscsi as root.
> I have iscsistart in the initrd and it boots fine, but after a brief
> period of time, it disconnects from the server. (under a minute.)
> Using revision 866 from berlios

Do not use that. It is old. Use what is on the open-iscsi page.
git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git

> 
> When I run iscsistart for root, I get the following error:
> 1316:913:demo01:MgmtExec: 7-Dec-2007 18:25:24.160914:targetAttr.cc:
> 933:INFO:7.2.15:iSCSI session to target '10.1.13.21:3260, iqn.
> 2001-05.com.equallogic:0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-
> base' from initiator '10.1.4.24:49498, iqn.1997-01.net.verio:ut1-eris'
> was closed.
> iSCSI initiator connection failure.
> No response on connection for 6 seconds.

That is expected in old versions. The nop handling was always done in 
the kernel in old vresions. In new versions (what will be in 2.6.25 and 
in the open-iscsi git tree I linked to above) we handle them in the kernel.

> 
> I've tried running iscsid and when I do, it disconnects the iscsi root
> drive and tties to reconnect, but attempts to do so with CHAP turned
> on. (It is not set on in the configuration on the client or equallogic
> server)

That is an old bug in the berilos code. Use the git code I pointed to 
and that should be fixed.

For boot you should just use iscsisgtart to start the session in the 
initrd. When the system comes up, you should then start iscsid, because 
that daemon handles error handling. That should all work in the git 
tree. In the berilos tree it should all be broken :)

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

iscsistart disconnect

2007-12-07 Thread mutsu 

I'm running a vanilla 2.6.18 kernel with openvz patched in (stab039)
and using iscsi as root.
I have iscsistart in the initrd and it boots fine, but after a brief
period of time, it disconnects from the server. (under a minute.)
Using revision 866 from berlios

When I run iscsistart for root, I get the following error:
1316:913:demo01:MgmtExec: 7-Dec-2007 18:25:24.160914:targetAttr.cc:
933:INFO:7.2.15:iSCSI session to target '10.1.13.21:3260, iqn.
2001-05.com.equallogic:0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-
base' from initiator '10.1.4.24:49498, iqn.1997-01.net.verio:ut1-eris'
was closed.
iSCSI initiator connection failure.
No response on connection for 6 seconds.

I've tried running iscsid and when I do, it disconnects the iscsi root
drive and tties to reconnect, but attempts to do so with CHAP turned
on. (It is not set on in the configuration on the client or equallogic
server)
These are the messages on the server:
1274:879:demo01:MgmtExec: 7-Dec-2007 18:06:16.490880:targetAttr.cc:
688:INFO:7.2.14:iSCSI login to target '10.1.13.21:3260, iqn.
2001-05.com.equallogic:0-8a0906-da3233602-1fbfb1cddf64759b-dl.ut1-eris-
base' from initiator '10.1.4.24:51567, iqn.1997-01.net.verio:ut1-eris'
successful, using Jumbo Frame length.
1275:880:demo01:MgmtExec: 7-Dec-2007 18:07:21.760881:targetAttr.cc:
933:INFO:7.2.15:iSCSI session to target '10.1.13.21:3260, iqn.
2001-05.com.equallogic:0-8a0906-da3233602-1fbfb1cddf64759b-dl.ut1-eris-
base' from initiator '10.1.4.24:51567, iqn.1997-01.net.verio:ut1-eris'
was closed.
iSCSI initiator connection failure.
Connection was closed by peer.
1276:881:demo01:MgmtExec: 7-Dec-2007 18:07:22.510882:targetAttr.cc:
498:ERROR:7.4.3:iSCSI login to target '10.1.13.21:3260, iqn.
2001-05.com.equallogic:0-8a0906-da3233602-1fbfb1cddf64759b-dl.ut1-eris-
base' from initiator '10.1.4.24:44170, iqn.1997-01.net.verio:ut1-luna'
failed for the following reason:
Initiator attempted to authenticate but volume access control
not configured for CHAP.

The sequence I use to run this is:
modprobe iscsi_tcp
iscsistart -i iqn.1997-01.net.verio:ut1-eris -t iqn.
2001-05.com.equallogic:0-8a0906-da3233602-1fbfb1cddf64759b-dl.ut1-eris-
base -g 1 -a 10.1.13.20
iscsid -f -d 9

The iscsid output follows:
iscsid: transport class version 2.0-865. iscsid version 2.0-865
iscsid: in ctldev_open
iscsid: created NETLINK_ISCSI socket...
iscsid: InitiatorName==iqn.1997-01.net.verio:ut1-luna
iscsid: InitiatorAlias==iqn.1997-01.net.verio:ut1-luna
iscsid: InitiatorName=iqn.1997-01.net.verio:ut1-luna
iscsid: InitiatorAlias=iqn.1997-01.net.verio:ut1-luna
iscsid: in read_transports
iscsid: Adding new transport tcp
iscsid: found targetname iqn.2001-05.com.equallogic:
0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-base address
10.1.13.21 pers address 10.1.13.20 port 3260 pers port 3260 driver tcp
iface ipaddress 10.1.4.24 netdev default hwaddress default
iscsid: sync session [1][iqn.2001-05.com.equallogic:
0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-base,10.1.13.20.3260]
[default]

iscsid: in read_transports
iscsid: iface_for_each_iface found iface0
iscsid: looking for iface conf /etc/iscsi/ifaces/iface0
iscsid: updated 'iface.transport_name', 'tcp' => 'tcp'
iscsid: updated 'iface.net_ifacename', 'default' => 'eth0'
iscsid: rec read looking for config file /etc/iscsi/nodes/iqn.
2001-05.com.equallogic:0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-
base/10.1.13.20,3260.
iscsid: rec read looking for config file /etc/iscsi/nodes/iqn.
2001-05.com.equallogic:0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-
base/10.1.13.20,3260,1/default.
iscsid: Could not stat /etc/iscsi/nodes/iqn.2001-05.com.equallogic:
0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-base/10.1.13.20,3260,1/
default err 2.
iscsid: Could not read data from db. Using default and currently
negotiated values

iscsid: updating defaults from '/etc/iscsi/iscsid.conf'
iscsid: updated
'discovery.sendtargets.iscsi.MaxRecvDataSegmentLength', '32768' =>
'262144'
iscsid: updated 'node.startup', 'manual' => 'manual'
iscsid: updated 'node.session.timeo.replacement_timeout', '120' =>
'120'
iscsid: updated 'node.conn[0].timeo.login_timeout', '15' => '15'
iscsid: updated 'node.conn[0].timeo.logout_timeout', '15' => '15'
iscsid: updated 'node.conn[0].timeo.noop_out_interval', '10' => '10'
iscsid: updated 'node.conn[0].timeo.noop_out_timeout', '15' => '15'
iscsid: updated 'node.session.iscsi.InitialR2T', 'No' => 'No'
iscsid: updated 'node.session.iscsi.ImmediateData', 'Yes' => 'Yes'
iscsid: updated 'node.session.iscsi.FirstBurstLength', '262144' =>
'262144'
iscsid: updated 'node.session.iscsi.MaxBurstLength', '16776192' =>
'16776192'
iscsid: updated 'node.conn[0].iscsi.MaxRecvDataSegmentLength',
'131072' => '262144'
iscsid: match session [iqn.2001-05.com.equallogic:
0-8a0906-4c0233602-7fbfb1cde0a4759d-dl.ut1-eris-base,10.1.13.20,3260]
[ tcp,default,10.1.4.24]
iscsid: to [iqn.2001-05.com.equallogic:
0-8a0906-4c0233602-7fbfb1cde0a4759d-