pbs: error fetching datastores - 500 Can't connect to

Gius_00

Member
Nov 23, 2019
2
0
21
25
Hello,
I've same issue after upgrading Proxmox from 7.4 to 8.2.4.
I can't connect to PBS

Error:
Jun 29 17:32:19 pvestatd[1677]: PBS-NAS: error fetching datastores - 500 Can't connect to 10.200.1.4:8007

Ping:
root@IT1:~# ping 10.200.1.4
PING 10.200.1.4 (10.200.1.4) 56(84) bytes of data.
64 bytes from 10.200.1.4: icmp_seq=1 ttl=63 time=52.8 ms
64 bytes from 10.200.1.4: icmp_seq=2 ttl=63 time=52.7 ms
64 bytes from 10.200.1.4: icmp_seq=3 ttl=63 time=53.0 ms
64 bytes from 10.200.1.4: icmp_seq=4 ttl=63 time=53.7 ms
^C
--- 10.200.1.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 52.723/53.067/53.718/0.392 ms

Telnet:
root@IT1:~# telnet 10.200.1.4 8007
Trying 10.200.1.4...
Connected to 10.200.1.4.
Escape character is '^]'.
^CConnection closed by foreign host.

storage config:
root@IT1:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,rootdir,images,backup,vztmpl,snippets
prune-backups keep-all=1
shared 0

zfspool: local-zfs
pool rpool/data
content images,rootdir
sparse 1

lvmthin: NVME1_LVMThin
thinpool NVME1_LVMThin
vgname NVME1_LVMThin
content images,rootdir
nodes IT1

pbs: PBS-NAS
datastore BackupVM-NAS
server 10.200.1.4
content backup
fingerprint 92:77:41:2d:10:cc:b3:f8:c5:9a:f6:3d:89:f6:74:e0:e3:89:c0:ba:04:df:9c:aa:77:11:2c:e9:47:92:c4:85
prune-backups keep-last=5
username root@pam

PVESM Status:
root@IT1:~# pvesm status
PBS-NAS: error fetching datastores - 500 Can't connect to 10.200.1.4:8007
Name Type Status Total Used Available %
NVME1_LVMThin lvmthin active 980070400 271577507 708492892 27.71%
PBS-NAS pbs inactive 0 0 0 0.00%
local dir active 398180480 232962688 165217792 58.51%
local-zfs zfspool active 241641276 76423428 165217848 31.63%

Other proxmox work correctly with same pbs:
root@PVE:~# pvesm status
Name Type Status Total Used Available %
PBS-NAS pbs active 10268351744 1855138688 8412672384 18.07%
 
well, are the PBS services running on the host with that IP?