[SOLVED] no webinterface

[vWolf]

I can´t access the webinterface after we had a power outage.. Idk what the problem is, as I´m fairly new to Proxmox. I have 3VMs 1 Win Server 2019 as DC and DNS, one Terminal Server and one Backup Server. None of those came up with the restart of Proxmox.
Also these are the newest logs:
-- Journal begins at Sun 2022-06-12 02:23:32 CEST, ends at Tue 2022-06-21 15:58:42 CEST. --
Jun 21 09:11:39 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:39 pve pmxcfs[1099]: fuse: mountpoint is not empty
Jun 21 09:11:39 pve pmxcfs[1099]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:39 pve pmxcfs[1099]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1099]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve pmxcfs[1099]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1099]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:39 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Jun 21 09:11:39 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:39 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:39 pve pmxcfs[1169]: fuse: mountpoint is not empty
Jun 21 09:11:39 pve pmxcfs[1169]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:39 pve pmxcfs[1169]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1169]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve pmxcfs[1169]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1169]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:39 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1170]: fuse: mountpoint is not empty
Jun 21 09:11:40 pve pmxcfs[1170]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:40 pve pmxcfs[1170]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1170]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve pmxcfs[1170]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1170]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:40 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1171]: fuse: mountpoint is not empty
Jun 21 09:11:40 pve pmxcfs[1171]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:40 pve pmxcfs[1171]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1171]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve pmxcfs[1171]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1171]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:40 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1172]: fuse: mountpoint is not empty

and in the directory /etc/host and /etc/network/interfaces the right IP is set..

 

[shrdlicka]

Hi,

take a look in the /etc/pve directory. According to the errors you are getting there is some data in there. If you find something put it somewhere else and try rebooting Proxmox .

 

[Stoiko Ivanov]

fuse: mountpoint is not empty

In case you still remember (I assume you resolved the issue) - what was inside /etc/pve when you triggered the issue?