On Sep 18, 8:54 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> Jeff Q wrote
>
> > ----------------------------------------------
>
> > with the following repeating pretty frequently:
> > ----------------------------------------------
> > Sep 17 13:09:56 afsbackup kernel: ping timeout of 5 secs expired, last
> > rx 4316722054, last ping 4316721118, now 4316724554
> > Sep 17 13:09:56 afsbackup kernel:  connection6:0: iscsi: detected conn
> > error (1011)
> > Sep 17 13:09:56 afsbackup iscsid: semop up failed 22
> > ----------------------------------------------
>
> > I've read that the "semop failed" can be resolved if i were to enable
> > CHAP authentication and include the log-in information in the /etc/
> > iscsi/iscsi.conf file, but I'm trying to take CHAP out of the picture.
>
> You can ignore the semop error. It is not related.
>
> > Any suggestions?  Would the newer version of open-iscsi solve the
>
> You could just turn off nops. Use these values.
>
> node.conn[0].timeo.noop_out_interval = 0
> node.conn[0].timeo.noop_out_timeout = 0
>

I tried this, and it doesn't seem to fix the problem.  When I'm logged
into both devices, an "fdisk -l" only shows the more recent of the
two. Is there anything I can do to get open-iscsi compiled on SLES10?


> A newer version might help. Some reporters have reported a change we did
> to the nop code has fixed the problem. You could try the open-iscsi.org
> code, but I do not think it compiles on SLES10.
>
> > issue?  If so, any idea when SLES10 will have an RPM, or the version
> > will be compilable?
>
> > Thanks for any help you can give me.
> > -Jeff
>
>
--~--~---------~--~----~------------~-------~--~----~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to