Search results

This seems to work. Thanks alot for all your feedback on this.

Agreed, I will test as soon as I have a moment.

This shows current login timeout: iscsiadm -m node -p 172.16.123.111:3260 | grep 'login_timeout' This sets the timeout: iscsiadm -m node -p 172.16.123.111:3260 --op=update --name=node.conn[0].timeo.login_timeout --value=5 So perhaps setting the timeout lower before attempting login will help...

Maybe I'm missing something, but your suggestion seems to still result in the same errors on our test platform. When a new iscsi storage location is saved, the web interface hangs for a while and then gives the alert: "500 read timeout". Even though adding the location seems to have failed...

We had issues adding iscsi targets with multiple subnets where one of the subnets was not connectable from the proxmox server: root@debian:~# iscsiadm --mode discovery --type sendtargets --portal 172.16.123.111 172.16.124.1:3260,1 iqn.2011-07.local.wpps:std.drbd0 172.16.123.111:3260,1...

Thanks Tom, Update seems to have resolved the issue.

Hi, After creating an OpenVz CT with Veth I can ping the host and other vms on the same host, but nothing beyond the host. If I ssh from the host into the CT the network starts to work as expected, and continues to work until it is restarted. vps-wpps-01:~# cat /etc/network/interfaces #...