On Mar 26, 10:52 am, Mike Christie <[EMAIL PROTECTED]> wrote:
> CymBa wrote:
> > Mar 25 01:34:52 srv1 iscsid: connect failed (113)
> > Mar 25 01:34:56 srv1 iscsid: connect failed (113)
> > Mar 25 01:34:56 srv1 kernel: Loading iSCSI transport class v2.0-724.
> > Mar 25 01:34:56 srv1 kernel: iscsi: registered transport (tcp)
> > Mar 25 01:34:56 srv1 kernel: iscsi: registered transport (iser)
> > Mar 25 01:35:00 srv1 iscsid: connect failed (113)
> > Mar 25 01:35:04 srv1 iscsid: connect failed (113)
> > :
> > I'm not sure whats happening here. The network is being loaded before
> > iscsi so it should be able to access the target.
>
> It looks like you are hitting the problem Hannes 
> described.http://groups.google.com/group/open-iscsi/browse_thread/thread/d1290f...
>
> Are you using static IP addresses? Try increasing:
> node.session.initial_login_retry_max
>
> in /etc/iscsi/iscsi.conf. Try something like 30 or 60.

Yes I'm using static IP's. I'm not sure if DHCP can be an option.

I read that thread and changed the value in /etc/iscsi/iscsid.conf
to :
:
# during startup or if the network is not ready at that time.

node.session.initial_login_retry_max = 60

################################
:
After the reboot the volume still wasn't loading.

Here are the results from the last couple reboots in /var/log/message
I'm noting however that even though I set the retry max to 60 I'm
still only seeing 4 "connect failed"'s per reboot session in the logs.
I also note that for the reboot at 23:18:13 it seems that it might
have worked.

Mar 26 23:13:00  iscsid: connect failed (113)
Mar 26 23:13:00 kernel: iscsi: registered transport (tcp)
Mar 26 23:13:00 kernel: iscsi: registered transport (iser)
Mar 26 23:13:04 iscsid: connect failed (113)
Mar 26 23:13:08 iscsid: connect failed (113)
Mar 26 23:18:12 iscsid: iSCSI logger with pid=3209 started!
Mar 26 23:18:13 iscsid: transport class version 2.0-724. iscsid
version 2.0-865
Mar 26 23:18:13 iscsid: iSCSI daemon with pid=3210 started!
Mar 26 23:18:13 iscsid: connection1:0 is operational now
Mar 26 23:20:32 iscsid: connect failed (113)
Mar 26 23:20:36 kernel: iscsi: registered transport (tcp)
Mar 26 23:20:36 kernel: iscsi: registered transport (iser)
Mar 26 23:20:36 iscsid: connect failed (113)
Mar 26 23:20:40 iscsid: connect failed (113)
Mar 26 23:20:44 iscsid: connect failed (113)
Mar 27 00:10:26 iscsid: connect failed (113)
Mar 27 00:10:30 iscsid: connect failed (113)
Mar 27 00:10:30 kernel: iscsi: registered transport (tcp)
Mar 27 00:10:30 kernel: iscsi: registered transport (iser)
Mar 27 00:10:34 iscsid: connect failed (113)
Mar 27 00:10:38 iscsid: connect failed (113)

Its almost as if the daemon wasn't reading the new values in the
iscsid.conf file but the perms look fine:

-rw-r----- 1 root root 7996 Mar 26 23:18 iscsid.conf

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

Reply via email to