communication failure (0) - Storage / Disks - 30 sec Timeout

Vel

Member
Oct 4, 2021
9
2
8
Dear all

I am trying to setup a Proxmox Backup Server. As soon as I open the "Storage / Disks" tab, the message "communication failure (0)" appears after about 30 seconds. The server has 90 disks installed. I assume that the listing takes too long and the web request falls into a default timeout of 30 seconds. Is there a solution for this problem?

1695015034821.png

Thanks and BR
 
mhmm yes most api calls from the gui have a 30 second timeout, but this is only a ui problem, it should work via the api/cli
but also with 90 disks, the call should not take over 30 seconds

how long does a

Code:
lsblk
take on the cli?
 
Dear Dominik

Thank you for the feedback.

That is instant (< 1 Sec.) there:

Code:
lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0 223.6G  0 disk
├─sda1    8:1    0  1007K  0 part
├─sda2    8:2    0     1G  0 part
└─sda3    8:3    0   222G  0 part
sdb       8:16   0 223.6G  0 disk
├─sdb1    8:17   0  1007K  0 part
├─sdb2    8:18   0     1G  0 part
└─sdb3    8:19   0   222G  0 part
sdc       8:32   0    20T  0 disk
sdd       8:48   0    20T  0 disk
sde       8:64   0    20T  0 disk
sdf       8:80   0    20T  0 disk
sdg       8:96   0    20T  0 disk
sdh       8:112  0    20T  0 disk
sdi       8:128  0    20T  0 disk
sdj       8:144  0    20T  0 disk
sdk       8:160  0    20T  0 disk
sdl       8:176  0    20T  0 disk
sdm       8:192  0    20T  0 disk
sdn       8:208  0    20T  0 disk
sdo       8:224  0    20T  0 disk
sdp       8:240  0    20T  0 disk
sdq      65:0    0    20T  0 disk
sdr      65:16   0    20T  0 disk
sds      65:32   0    20T  0 disk
sdt      65:48   0    20T  0 disk
sdu      65:64   0    20T  0 disk
sdv      65:80   0    20T  0 disk
sdw      65:96   0    20T  0 disk
sdx      65:112  0    20T  0 disk
sdy      65:128  0    20T  0 disk
sdz      65:144  0    20T  0 disk
sdaa     65:160  0    20T  0 disk
sdab     65:176  0    20T  0 disk
sdac     65:192  0    20T  0 disk
sdad     65:208  0    20T  0 disk
sdae     65:224  0    20T  0 disk
sdaf     65:240  0    20T  0 disk
sdag     66:0    0    20T  0 disk
sdah     66:16   0    20T  0 disk
sdai     66:32   0    20T  0 disk
sdaj     66:48   0    20T  0 disk
sdak     66:64   0    20T  0 disk
sdal     66:80   0    20T  0 disk
sdam     66:96   0    20T  0 disk
sdan     66:112  0    20T  0 disk
sdao     66:128  0    20T  0 disk
sdap     66:144  0    20T  0 disk
sdaq     66:160  0    20T  0 disk
sdar     66:176  0    20T  0 disk
sdas     66:192  0    20T  0 disk
sdat     66:208  0    20T  0 disk
sdau     66:224  0    20T  0 disk
sdav     66:240  0    20T  0 disk
sdaw     67:0    0    20T  0 disk
sdax     67:16   0    20T  0 disk
sday     67:32   0    20T  0 disk
sdaz     67:48   0    20T  0 disk
sdba     67:64   0    20T  0 disk
sdbb     67:80   0    20T  0 disk
sdbc     67:96   0    20T  0 disk
sdbd     67:112  0    20T  0 disk
sdbe     67:128  0    20T  0 disk
sdbf     67:144  0    20T  0 disk
sdbg     67:160  0    20T  0 disk
sdbh     67:176  0    20T  0 disk
sdbi     67:192  0    20T  0 disk
sdbj     67:208  0    20T  0 disk
sdbk     67:224  0    20T  0 disk
sdbl     67:240  0    20T  0 disk
sdbm     68:0    0    20T  0 disk
sdbn     68:16   0    20T  0 disk
sdbo     68:32   0    20T  0 disk
sdbp     68:48   0    20T  0 disk
sdbq     68:64   0    20T  0 disk
sdbr     68:80   0    20T  0 disk
sdbs     68:96   0    20T  0 disk
sdbt     68:112  0    20T  0 disk
sdbu     68:128  0    20T  0 disk
sdbv     68:144  0    20T  0 disk
sdbw     68:160  0    20T  0 disk
sdbx     68:176  0    20T  0 disk
sdby     68:192  0    20T  0 disk
sdbz     68:208  0    20T  0 disk
sdca     68:224  0    20T  0 disk
sdcb     68:240  0    20T  0 disk
sdcc     69:0    0    20T  0 disk
sdcd     69:16   0    20T  0 disk
sdce     69:32   0    20T  0 disk
sdcf     69:48   0    20T  0 disk
sdcg     69:64   0    20T  0 disk
sdch     69:80   0    20T  0 disk
sdci     69:96   0    20T  0 disk
sdcj     69:112  0    20T  0 disk
sdck     69:128  0    20T  0 disk
sdcl     69:144  0    20T  0 disk
sdcm     69:160  0    20T  0 disk
sdcn     69:176  0    20T  0 disk
nvme0n1 259:0    0    14T  0 disk
nvme1n1 259:1    0    14T  0 disk
nvme2n1 259:2    0    14T  0 disk
nvme3n1 259:3    0    14T  0 disk
 
ok, then it's probably an issue that the smartctl checks take too long..
you can open a bug report/feature request here: https://bugzilla.proxmox.com to increase the gui timeout but for that we have to know how long it takes in your case (that is on the large side of things)

can you do
Code:
time proxmox-backup-debug api get /nodes/localhost/disks/list

and post the last few lines of the output ?
 
Dear Dominik

Thank you very much, here is the output:

Code:
 time proxmox-backup-debug api get /nodes/localhost/disks/list
...
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ hdd       │   0 │ sds     │ 22000969973760 │ passed │ unused │ /dev/sds     │ ST22000NM000E              │            │     │ 5000c500.........│ SEAGATE │         │ 0x5000c500da...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ hdd       │   0 │ sdaa    │ 22000969973760 │ passed │ unused │ /dev/sdaa    │ ST22000NM000E              │            │     │ 5000c500.........│ SEAGATE │         │ 0x5000c500da...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   1 │ sdb     │   240057409536 │ passed │ zfs    │ /dev/sdb     │ SAMSUNG_MZ7L3240HCHQ-00A07 │            │   0 │ S663NS0W.........│ ATA     │      99 │ 0x5002538f33...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   1 │ sda     │   240057409536 │ passed │ zfs    │ /dev/sda     │ SAMSUNG_MZ7L3240HCHQ-00A07 │            │   0 │ S663NS0W.........│ ATA     │      99 │ 0x5002538f33...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   0 │ nvme3n1 │ 15362991415296 │ passed │ unused │ /dev/nvme3n1 │ SAMSUNG MZQL215THBLA-00A07 │            │     │ S6VANE0W.........│         │     100 │ eui.36564130...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   0 │ nvme2n1 │ 15362991415296 │ passed │ unused │ /dev/nvme2n1 │ SAMSUNG MZQL215THBLA-00A07 │            │     │ S6VANE0W.........│         │     100 │ eui.36564130...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   0 │ nvme1n1 │ 15362991415296 │ passed │ unused │ /dev/nvme1n1 │ SAMSUNG MZQL215THBLA-00A07 │            │     │ S6VANE0W.........│         │     100 │ eui.36564130...│
├───────────┼─────┼─────────┼────────────────┼────────┼────────┼──────────────┼────────────────────────────┼────────────┼─────┼─────────.........┼─────────┼─────────┼─────────────...┤
│ ssd       │   0 │ nvme0n1 │ 15362991415296 │ passed │ unused │ /dev/nvme0n1 │ SAMSUNG MZQL215THBLA-00A07 │            │     │ S6VANE0W.........│         │     100 │ eui.36564130...│
└───────────┴─────┴─────────┴────────────────┴────────┴────────┴──────────────┴────────────────────────────┴────────────┴─────┴──────────────────┴─────────┴─────────┴────────────────┘

real    0m37.433s
user    0m0.059s
sys     0m0.023s

Not much is missing for it to be displayed :)

I will create a bug report separately.
(EDIT: https://bugzilla.proxmox.com/show_bug.cgi?id=4961)

Thanks and BR
 

Attachments

  • Output.txt
    71 KB · Views: 1
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!