Cannot access webgui - proxy logs assertion errors related to cargo/miniz_oxide & hyper

[Warren Head]

Hi there,

I have a fresh installation of (tried both) proxmox backup server v3.2 (also tried v3.1), running on a teenie tiny system, meant as a backup (pbs2) of my other backup server (pbs1).
The pbs2 system seems to operate fine, but since I cannot access the webgui, it isn't running any backups yet.
When I try to access the webgui from a different system, I first get the warning about the self-signed certificate. After approving accessing that, the browser shows me this error:

Secure Connection Failed​

An error occurred during a connection to pbs2.test.lan:8007.

• The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
• Please contact the website owners to inform them of this problem.

Via ssh I can access the sytem. From other issues mentioned on this forum, I followed the potential solution to reinstall these packages: proxmox-backup-server and proxmox-widget-toolkit, but those didn't fix it.
Then I noticed this in the journal of service proxmox-backup-proxy:

Jun 06 12:39:07 pbs2 proxmox-backup-[833]: Jun 0� ��:��:0� pbs2 proxmox-backup-proxy[833]: service is ready
Jun 06 12:39:07 pbs2 systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Jun 06 12:50:31 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: bits <= ((1u32 << len) - 1u32)', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:686:9
Jun 06 12:50:31 pbs2 proxmox-backup-proxy[833]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jun 06 12:50:31 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: bits <= ((1u32 << len) - 1u32)', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:686:9
Jun 06 12:50:31 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: bits <= ((1u32 << len) - 1u32)', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:686:9
Jun 06 12:50:32 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: bits <= ((1u32 << len) - 1u32)', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:686:9
Jun 06 12:50:32 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: bits <= ((1u32 << len) - 1u32)', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:686:9
Jun 06 12:50:32 pbs2 proxmox-backup-proxy[833]: thread 'tokio-runtime-worker' panicked at 'assertion failed: code < MAX_HUFF_SYMBOLS_2', /usr/share/cargo/registry/miniz_oxide-0.7.1/src/deflate/core.rs:1179:13

Github link to miniz_oxide:
https://github.com/Frommi/miniz_oxide/blob/0.7.1/miniz_oxide/src/deflate/core.rs

Followed by:

Jun 06 14:35:44 pbs2 proxmox-backup-proxy[23249]: thread 'tokio-runtime-worker' panicked at 'slice index starts at 94743947124312 but ends at 0', /usr/share/cargo/registry/hyper-0.14.27/src/proto/h1/role.rs:232:38
Jun 06 14:35:44 pbs2 proxmox-backup-proxy[23249]: thread 'tokio-runtime-worker' panicked at 'slice index starts at 94743947124312 but ends at 0', /usr/share/cargo/registry/hyper-0.14.27/src/proto/h1/role.rs:232:38
Jun 06 14:35:52 pbs2 proxmox-backup-proxy[23249]: thread 'tokio-runtime-worker' panicked at 'range end index 94743947096944 out of range for slice of length 502', /usr/share/cargo/registry/hyper-0.14.27/src/proto/h1/role.rs:232:38
Jun 06 14:35:52 pbs2 proxmox-backup-proxy[23249]: thread 'tokio-runtime-worker' panicked at 'range end index 94743947094736 out of range for slice of length 502', /usr/share/cargo/registry/hyper-0.14.27/src/proto/h1/role.rs:232:38

Github link to hyper:
https://github.com/hyperium/hyper/blob/0.14.x/src/proto/h1/role.rs

Since I don't have these errors on my pbs1 system, I am curious whether it could be due to the different processor.
This pbs2 I am setting up has an AMD E-350. It is 64-bit though, so as far as hardware requirements go, I think that should be suitable?
Or are there more cpu flags required that this system is without?

Otherwise, this could be a software bug related to cargo, but that is beyond me at the moment.
Still, since I cannot yet use this system for backups, I am open for suggestions for testing all sorts of things out.

I have run memtest from the installer and that completes succesfully.
System information:
lshw -class cpu

  *-cpu                     
       description: CPU
       product: AMD E-350 Processor
       vendor: Advanced Micro Devices [AMD]
       physical id: 4
       bus info: cpu@0
       version: 20.1.0
       serial: To Be Filled By O.E.M.
       slot: CPU 1
       size: 1601MHz
       width: 64 bits
       clock: 100MHz
       capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate vmmcall arat npt lbrv svm_lock nrip_save pausefilter cpufreq
       configuration: cores=2 enabledcores=2 microcode=83886118

 

[Warren Head]

Because of the errors shown by the libraries, I wanted to install cargo to be able to run their module and unittests.
But I noticed I could not install rust (with the default installer from the rust-lang website), because it failed another checksum on a file download.
So seemingly rust related.

To get more information, I have installed both Debian 12 and Openmediavault and noticed that the system could run those fine.
Everytime I would again reinstall proxmox-backup-server (using different usb sticks and ports even), proxmox would be steadfast in showing a white webpage with the above mentioned errors.

This made me curious whether the proxmox kernel was the important difference between the setups/systems.

To test that out, I installed debian 12 again and on that installed proxmox-backup-server. Curiously, I could this time both use the proxmox-default-kernel and access the web gui without errors. (and install rust)
The only change then currently is the fact that I am now not running on zfs root, which has my preference, but I am using a single ext4 disk as root since I had to use the debian 12 installer. Could that really be a reason for the strange errors I mentioned in my first post?


With more time, I am planning to try and chroot the current debian12 + proxmox to running on a zfs pool and hopefully the error shall not return.