/etc/pve: Transport endpoint is not connected

[adoII]

Hi,

I manually edited /etc/cluster/cluster.conf on a node and increased version number to get the cluster working.
After that I issued /etc/init.d/pve-cluster restart to remount /etc/pve

An error appeared saying something like "local cluster.conf version newer" and since that time I cannot mount /etc/pve anymore, not even readonly

I get this message:

san03:/var/lib/pve-cluster# /etc/init.d/pve-cluster start
Starting pve cluster filesystem : pve-clusterfuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected
[main] notice: exit proxmox configuration filesystem (-1)
 (warning).
san03:/var/lib/pve-cluster#

Local mount also does not work:

pmxcfs -d -f -l

...
[main] debug: memdb open '/var/lib/pve-cluster/config.db' successful (version = 0000000000000322) (memdb.c:518:memdb_open)
[main] notice: forcing local mode (althought cluster.conf exists) (pmxcfs.c:856:main)
fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected (pmxcfs.c:885:main)
[main] notice: exit proxmox configuration filesystem (-1) (pmxcfs.c:1008:main)

How can I remount /etc/pve ?
Any ideas ?
The node is in production and i cannot reboot

 

[adoII]

To answer the question myself:
I just had to umount -f /etc/pve before mounting, that was all

 

[dietmar]

An error appeared saying something like "local cluster.conf version newer" and since that time I cannot mount /etc/pve anymore, not even readonly

That means the the version number in /etc/cluster/cluster.conf is greater than the version in /etc/pve/cluster.conf?

 

[Chris Rivera]

service pve-cluster stop

then service pve-cluster start..... thats when i got the error about fuse not being able to mount to target


umount -f /etc/pve solved my issue..

thanks

 

[fat_kid]

Just in case anyone else stumbles across this post when looking into this. I had a similar issue where I could not restart pve-cluster. I kept getting this error:

root@vmh:/mnt# service pve-cluster restart
Restarting pve cluster filesystem: pve-clusterstart-stop-daemon: warning: failed to kill 4869: No such process
fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected
[main] notice: exit proxmox configuration filesystem (-1)
(warning).

And if I tried to unmount I got this:

root@vmh:/mnt# ls -la /etc/pve
ls: cannot access /etc/pve: Transport endpoint is not connected
root@vmh:/mnt# umount -f /etc/pve
umount2: Device or resource busy
umount: /etc/pve: device is busy.
  (In some cases useful info about processes that use
  the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
root@vmh:/mnt# fusermount -u /etc/pve
fusermount: failed to unmount /etc/pve: Device or resource busy

Here's what worked for me, a lazy unmount:

root@vmh:/mnt# umount -l /etc/pve

After that, I was able to restart the pve-cluster service without any issues.