I've recently been playing around with a four node cluster using a NFS mount for VM storage.
Debian version: 8.5 Proxmox version: 4.2.11 The NFS mounts on all four nodes without any issue and I can read/write files via ssh. However, from the webui I can only load status details from node 2 and node 4. For example this page loads perfectly: https://localhost:8006/api2/json/nodes/proxmox-2-1/storage/VM-Storage/status But this page times out with a 596 response code: https://localhost:8006/api2/json/nodes/proxmox-2-2/storage/VM-Storage/status >From the /var/log/pveproxy/access.log file from the failing node (proxmox2-2) it responds with a 500 response code: 172.16.0.240 - root@pam [19/Jun/2016:20:42:43 -0700] "GET /api2/json/nodes/proxmox-2-2/storage/VM-Storage/content?content=backup HTTP/1.1" 500 - 172.16.0.240 - root@pam [19/Jun/2016:20:42:44 -0700] "GET /api2/json/nodes/proxmox-2-2/storage/VM-Storage/status HTTP/1.1" 500 - But writes work from the same node. root@proxmox-2-2:~# cd /mnt/pve/VM-Storage/ root@proxmox-2-2:/mnt/pve/VM-Storage# touch test.txt root@proxmox-2-2:/mnt/pve/VM-Storage# ls -l test.txt -rw-r--r-- 1 root root 0 Jun 19 20:44 test.txt I can't seem to find any failures in the logs, would there be any suggestions on the best way to trace where this is failing? I've tried with strace on the worker processes, but nothing useful seems to be coming up. Rory _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
