iscsi authentication error from centos to a synology iscsi target.
Tim Fotherby
Mike Christie
> I'm having a problem getting an iscsi target connected to a CentOS 5.7
> server. This is my second time having this similar issue.
> Before I solved the problem by reinstalling ipv6 settings. It's saying that
> it can't authenticate to the Synology iscsi target that I have setup with
> CHAP, and a simple username and password.
> Please see below the errors
>
>
> config:
> node.session.auth.authmethod = CHAP
> node.session.auth.username = target1
> node.session.auth.password = abc123abc123
>
> commands ran:
> iscsiadm -m discovery -t sendtargets -p 192.168.214.199
> iscsiadm -m node --op delete -T iqn.2000-01.com.synology:rackstation.name1
> iscsiadm -m node --op delete -T iqn.2000-01.com.synology:rackstation.name2
> iscsiadm -m node --op delete -T iqn.2000-01.com.synology:rackstation.name3
>
> [root@fish ~]# service iscsid restart
> Stopping iSCSI daemon:
> Starting iSCSI daemon: [ OK ]
> [ OK ]
You do not need to do this. The command below will do it for you.
>
>
> [root@fish ~]# service iscsi restart
> iscsiadm: No matching sessions found
> Stopping iSCSI daemon:
> iscsid is stopped [ OK ]
> Starting iSCSI daemon: [ OK ]
> [ OK ]
> Setting up iSCSI targets: Logging in to [iface: default, target:
> iqn.2000-01.com.synology:rackstation.name, portal: 192.168.214.199,3260]
> iscsiadm: Could not login to [iface: default, target:
> iqn.2000-01.com.synology:rackstation.name, portal: 192.168.214.199,3260].
> iscsiadm: initiator reported error (24 - iSCSI login failed due to
> authorization failure)
Is there some more info in /var/log/messages? Something from "iscsid"
indicating a login error value?
For that target is the chap info what you wrote above? Do
iscsiadm -m node -T iqn.2000-01.com.synology:rackstation.name -p
192.168.214.199
to see.
> iscsiadm: Could not log into all portals
> [ OK ]
>
> dmesg output:
> Loading iSCSI transport class v2.0-871.
> cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
> iscsi: registered transport (cxgb3i)
> Broadcom NetXtreme II CNIC Driver cnic v2.0.1 (Oct 01, 2009)
> Broadcom NetXtreme II iSCSI Driver bnx2i v2.0.1e (June 22, 2009)
> iscsi: registered transport (bnx2i)
> iscsi: registered transport (tcp)
> iscsi: registered transport (iser)
> scsi20 : iSCSI Initiator over TCP/IP
> BUG: warning at drivers/scsi/libiscsi2.c:465/iscsi_complete_task()
> (Tainted: G )
When you did the restart, were there sessions already running? Were you
also running IO to those sessions? This trace is bad because it
indicates a double free. I am not sure if it is related to the login
error above though. Could you do:
echo 1 > /sys/module/libiscsi2/paramters/debug_libiscsi
echo 1 > /sys/module/libiscsi_tcp/paramters/debug_libiscsi_tcp
echo 1 > /sys/module/iscsi_tcp/paramters/debug_iscsi_tcp
Then rerun your test?
Tim Fotherby
> When you did the restart, were there sessions already running? Were you
> also running IO to those sessions? This trace is bad because it
> indicates a double free. I am not sure if it is related to the login
> error above though. Could you do:
>
> echo 1 > /sys/module/libiscsi2/paramters/debug_libiscsi
> echo 1 > /sys/module/libiscsi_tcp/paramters/debug_libiscsi_tcp
> echo 1 > /sys/module/iscsi_tcp/paramters/debug_iscsi_tcp
>
> Then rerun your test?
>
I ended up fixing this by removing all the scanned targets and readding them.
Apparently if you change the config to chap from default config after you've
added targets then you have to delete them, re-add them, then restart the iscsi
service.
Mike Christie
By config you must meant the iscsid.conf settings. iscsid.conf settings
are the ones used for the initial discovery session and used to create
the per portal iscsi node db. If you have already discovered
targets/portals then to update specific portals settings you need to run
iscsiadm -m node -T target -p ip -o update -n name-of-setting -v value
Or you can set them in iscsid.conf then rerun the discovery command.
That will overwrite the current node db with settings based on
iscsid.conf values.
But even if you did not do this, you should not hit that OOPS/BUG you
were hitting in the kernel.
Guillaume
The problem arise when I activate data CRC on the Syno. I have no problem with header CRC.
It seems that the data digest parameter is not supported by RH & CentOS.
Guillaume
I did have the same problem from Redhat EL5 & CentOS. The same target
is not problematic with Ubuntu and Win7 initiators.
I discovered that my problem come from the DATA CRC32C. When I
deactivate the data digest on the Syno, the Redhat can login to the
target.
Mike Christie
> Hello,
>
> I did have the same problem from Redhat EL5 & CentOS. The same target
> is not problematic with Ubuntu and Win7 initiators.
> I discovered that my problem come from the DATA CRC32C. When I
> deactivate the data digest on the Syno, the Redhat can login to the
> target.
> I have no problem with header CRC.
> Could you verify if your target use Data CRC ?
different error though. You should not get that stack trace below. If
you guys are getting a stack trace like below I will try to do some more
debugging. I did not see that below when I tested here.
Guillaume
Le mercredi 25 avril 2012 06:15:55 UTC+2, Mike Christie a écrit :
Data digests are not supported in centos/rhel 5. You should get a
different error though. You should not get that stack trace below. If
you guys are getting a stack trace like below I will try to do some more
debugging. I did not see that below when I tested here.
I don't have the stack trace but whe I activate data digest on the target I have the error :
iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure)
(sorry for the double post yesterday, I did not see my post in the thread so I posted another one)
Mike Christie
>
>
> Le mercredi 25 avril 2012 06:15:55 UTC+2, Mike Christie a �crit :
>>
>>
>> Data digests are not supported in centos/rhel 5. You should get a
>> different error though. You should not get that stack trace below. If
>> you guys are getting a stack trace like below I will try to do some more
>> debugging. I did not see that below when I tested here.
>>
>>
>>
> Ok.
>
> I don't have the stack trace but whe I activate data digest on the target I
> have the error :
> iscsiadm: initiator reported error (24 - iSCSI login failed due to
> authorization failure)
>
> Is data digest supported in RedHat EL6 or CentOS 6 ? I will have to
> reinstall the server this summer on new hardware soo if it's ok I will
> install one of these.
>
> (sorry for the double post yesterday, I did not see my post in the thread
> so I posted another one)