[SOLVED] PVE tries to connect to already deleted ISCSI target

A

Accept

New Member
May 5, 2024
3
0
1
Germany
Hello,

a couple of days ago I deleted a ISCSI target configured (via GUI) on my PVE and created a new one.

Now, after examining the logs the PVE tries continuously to connect to this (old) specific target and logically fails with that.

PVE 8.2.2

/etc/pve/storage.cfg:
Code: 
dir: local
        path /var/lib/vz
        content vztmpl,backup,iso

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

cifs: syn-smb-1
        path /mnt/pve/syn-smb-1
        server 10.0.3.30
        share home
        content snippets,iso,rootdir,backup,images,vztmpl
        prune-backups keep-all=1
        username pve

# new one
iscsi: syn-iscsi-0
        portal 10.0.3.30
        target iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe
        content none

lvm: syn-lvm-0
        vgname syn-iscsi
        base syn-iscsi-0:0.0.1.scsi-36001405301708cdd0e11d47a7db3abd6
        content rootdir,images
        saferemove 1
        shared 1

lvm: syn-lvm-1
        vgname syn-iscsi2
        base syn-iscsi-0:0.0.2.scsi-360014050b896e89d0ee4d41ecd8506d9
        content rootdir,images
        saferemove 1
        shared 1

As far as I can estimate this, there is no storage misconfigured.

Logs:
Code: 
May 05 20:53:51 pve iscsid[7232]: connection-1:0 cannot make a connection to fe80::211:32ff:fef5:b94:3260 (-1,22)
May 05 20:53:51 pve iscsid[7232]: connect to 10.0.0.30:3260 failed (Connection refused)
May 05 20:53:56 pve iscsid[7232]: connection-1:0 cannot make a connection to fe80::211:32ff:fef5:b94:3260 (-1,22)
May 05 20:53:56 pve iscsid[7232]: connect to 10.0.0.30:3260 failed (Connection refused)
May 05 20:53:59 pve iscsid[7232]: connection-1:0 cannot make a connection to fe80::211:32ff:fef5:b94:3260 (-1,22)
May 05 20:53:59 pve iscsid[7232]: connect to 10.0.0.30:3260 failed (Connection refused)
May 05 20:54:02 pve iscsid[7232]: connection-1:0 cannot make a connection to fe80::211:32ff:fef5:b94:3260 (-1,22)
May 05 20:54:02 pve iscsid[7232]: connect to 10.0.0.30:3260 failed (Connection refused)

10.0.0.30 is the "old" storage device and should not be used for ISCSI-connections anymore.

iscsiadm -m session -P 1
Code: 
Target: iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe (non-flash)
        Current Portal: 10.0.3.30:3260,1
        Persistent Portal: 10.0.3.30:3260,1
                **********
                Interface:
                **********
                Iface Name: default
                Iface Transport: tcp
                Iface Initiatorname: iqn.1993-08.org.debian:01:d34f76eea0c9
                Iface IPaddress: 10.0.3.20
                Iface HWaddress: default
                Iface Netdev: default
                SID: 1
                iSCSI Connection State: LOGGED IN
                iSCSI Session State: LOGGED_IN
                Internal iscsid Session State: NO CHANGE

Any suggestions how to prevent PVE from connecting to the 10.0.0.30 device?

What I've already tried: reboot :D

Love u guys!

Phil
 
Last edited:
Hello! :)

Return of "iscsiadm -m node":

Code: 
10.0.0.30:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe
10.0.3.30:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe
[fe80::211:32ff:fef5:b94]:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe

This is kinda weird. I would like to remove the unused target.

I tried to logout with the command
Code: 
iscsiadm --mode node --targetname iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe --portal 10.0.0.30:3260 --logout
but get
Code: 
iscsiadm: No matching sessions found

It makes sense because the system cannot logout a connection which is not established.

Best regards,

Phil
 
Last edited:
Have you tried
Code: 
iscsiadm remove discovery-address 10.0.0.30:3260

Note: Never done this before
 
Hello and thanks for your reply!

I tried the command you posted but it It doesn't work:

iscsiadm remove discovery-address 10.0.0.30:3260
Code: 
Try `iscsiadm --help' for more information.

I've searched for a command to delete discovery addresses and tried this:

iscsiadm -m discoverydb -t sendtargets -p 10.0.0.30:3260 -o delete


That worked for me. The session list is cleaned up now.

iscsiadm -m node:
Code: 
10.0.3.30:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.a9ad618a0fe

Additionally the node summary stats are available again. That's awesome!

Thank you very much for your assist. It would have taken me a long time to figure that out for myself.

Phil
 
Unfortunately this didn't work for me. I got the below returned when running the command. Seems the IP address:3260 is causing issues.

root@pve:~# iscsiadm -m discoverydb -t sendtargets -p <IPAddress>:3260 -o delete
[B]iscsiadm: Discovery record [<IPAddress>,3260] not found.[/B]

My Error Log still shows:
Apr 25 07:01:00 pve iscsid[18010]: connect to <IPAddress>:3260 failed (Connection refused)

**IP is hidden with <IPAddress>, real IP was used in the commands
 
Last edited:
Hi @confidentcyber.org , welcome to the forum.
Please review the posts above yours and provide similar information and command output as original poster. It would be best to do so in your own thread.

Are you trying to hide your IP address, or did you actually run the command with <IPAddress> in it?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
Hi @confidentcyber.org , welcome to the forum.
Please review the posts above yours and provide similar information and command output as original poster. It would be best to do so in your own thread.

Are you trying to hide your IP address, or did you actually run the command with <IPAddress> in it?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Just obfuscating the IP in the command. I posted to this thread as the error was the same, but the solution did not work for me.
 
confidentcyber.org said:
Just obfuscating the IP in the command
Click to expand...
No offense meant - we get posters with all levels of experience here. Just a guess, but it seems like you may have configured PVE on a publicly accessible IP. Obfuscating a private range IP usually isn't necessary or particularly helpful.

confidentcyber.org said:
I posted to this thread as the error was the same
Click to expand...
A good place to start is by sharing the actual error message you're seeing. Sometimes small details in the output can help others identify the issue more quickly.

There are plenty of situations where similar errors stem from entirely different causes, so including the specific troubleshooting commands you've run, as mentioned earlier in this thread, alongside the full error will go a long way in helping folks assist you more effectively.

Cheers.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom