Re: iscsiadm: No records found!

2017-08-08 Thread vinodmghodke
Thanks Sushanth . after lot of google, your tips works... Thanks 
again... heartly thankfull ...




On Wednesday, 24 July 2013 18:51:58 UTC+5:30, Sushanth Bhat wrote:

> Hi Nithin
>
> Are you still facing the same problem?
>
> Try commenting all the lines in open filer machine "*/etc/initiator.deny*
> ".
>
> And also check* iptables* you could just stop or edit *"# service 
> iptables stop"*
>
> Reboot the machine.
>
> On Thursday, 14 February 2008 23:14:30 UTC+5:30, nithink...@gmail.com 
> wrote:
>>
>>
>>
>> On Feb 14, 10:23 pm, Mike Christie  wrote: 
>> > nithinkumar...@gmail.com wrote: 
>> > > Apart from this i ll show you the iscsid.conf 
>> > 
>> > >  node.startup = automatic 
>> > > node.session.auth.authmethod = CHAP 
>> > > node.session.auth.username = xx 
>> > > node.session.auth.password = xxx 
>> > > discovery.sendtargets.auth.authmethod = CHAP 
>> > > discovery.sendtargets.auth.username =  
>> > > discovery.sendtargets.auth.password = xxx 
>> > 
>> > Maybe we should start with a really simple setup. If you remove all the 
>> > CHAP settings from the target and initiator, does it work? If you then 
>> I have removed all the CHAP setting from both the initiator as well as 
>> target. 
>> Still the same problem. 
>> > do one way chap does it work?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.


[Bug?] Stray session in sysfs

2017-08-08 Thread Frank Ritsema
During changes in the iscsi SAN layout the initiator got confused, holding 
on to a session in RAM while this session should not exists. 

"iscsiadm -m session" shows 1 session. Trying to delete the record for it 
fails because the session is in use
The sessions persists, no matter what I try, even if all nodes, ifaces, 
portals etc are deleted from the persistent DB. The only place there is a 
reference to the session is in sysfs, which i cannot delete.

Trying to log it out with the daemon running fails because the session 
keeps trying to log in to a target with wrong credentials (which i for some 
reason cannot adjust with --op=update and node.session.auth.* variables; no 
error, they just don't get saved)
Trying to log out of the session with the daemon off returns a 'no records 
found'.

Every time the daemon starts it sees the device in sysfs and happily starts 
trying to connect.
As far as I am aware there is no way to force delete a broken session, 
besides by rebooting. This is something I prefer not to do though.
Is there something I'm missing?

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.