wofferl / proxmox-backup-arm64

Script for building Proxmox Backup Server 3.x (Bookworm) for Armbian64
151 stars 12 forks source link

3.1.2-1: Dashboard -> Status loading all the time #42

Closed mhaluska closed 9 months ago

mhaluska commented 9 months ago

I just updated to version 3.1.2-1 and Dashboard -> Status is all the time with Loading... status. There is no error in logs.

image

HW: Rpi4 OS: RaspberryPi OS 12

Nov 30 21:01:16 zr-rpi1 systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Nov 30 21:01:16 zr-rpi1 proxmox-backup-[61295]: zr-rpi1 proxmox-backup-proxy[61295]: applied rrd journal (52 entries in 0.036 seconds)
Nov 30 21:01:16 zr-rpi1 proxmox-backup-[61295]: zr-rpi1 proxmox-backup-proxy[61295]: write rrd data back to disk
Nov 30 21:01:16 zr-rpi1 proxmox-backup-[61295]: zr-rpi1 proxmox-backup-proxy[61295]: starting rrd data sync
Nov 30 21:01:16 zr-rpi1 proxmox-backup-[61295]: zr-rpi1 proxmox-backup-proxy[61295]: rrd journal successfully committed (25 files in 0.046 seconds)
mhaluska commented 9 months ago

Revert to 3.0.4-1 and everything is fine:

image
wofferl commented 9 months ago

Unfortunately they changed the way they get the kernel version (https://github.com/proxmox/proxmox-backup/commit/487922752ba70a70f5f791e599ba8434b14c7f33) and now the status dashboard fails if the kernel name is not in there format, with the timestamp in () like:

6.5.11-6-pve (build@proxmox) #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-6 (2023-11-29T08:32Z)

I will fix this in the next version.

Meanwhile you can fix it manually by changing line 9353 to the following in /usr/share/javascript/proxmox-backup/js/proxmox-backup-gui.js.

  9352                 let kernel = data['current-kernel'];
  9353                 let buildDate = 'unknown'; //kernel.version.match(/\((.+)\)\s*$/) ?? 'unknown';
  9354                 return `${kernel.sysname} ${kernel.release} (${buildDate})`;
mhaluska commented 9 months ago

Thank you, I didn't find the right js file myself. Your fix helped. Thank you

wofferl commented 9 months ago

Bug fixed with 3.1.2-2

mhaluska commented 9 months ago

Awesome, thank you ;-)