[SOLVED] VMWARE ESXi storage connection dropped, now I can't reconnect it

[Curt Hall]

I connected to 3 vmware vsphere boxes. 1 dropped during a VM migration. I deleted the storage and now cannot re-add it. I get the below error:


create storage failed: (vim.fault.HostConnectFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '503 Service Unavailable', faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [] } (500)

The other 2 servers are still connected.

 

[Curt Hall]

Well, I tried it on one of the other VMWARE boxes and it did the exact same thing. I now only have one VMWARE box I can connect to, although I can't migrate any VM from any box.

 

[Curt Hall]

**Update**, after waiting 15 minutes I can rejoin the server now. What is going on here?

 

[cheiss]

Hi,

first, please provide the output of pveversion -v and apt-cache policy pve-esxi-import-tools, to get information what package versions you are on exactly.
Also you don't specify what ESXi version you are on, which could also be pretty relevant.

In any case, this might be related to rate-limited done by VMware. Have you tried some solution in the main thread, such as
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649926
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649242

In that thread, there is generally more of a discussion about this.

 

[Curt Hall]

Hi,

first, please provide the output of pveversion -v and apt-cache policy pve-esxi-import-tools, to get information what package versions you are on exactly.
Also you don't specify what ESXi version you are on, which could also be pretty relevant.

In any case, this might be related to rate-limited done by VMware. Have you tried some solution in the main thread, such as
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649926
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649242

In that thread, there is generally more of a discussion about this.

root@proxmoxVDI1:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.11-5-pve)
pve-manager: 8.1.10 (running version: 8.1.10/4b06efb5db453f29)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-8
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5: 6.5.13-3
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-5-pve-signed: 6.5.11-5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
pve-kernel-5.15.131-1-pve: 5.15.131-2
pve-kernel-5.15.126-1-pve: 5.15.126-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.3
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.5
libpve-cluster-perl: 8.0.5
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.6
libpve-network-perl: 0.9.6
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.5-1
proxmox-backup-file-restore: 3.1.5-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.5
pve-cluster: 8.0.5
pve-container: 5.0.9
pve-docs: 8.1.5
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.1.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve1

 

[Curt Hall]

Hi,

first, please provide the output of pveversion -v and apt-cache policy pve-esxi-import-tools, to get information what package versions you are on exactly.
Also you don't specify what ESXi version you are on, which could also be pretty relevant.

In any case, this might be related to rate-limited done by VMware. Have you tried some solution in the main thread, such as
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649926
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649242

In that thread, there is generally more of a discussion about this.

pve-esxi-import-tools:
Installed: 0.6.1
Candidate: 0.6.1
Version table:
*** 0.6.1 500
500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages
100 /var/lib/dpkg/status
0.6.0 500
500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages
0.5.0 500
500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages

 

[Curt Hall]

Hi,

first, please provide the output of pveversion -v and apt-cache policy pve-esxi-import-tools, to get information what package versions you are on exactly.
Also you don't specify what ESXi version you are on, which could also be pretty relevant.

In any case, this might be related to rate-limited done by VMware. Have you tried some solution in the main thread, such as
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649926
- https://forum.proxmox.com/threads/n...sxi-based-virtual-machines.144023/post-649242

In that thread, there is generally more of a discussion about this.

Hypervisor: VMware ESXi, 7.0.3, 19193900

 

[sheldor]

We're having the same issue after installing the newest updates to our host. We have already added the soap parameters and maxSessionCount is set to 0.

 

[Curt Hall]

We're having the same issue after installing the newest updates to our host. We have already added the soap parameters and maxSessionCount is set to 0.

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. But your solution makes sense also.

 

[Curt Hall]

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. So clearly there is more bug fixes that are being fixed we will wait for a stable version of the tool. its not even version1.0.0 yet.

 

[sheldor]

Our issue was just resolved. After adding the soap parameters we had to run /etc/init.d/hostd restart to get ESXi to recognize the new config.xml.

Running /etc/init.d/hostd restart just fixed our issue.