iscsi on el5 5.2 session hung

2009-07-24 Thread Joris
For some time i've been fighting with the manually logged in iscsi- session. It is impossible to remove this manually. I've restarted the iscsi server but even when stopped this session is visible with iscsiadm -m session So far i've found that under /sys/class/iscsi_... there are various indic

[ bug ? ] open-iscsi 868 chap on el5 ( Centos 5.3 and RedHat 5.2 )

2009-07-24 Thread Joris
ug reports regarding so any reference is welcome. For now the only correlation i've found is the open-iscsi version used which is ...-868 Attempts to compile the ...-871 tarball were unsuccessfull. This is not the no-brainer as the README sugg

Re: open-iscsi 868 chap on el5 ( Centos 5.3 and RedHat 5.2 )

2009-07-25 Thread Joris
de.conn[0].iscsi.IFMarker = No node.conn[0].iscsi.OFMarker = No # END RECORD On 24 jul, 18:22, Mike Christie wrote: > On 07/24/2009 03:42 AM, Joris wrote: > > > Hello, > > > I'm new to iscsi and ran into an authentication error with errocode > > 02/01 (target).

Re: open-iscsi 868 chap on el5 ( Centos 5.3 and RedHat 5.2 )

2009-07-28 Thread Joris
used to at first. Selectively commenting the usernames en passwords in the iscsid.conf file was key to the success for mounting the iscsi-target. Joris On 27 jul, 23:29, Mike Christie wrote: > On 07/24/2009 01:05 PM, Joris wrote: > > > Hi Mike, > > > In the meantime i've ki

Re: open-iscsi 868 chap on el5 ( Centos 5.3 and RedHat 5.2 )

2009-07-28 Thread Joris
error from /var/log/messages is at the bottom On 27 jul, 23:29, Mike Christie wrote: > On 07/24/2009 01:05 PM, Joris wrote: > > > Hi Mike, > > > In the meantime i've kind of got it to work but i feel like acting > > blind. > > > I've not followed an

Re: open-iscsi 868 chap on el5 ( Centos 5.3 and RedHat 5.2 )

2009-07-28 Thread Joris
Hi Mike, Thanks for the follow-up. On 27 jul, 23:29, Mike Christie wrote: > On 07/24/2009 01:05 PM, Joris wrote: > > > Hi Mike, > > > In the meantime i've kind of got it to work but i feel like acting > > blind. > > > I've not followed an