[SOLVED] [HELP] Issue after an update v7 to v8 on a HP Gen8

mitch55

New Member
Jul 4, 2024
7
0
1
Hi,

Someone could help me?

I use Proxmox on a HP microserver Gen 8.
I have made an update v7 to v8.

After some errors (I have tried to resolve), now I can't access to the interface localhost:8086 (I have a white screen).

Through SSH, I can't do anything : every action I can do is aborded. : Resolved

After the update, the issue might be caused by this (I think).

Now, I see 2 possibilities :

-) Someone could help me to resolve my problem ;
-) Or, I recover my files (vm) and reinstall proxmox via USB (but I knwo how to recover my files and which files...)

Thanks for your helps and your answers.

*Edit : My VM work !!
 

Attachments

  • 1720115320933.png
    1720115320933.png
    6.7 KB · Views: 17
  • 1720115344549.png
    1720115344549.png
    67.4 KB · Views: 13
  • 1720115767927.png
    1720115767927.png
    221.3 KB · Views: 17
  • 1720124340172.png
    1720124340172.png
    19.2 KB · Views: 15
Last edited:
Hi,
Could someone help me?

I can't access to the Proxmox interface.

With 192.168.1.190:8086, just a white screen appears.
 
Hi,

With 192.168.1.190:8086, just a white screen appears.
what does that mean? I guess you mean with your web browser? What is the exact error messages that gives?
Did you ensure to connect using HTTPS?

Since you have access via SSH, please post the output of (in codetags!): systemctl status pveproxy

Also, have you looked at the system log (via journalctl -b) for potential messages that might be related to this?
 
what does that mean? I guess you mean with your web browser? What is the exact error messages that gives?
Did you ensure to connect using HTTPS?"

Yes, with my web browser. I tried with Chrome and Edge, and private navigation.
The adress I use is : "https://192.168.1.190:8006/" like before the update.

Code:
root@pve:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-07-05 10:58:07 CEST; 29min ago
    Process: 1133 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1135 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1137 (pveproxy)
      Tasks: 4 (limit: 18896)
     Memory: 190.5M
        CPU: 3.708s
     CGroup: /system.slice/pveproxy.service
             ├─1137 pveproxy
             ├─1138 "pveproxy worker"
             ├─1139 "pveproxy worker"
             └─1140 "pveproxy worker"

Jul 05 10:58:05 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Jul 05 10:58:07 pve pveproxy[1137]: starting server
Jul 05 10:58:07 pve pveproxy[1137]: starting 3 worker(s)
Jul 05 10:58:07 pve pveproxy[1137]: worker 1138 started
Jul 05 10:58:07 pve pveproxy[1137]: worker 1139 started
Jul 05 10:58:07 pve pveproxy[1137]: worker 1140 started
Jul 05 10:58:07 pve systemd[1]: Started pveproxy.service - PVE API Proxy Server.

Code:
root@pve:~# journalctl -b
Journal file /var/log/journal/ea301836bd924b318b1da277fa2396d2/system@80017d8f836c4ee18f32d99702cee693-0000000000000001-00061c6e324fbb6b.journal is truncated, ignoring file.
Jul 05 10:57:58 pve kernel: Linux version 6.8.8-2-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.>
Jul 05 10:57:58 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.8-2-pve root=/dev/mapper/pve-root ro intel_iommu=off quiet intel_i>
Jul 05 10:57:58 pve kernel: KERNEL supported cpus:
Jul 05 10:57:58 pve kernel:   Intel GenuineIntel
Jul 05 10:57:58 pve kernel:   AMD AuthenticAMD
Jul 05 10:57:58 pve kernel:   Hygon HygonGenuine
Jul 05 10:57:58 pve kernel:   Centaur CentaurHauls
Jul 05 10:57:58 pve kernel:   zhaoxin   Shanghai
Jul 05 10:57:58 pve kernel: BIOS-provided physical RAM map:
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009bbff] usable
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x000000000009bc00-0x000000000009bfff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000adde3fff] usable
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x00000000adde4000-0x00000000addedfff] ACPI data
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x00000000addee000-0x00000000bbffffff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fee0ffff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
Jul 05 10:57:58 pve kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000447ffefff] usable
Jul 05 10:57:58 pve kernel: NX (Execute Disable) protection: active
Jul 05 10:57:58 pve kernel: APIC: Static calls initialized
Jul 05 10:57:58 pve kernel: SMBIOS 2.7 present.
Jul 05 10:57:58 pve kernel: DMI: HP ProLiant MicroServer Gen8, BIOS J06 11/02/2015
Jul 05 10:57:58 pve kernel: tsc: Fast TSC calibration using PIT
Jul 05 10:57:58 pve kernel: tsc: Detected 3292.647 MHz processor
Jul 05 10:57:58 pve kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 05 10:57:58 pve kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 05 10:57:58 pve kernel: last_pfn = 0x447fff max_arch_pfn = 0x400000000
Jul 05 10:57:58 pve kernel: MTRR map: 4 entries (3 fixed + 1 variable; max 23), built from 10 variable MTRRs
Jul 05 10:57:58 pve kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Jul 05 10:57:58 pve kernel: last_pfn = 0xadde4 max_arch_pfn = 0x400000000
Jul 05 10:57:58 pve kernel: found SMP MP-table at [mem 0x000f4f80-0x000f4f8f]
Jul 05 10:57:58 pve kernel: RAMDISK: [mem 0x30ae5000-0x34569fff]
Jul 05 10:57:58 pve kernel: ACPI: Early table checksum verification disabled
Jul 05 10:57:58 pve kernel: ACPI: RSDP 0x00000000000F4F00 000024 (v02 HP    )
Jul 05 10:57:58 pve kernel: [81B blob data]
Jul 05 10:57:58 pve kernel: [81B blob data]
Jul 05 10:57:58 pve kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20230628/tbfadt-564)
Jul 05 10:57:58 pve kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20230628/tbfadt-564)
Jul 05 10:57:58 pve kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20230628/tbfadt-669)

Here you are.
 
Last edited:
There is something new: from my phone, I can get something but only in mobile version. As soon as I switch to "computer" version, I have an empty page (like on my PC).
 
Here's the solution :

Code:
apt install --reinstall pve-manager
apt install --reinstall proxmox-widget-toolkit
 

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!