iscsid: can't create connection

Dmitry Melekhov

unread,

May 31, 2007, 12:50:58 AM5/31/07

to open-iscsi

Hello!

I want to run open iscsi with iet.
iet works OK with microsoft scsi initiator and with initiator included
to centos 4.

But open-scsi doesn't work.

iscsi_discovery 192.168.22.229
starting discovery to 192.168.22.229
Testing iser-login to target iqn.
2001-04.com.example:storage.disk2.sys1.xyz portal 192.168.22.229:3260
starting to test tcp-login to target iqn.
2001-04.com.example:storage.disk2.sys1.xyz portal 192.168.22.229:3260
discovered 1 targets at 192.168.22.229, connected to 0

I see in iscsd log:

iscsid: connected local port 55138 to 192.168.22.229:3260
iscsid: thread 0807172c delete: state 0
iscsid: deleting a scheduled/waiting thread!
iscsid: in kcreate_session
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: created new iSCSI session 12
iscsid: in kcreate_conn
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: expecting event 13, got 103, handling...
iscsid: in nlpayload_read
iscsid: received iferror -12
iscsid: returned -12
iscsid: can't create connection (115)
iscsid: in kdestroy_session
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: disconnecting conn 0x806f2a4, fd 6
iscsid: write_mgmt_rsp: rsp to fd 5
iscsid: thread 0807172c delete: state 2
iscsid: destroying session

what does it mean?
how can I fix this?

Thank you!

Mike Christie

unread,

May 31, 2007, 1:36:59 PM5/31/07

to open-...@googlegroups.com

Dmitry Melekhov wrote:
> Hello!
>
> I want to run open iscsi with iet.
> iet works OK with microsoft scsi initiator and with initiator included
> to centos 4.
>
> But open-scsi doesn't work.
>
> iscsi_discovery 192.168.22.229
> starting discovery to 192.168.22.229
> Testing iser-login to target iqn.
> 2001-04.com.example:storage.disk2.sys1.xyz portal 192.168.22.229:3260
> starting to test tcp-login to target iqn.
> 2001-04.com.example:storage.disk2.sys1.xyz portal 192.168.22.229:3260
> discovered 1 targets at 192.168.22.229, connected to 0
>

iscsi_discovery just does discovery and sets things up for iser or iscsi
over tcp/ip. After running that you need to login or set it up to log in
automatically when the service is started.

For example run:

iscsiadm -m node

to see what was found. Then run

iscsiadm -m node -L all

to login to all the nodes

Dmitry Melekhov

unread,

May 31, 2007, 11:56:49 PM5/31/07

to open-iscsi

On 31 май, 22:36, Mike Christie <micha...@cs.wisc.edu> wrote:
> For example run:
>
> iscsiadm -m node
>
> to see what was found. Then run
>
> iscsiadm -m node -L all
>
> to login to all the nodes

I can't login:

iscsiadm -m node -L all

Login session [192.168.22.229:3260 iqn.
2001-04.com.example:storage.disk2.sys1.xyz]
iscsiadm: Could not login session (err 9).

iscsiadm: initiator reported error (9 - internal error)

And I get the same error as with iscsi_discovery

scsi16 : iSCSI Initiator over TCP/IP
iscsi: couldn't create a new connection for session 15

So something is wrong in my configration or this is bug.
What can I do?

Mike Christie

unread,

Jun 1, 2007, 12:08:29 AM6/1/07

to open-...@googlegroups.com

Make sure you have the crc32c module built and loaded. Older versions
would fail and not print a error.

Dmitry Melekhov

unread,

Jun 1, 2007, 8:09:37 AM6/1/07

to open-iscsi

On 1 июн, 09:08, Mike Christie <micha...@cs.wisc.edu> wrote:

>
> Make sure you have the crc32c module built and loaded. Older versions
> would fail and not print a error.