pvesm list 'VM-Storage' works on all nodes and gives a list like this: VM-Storage:100/vm-100-disk-1.qcow2 qcow2 274877906944 100 VM-Storage:100/vm-100-disk-2.qcow2 qcow2 536870912000 100 VM-Storage:101/vm-101-disk-1.qcow2 qcow2 274877906944 101 VM-Storage:102/vm-102-disk-1.qcow2 qcow2 274877906944 102
showmount --exports IP_ADDR also works on all nodes and gives the expected export list from the NFS server where VM-Storage exists. It seems kind of odd that this works on the first and third node, but not the second and fourth. Does /api2/json/nodes/proxmox-2-2/storage/VM-Storage/status get handed off to a backend process that may not be responding correctly? One item of note is that I hadn't noticed earlier is that this doesn't appear to be limited to NFS, if I attempt to hit https://localhost:8006/api2/json/nodes/proxmox-2-2/storage/local/status I see the same behavior on nodes 2 and 4. On 19 June 2016 at 21:12, Dietmar Maurer <[email protected]> wrote: > > 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. > > Does the following command work on all nodes? > > # pvesm list 'VM-Storage' > > Maybe you run into a timeout? > > Also make sure the following command works from all nodes: > > # showmount --exports <nfs-server> > > _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
