[RESOLVED] Error when accessing VMWare storage

Oct 2, 2024
3
0
1
Tampa, Florida
We are getting an error when trying to connect to VMWare storage: failed to spawn fuse mount, process exited with status 256 (500)

This is only occuring on on one of 8 Proxmox nodes. The other nodes can access the storage fine and this particular one worked previously.

Some output from journalctl:

Sep 18 06:26:07 pvm05 esxi-folder-fus[3096]: pvm05 esxi-folder-fuse[3096]: esxi fuse mount ready
Sep 18 06:26:09 pvm05 systemd[1]: Started pve-esxi-fuse-vm\x2ddev03.scope.
Sep 18 06:26:12 pvm05 esxi-folder-fus[3118]: pvm05 esxi-folder-fuse[3118]: esxi fuse mount ready
Sep 18 06:26:12 pvm05 systemd[1]: Started pve-esxi-fuse-vm\x2ddev15.scope.
Sep 18 06:26:13 pvm05 esxi-folder-fus[3132]: pvm05 esxi-folder-fuse[3132]: esxi fuse mount ready
Oct 02 04:29:11 pvm05 systemd[1]: pve-esxi-fuse-vm\x2ddev01.scope: Deactivated successfully.
Oct 02 04:29:11 pvm05 systemd[1]: pve-esxi-fuse-vm\x2ddev01.scope: Consumed 1h 28min 33.805s CPU time.
Oct 02 04:29:14 pvm05 systemd[1]: Started pve-esxi-fuse-vm\x2ddev01.scope.
Oct 02 04:29:17 pvm05 esxi-folder-fus[3635606]: pvm05 esxi-folder-fuse[3635606]: esxi fuse mount ready
Oct 02 04:30:40 pvm05 esxi-folder-fus[3635606]: pvm05 esxi-folder-fuse[3635606]: STAT ON VERSION?
Oct 02 04:30:42 pvm05 esxi-folder-fus[3635606]: pvm05 esxi-folder-fuse[3635606]: STAT ON VERSION?
Oct 02 04:36:38 pvm05 systemd[1]: pve-esxi-fuse-vm\x2ddev01.scope: Deactivated successfully.
Oct 02 04:36:44 pvm05 systemd[1]: Started pve-esxi-fuse-vm\x2ddev01.scope.
Oct 02 04:36:47 pvm05 esxi-folder-fus[3637043]: pvm05 esxi-folder-fuse[3637043]: esxi fuse mount ready
Oct 02 12:56:21 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:23 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:24 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:26 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:27 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:29 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:30 pvm05 pvedaemon[1786196]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:34 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:34 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:34 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:34 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:34 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:35 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:56:35 pvm05 pvedaemon[1571730]: failed to spawn fuse mount, process exited with status 256
Oct 02 12:59:49 pvm05 esxi-folder-fus[2773]: pvm05 esxi-folder-fuse[2773]: STAT ON VERSION?
Oct 02 13:00:04 pvm05 esxi-folder-fus[2773]: pvm05 esxi-folder-fuse[2773]: STAT ON VERSION?

Any suggestions appreciated.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!