After Upgrade to 1.7: ISCSI Connection Errors

nasenmann72

Renowned Member
Dec 9, 2008
71
2
73
Germany, Saarland
Hi,

after upgrading our two node PVE Cluster to 1.7, I get iSCSI connection errors while trying to connect to the openfiler targets:

Code:
Dec  5 01:51:25 asterix kernel: connection5:0: detected conn error (1020)
Dec  5 01:51:26 asterix iscsid: conn 0 login rejected: initiator error - target not found (02/03)
Dec  5 01:51:27 asterix proxwww[3959]: 500 Can't connect to 127.0.0.1:50000 (connect: Connection refused)
Dec  5 01:51:28 asterix kernel: connection5:0: detected conn error (1020)
Dec  5 01:51:29 asterix iscsid: conn 0 login rejected: initiator error - target not found (02/03)
Dec  5 01:51:31 asterix kernel: connection5:0: detected conn error (1020)
Dec  5 01:51:32 asterix proxwww[4051]: 500 Can't connect to 127.0.0.1:50000 (connect: Connection refused)
Dec  5 01:51:32 asterix iscsid: conn 0 login rejected: initiator error - target not found (02/03)
Dec  5 01:51:34 asterix kernel: connection5:0: detected conn error (1020)
An 'iscsiadm -m discovery -t sendtargets -p 10.10.99.20' lists all the targets:

Code:
asterix:~# iscsiadm  -m discovery -t sendtargets -p 10.10.99.20
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-telefonstatistik
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-wks-martin
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-buchhaltung
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-dbs
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-srv-bes
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target_srv_fs2
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-vm-wks
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target_srv_cholerik
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target_srv_fs2
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-srv-baan
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-telefonstatistik
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-srv-bes
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-vm-wks
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target_srv_cholerik
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-srv-gutemine
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-dbs
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-srv-gutemine
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-srv-baan
192.168.111.5:3260,1 iqn.2006-01.com.openfiler:target-wks-martin
10.10.99.20:3260,1 iqn.2006-01.com.openfiler:target-buchhaltung
Thanks in advance to any help!
 
Hi,

I've found a solution, thanks to guillermo!
http://forum.proxmox.com/threads/5249-iscsi-error-after-upgrade-proxmox-1.6-to-1.7

On openfiler I changed the /etc/sysconfig/iscsi-target from
Code:
MEM_SIZE=1048576
LISTEN_ADDR=""
to

Code:
MEM_SIZE=1048576
LISTEN_ADDR="10.10.99.20"

Then

/etc/init.d/iscsi-target restart

Et voila, the Proxmox nodes could access the iSCSI targets again.

But I still do not understand why this happend after upgrade to 1.7. What changed in Proxmox, that caused this problem?
 
defaut timeout of iscsiadm login is 60sec, so maybe it's too long for proxmox.

you can try to modify the file:
/usr/share/perl5/PVE/Storage.pm

sub iscsi_login

Code:
 my $cmd = [$ISCSIADM, '--mode', 'node', '--portal', $portal,
                   '--targetname',  $target, '--login'];

change to

Code:
 my $cmd = [$ISCSIADM, '--mode', 'node', '--portal', $portal,
                   '--targetname',  $target, '--login -T  recv-login-rsp-timeout=5'];

and after, do a "/etc/init.d/pvedaemon restart"



But, it's clearly of missconfig of your iscsi san target. Each ip of the target (portal ip group) in response of the discovery must be accessible from the initiator.
 
That is true spirit :
"it's clearly of missconfig of your iscsi san target. Each ip of the target (portal ip group) in response of the discovery must be accessible from the initiator."
But if for example if some element ( route, switch, nic) in one net crash, then proxmox can not access to it and it should try other portal that the discovery gave to it.
 
Now, my system is in production, so i can not do test. But what i can tell you spirit, is until solved the configuration in the OPENFILER, always i reset the open-iscsi and the configuration was in automatic i could reproduce the error, the same that nasenmann72. The system try to connect with the fallen portal and after give the error, it can not try other portal.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!