communication failure (0) / Connection timed out (596)

[theOwnest]

proxmox 9.1.5 still problem

can I fix it by edit some configuration files?

 

[Chris]

proxmox 9.1.5 still problem

can I fix it by edit some configuration files?

Hi, what version of PBS are you running? There have been prefromance improvements to the group listing [0], which are included since version 4.1.

[0] https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=e59d33f4cede466d8b175bab2f292d6e4279c28c

 

[theOwnest]

Hi, what version of PBS are you running? There have been prefromance improvements to the group listing [0], which are included since version 4.1.

[0] https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=e59d33f4cede466d8b175bab2f292d6e4279c28c

I'm running PVE 9.1.5 but error same



but in console "ls" command displays content of folder

 

[Chris]

I'm running PVE 9.1.5 but error same

The PVE is only acting as the client here, you should check the version on the PBS.

 

[theOwnest]

The PVE is only acting as the client here, you should check the version on the PBS.

I'm not using PBS, I use storagebox on hetzner connected through smb/cifs

 

[Chris]

Ah, assumed this is to a PBS since the thread is specific to that. In that case you might check if your NAS storage is online and reachable, e.g. check the output of pvesm status

 

[theOwnest]

Ah, assumed this is to a PBS since the thread is specific to that. In that case you might check if your NAS storage is online and reachable, e.g. check the output of pvesm status

I wrote here because error same and there is no topic in pve branch…
StorageBox is online and reachable, I could get its content by ls in console, also I copy files there by cp

 

[mp.plusserver]

Hi All,

I stumbled over this faulty behavior today. We also have PBS servers running which already contain many backups. Our versions are quite recent:

$ pveversion
pve-manager/9.2.4/5e5ae681198514d4 (running kernel: 7.0.14-11-pve)

$ proxmox-backup-manager versions
proxmox-backup-server 4.2.3-1 running version: 4.2.1

Our PBS machines are using spinning disks with two SSDs as "special" meta data cache.

Since there is not much activity in the open bug I would like to ask if we can make changes on local files to get the function working again until a fix is released.

Thank You & kind regards,
Martin