StarWind Software

I have a 2 host Proxmox cluster and when rebooting a host I get this message from the rebooted host:-
Sep 19 19:49:45 pve-ruby iscsid[1467]: connect to 192.168.182.205:3260 failed (No route to host)

where 192.168.182.205 is the local VM running CVM Version 20250225.
followed by:-
Sep 19 19:49:55 pve-ruby iscsiadm[1439]: Login to [iface: default, target: iqn.2008-08.com.starwindsoftware:192.168.182.204-vmth-data, portal: 192.168.182.204,3260] successful.
Sep 19 19:49:55 pve-ruby systemd[1]: open-iscsi.service: Main process exited, code=exited, status=8/n/a
Sep 19 19:49:55 pve-ruby systemd[1]: open-iscsi.service: Failed with result 'exit-code'.

where 192.168.182.204 is the other host's VM running CVM Version 20250225.

The host continues and appears to come up and shared storage all works. Is this expected?

I also periodically get when doing disk operations:-
Sep 19 19:49:55 pve-ruby pve-ha-lrm[2440]: Plugin "PVE::Storage::Custom::StarLvmPlugin" is implementing an older storage API, an upgrade is recommended

and I assume a patch release will fix this at some stage in the future??

Greetings,

Those are normal. Thanks a lot for pointing those out.
The system expects iSCSI targets to be there on startup and sits there waiting for them (in vain )
The plugin thing is known too. My colleagues are working on it, I hope.

Ok thanks for the heads up.
Yeah it looks like it hangs when booting.
So would it be better to have a script that polls for iSCSI on it's local VM and then recreate the connection??

I think the local VM is not running when the service starts, so it can't poll.