ISCSI Error code 255

W

wizard3

Guest
Hello, I have a master and node server both running proxmox and in active sync. The problem is that the iscsi port is not discoverable on port 3260. I do not have any firewalls running, and the port is not active.

Both Master and Node are running the newest Proxmox version 1.5

When I try to add iscsi through proxmox I get the error described in this thread:
http://forum.proxmox.com/threads/3512-Not-being-able-to-add-ISCSI-target

This error code 255
Code:
Error: command '/usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260' failed with exit code 255
I tried starting iscsi through terminal:
------------------------------------------------
Master:
localhost:~# uname -a
Linux localhost 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux

localhost:/etc/init.d# iscsistart
iscsistart: transport class version 2.0-871. iscsid version 2.0-870
iscsistart: InitiatorName not set. Exiting iscsistart


-------------------------------------------------

Node:
serv:/# uname -a
Linux serv 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux

serv:/etc/init.d# iscsistart
iscsistart: transport class version 2.0-871. iscsid version 2.0-870
iscsistart: InitiatorName not set. Exiting iscsistart

( I tried manually installing some iscsitarget packages but still having some problems )
serv:/# /etc/init.d/iscsitarget start
Starting iSCSI enterprise target service: FATAL: Module iscsi_trgt not found.
failed - module is missing!

-----------------------------------------


Any help is greatly appreciated.

Thanks
 
What output do you get when you run the command manually:

Code:
 [FONT=&quot]/usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260[/FONT]

maybe 'iscsid' is not running?

# /etc/init.d/open-iscsi start

Note: You do not need an iscsi target server.
 
Code:
serv:~#  /usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: caught SIGINT, exiting...


Code:
serv:~# /etc/init.d/open-iscsi start
Starting iSCSI initiator service: iscsid
iSCSI daemon already running
 
serv:~#
 
Last edited by a moderator:
it's the proxmox slave node:

Code:
serv:~# uname -a
Linux serv 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux
serv:~#

The proxmox control panel is working fine. I installed from the 1.5 proxmox ISO. Just this iscsi is not working properly.
 
Master node has the same problems:
(installed from proxmox 1.5 ISO)

Code:
localhost:~#  /usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: connection login retries (reopen_max) 5 exceeded
Code:
localhost:~# uname -a
Linux localhost 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux
Code:
localhost:~# /etc/init.d/open-iscsi start
Starting iSCSI initiator service: iscsid
iSCSI daemon already running
 
localhost:~#


Could this be a problem with my storage devices not being ISCSI compatible?
 
Last edited by a moderator:
are you able to ping 10.0.0.3 ?
Yep

Code:
serv:~# uname -a
Linux serv 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux
serv:~# ping 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
64 bytes from xx.xxx.xxx.xxx: icmp_seq=1 ttl=255 time=0.772 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=2 ttl=255 time=1.75 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=3 ttl=255 time=1.71 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=4 ttl=255 time=1.41 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=5 ttl=255 time=1.55 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=6 ttl=255 time=2.15 ms
 
--- 10.0.0.3 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 0.772/1.560/2.155/0.422 ms
serv:~#
 
hmm...
I can see
localhost:/etc/init.d# iscsistart
iscsistart: transport class version 2.0-871. iscsid version 2.0-870
iscsistart: InitiatorName not set. Exiting iscsistart

it seems iscsi isn't properly configured if you don't have this file...

Code:
# cat /etc/iscsi/initiatorname.iscsi

you should get something like :
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator. The InitiatorName must be unique
## for each iSCSI initiator. Do NOT duplicate iSCSI InitiatorNames.
#InitiatorName=iqn.1993-08.org.debian:01:189b41993854
InitiatorName=iqn.1993-08.org.debian:neptune2
Code:
# dpkg -l | grep iscsi

you should get something like
ii open-iscsi 2.0.870~rc3-0.4 High performance, transport independent iSCS
 
Master Node:
Code:
localhost:~# uname -a 
Linux localhost 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux

localhost:~# cat /etc/iscsi/initiatorname.iscsi
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:1bfd1b578dca

localhost:~# dpkg -l | grep iscsi 
ii  open-iscsi                        2.0.870~rc3-0.4          High performance, transport independent iSCS

localhost:~#  /usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: caught SIGINT, exiting...
on the slave node I have similar results
Code:
serv:~# uname -a
Linux serv 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux

serv:~# cat /etc/iscsi/initiatorname.iscsi
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:4ee6f26e5b6d


serv:~# dpkg -l | grep iscsi
iF  iscsitarget                       0.4.16+svn162-3.1+lenny1 iSCSI Enterprise Target userland tools
ii  iscsitarget-source                0.4.16+svn162-3.1+lenny1 iSCSI Enterprise Target kernel module source
ii  open-iscsi                        2.0.870~rc3-0.4.1        High performance, transport independent iSCS

serv:~#  /usr/bin/iscsiadm --mode discovery --type sendtargets --portal 10.0.0.3:3260 
iscsiadm: connection to discovery address 10.0.0.3 failed
iscsiadm: caught SIGINT, exiting...
^^ I tried to apt-get install iscsitarget and iscsitarget-source on the slave node, but it did not fix the problem.
 
Last edited by a moderator:
just to be sure everything is well understood :
* your PVE's are iscsi initiators. (clients that connect to an iSCSI target)
* they must connect to an iSCSI target (a server providing LUN's)

that's why you don't need to install iscsitarget on your PVE's

some questions :
* what kind of iSCSI target do you have ?
* 10.10.0.3 is really the target's IP?
* can you paste an ifconfig -a of your 2 PVE's?
* try to telnet your target from your PVE with
Code:
telnet targetIP 3260
you should get :
Trying 10.10.0.2...
Connected to 10.10.0.2.
Escape character is '^]'.
CTRL-D to close...

if it doesn't work try from other machine that can access this IP range...to be sure the target is really accessible...
 

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!