connection timeout(596)

punjprateek

Member
Jul 26, 2021
71
1
13
31
India
Hi Guys,

I am having NFS storage mounted in cluster as well as on normal node, but i am not able to see the VM Disk when i try to access through GUI or API i get a response of connection timeout(596) from gui as well as api. but when i search through pvesm list <storage> it shows me all the VM Disk. on the cluster i am on 7.2-11 an on seperate node i am on 7.3-6

Code:
proxmox-ve: 7.3-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-8
pve-kernel-5.15: 7.3-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-6
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.2-7
pve-firmware: 3.6-4
pve-ha-manager: 3.5.1
pve-i18n: 2.8-3
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
 

Attachments

  • Screenshot_46.png
    Screenshot_46.png
    50.2 KB · Views: 25
Actually, we've got tons of them all the time.
# tail -f /var/log/pveproxy/access.log | grep -v " 200 "
- root@pam [16/04/2025:18:48:07 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:48:19 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:48:19 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 500 -
- root@pam [16/04/2025:18:48:19 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- [16/04/2025:18:48:25 +0200] "GET /api2/json/nodes/pve-node01/qemu/713/config HTTP/1.1" 401 -
- [16/04/2025:18:48:25 +0200] "GET /api2/json/nodes/pve-node01/qemu/713/pending HTTP/1.1" 401 -
- root@pam [16/04/2025:18:48:41 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:48:42 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 500 -
- [16/04/2025:18:48:53 +0200] "POST /api2/json/access/ticket HTTP/1.1" 596 -
- [16/04/2025:18:48:53 +0200] "GET /api2/json/nodes/pve-node01/qemu/214/pending HTTP/1.1" 401 -
- [16/04/2025:18:48:53 +0200] "GET /api2/json/nodes/pve-node01/qemu/214/config HTTP/1.1" 401 -
- root@pam [16/04/2025:18:49:04 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:49:04 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:49:04 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:49:05 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:49:17 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- root@pam [16/04/2025:18:49:29 +0200] "GET /api2/json/nodes/pve-node01/storage HTTP/1.1" 596 -
- [16/04/2025:18:49:30 +0200] "GET /api2/json/nodes/pve-node01/qemu/1209/config HTTP/1.1" 401 -
- [16/04/2025:18:49:30 +0200] "GET /api2/json/nodes/pve-node01/qemu/1209/pending HTTP/1.1" 401 -