Hi Friedrich,
> Thanks! Just FYI, there is also a more convenient public-inbox instance for browsing our mailing lists [1]. Great, thanks for pointing me towards this page! > So if I understand correctly, after applying only your hostname patch on > top of an up-to-date libpve-storage-perl, you are still seeing the > "connection lost" entries on the iSCSI target? Can you double-check the > version of libpve-storage-perl (e.g. using `pveversion -v | grep > libpve-storage`) on top of which you applied your hostname patch? Could > you post the (anonymized) output of `iscsiadm -m node` and `iscsiadm -m > session` on nodes 1-4 and 5? For clarity, the connection lost entries no longer occur after applying my patch on all previously mentioned PVE stacks as well as within 9.01 which I recently upgraded to. Current environment is proxmox1 - patched, proxmox2 - default. I will show icsiadm output on a "good" proxmox1 vs "bad" proxmox2. 12345 is a placeholder for domain, IP addresses irrelevant and made up. I will leave my proxmox2 node unpatched in case we need any more information. #Version sanity check root@proxmox1:~# pveversion -v | grep 'libpve-storage\|pve-manager' pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2) libpve-storage-perl: 9.0.13 root@proxmox2:~# pveversion -v | grep 'libpve-storage\|pve-manager' pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2) libpve-storage-perl: 9.0.13 #proxmox1 iscsiadm root@proxmox1:~# iscsiadm -m node nas.12345.com:3260,4294967295 iqn.2024-01.com.12345.vm-stor nas.12345.com:3260,4294967295 iqn.2025-06.com.12345.ssd-vm-stor root@proxmox1:~# iscsiadm -m session tcp: [1] 192.168.1.10:3260,1 iqn.2024-01.com.12345.vm-stor (non-flash) tcp: [2] 192.168.1.10:3260,1 iqn.2025-06.com.12345.ssd-vm-stor (non-flash) #proxmox2 icsiadm root@proxmox2:~# iscsiadm -m node nas.12345.com:3260,4294967295 iqn.2024-01.com.12345.vm-stor nas.12345.com:3260,4294967295 iqn.2025-06.com.12345.ssd-vm-stor root@proxmox2:~# iscsiadm -m session tcp: [1] 192.168.1.10:3260,1 iqn.2025-06.com.12345.ssd-vm-stor (non-flash) tcp: [2] 192.168.1.10:3260,1 iqn.2024-01.com.12345.vm-stor (non-flash) #BEFORE PATCH journalctl -xeu pvestatd on proxmox1 9.01- constantly repeating: Nov 10 16:56:32 proxmox1 pvestatd[1245435]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2024-01.com.12345.vm-stor --login' failed: exit code 15 Nov 10 16:56:39 proxmox1 pvestatd[1245435]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2025-06.com.12345.ssd-vm-stor --login' failed: exit code 15 Nov 10 16:56:39 proxmox1 pvestatd[1245435]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2024-01.com.12345.vm-stor --login' failed: exit code 15 Nov 10 16:56:50 proxmox1 pvestatd[1245435]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2025-06.com.12345.ssd-vm-stor --login' failed: exit code 15 Nov 10 16:56:51 proxmox1 pvestatd[1245435]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2024-01.com.12345.vm-stor --login' failed: exit code 15 #AFTER PATCH journalctl -xeu pvestatd on proxmox1 9.01: [Service started successfully several minutes ago as expected, no errors like above] #journalctl -xeu pvestatd with no patch on proxmox2 - constantly repeating: Nov 10 17:12:42 proxmox2 pvestatd[1153]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2025-06.com.12345.ssd-vm-stor --login' failed: exit code 15 Nov 10 17:12:45 proxmox2 pvestatd[1153]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2024-01.com.12345.vm-stor --login' failed: exit code 15 Nov 10 17:12:52 proxmox2 pvestatd[1153]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2025-06.com.12345.ssd-vm-stor --login' failed: exit code 15 Nov 10 17:12:54 proxmox2 pvestatd[1153]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2024-01.com.12345.vm-stor --login' failed: exit code 15 Regards, Stelios Vailakakis _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
