Can't connect to GUI after update & restart

N

nemgreen

New Member
Dec 31, 2023
3
0
1
I updated my pve 8.1 and then rebooted as new kernel packages had been installed.
I can't now connect to the PVE web interface!

I can ssh to the pve ip address (192.168.1.128)

Both "curl -k https://127.0.0.1:8006" and "curl -k https://192.168.1.128:8006" return a similar message

curl: (7) Failed to connect to 127.0.0.1 port 8006 after 0 ms: Couldn't connect to server

Code: 
ps -ef | grep pve
root        1156       1  0 14:36 ?        00:00:01 /usr/sbin/pvefw-logger
root        1182       1  0 14:36 ?        00:00:00 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock
root       12185   11520  0 18:50 pts/0    00:00:00 grep pve

What should I check next?

Thanks
 
Code: 
systemctl | grep pve

  etc-pve.mount                                                                            loaded active     mounted   /etc/pve
  pve-cluster.service                                                                      loaded active     running   The Proxmox VE cluster filesystem
● pve-firewall.service                                                                     loaded failed     failed    Proxmox VE firewall
● pve-guests.service                                                                       loaded failed     failed    PVE guests
● pve-ha-crm.service                                                                       loaded failed     failed    PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service                                                                       loaded failed     failed    PVE Local HA Resource Manager Daemon
  pve-lxc-syscalld.service                                                                 loaded active     running   Proxmox VE LXC Syscall Daemon
  pve-query-machine-capabilities.service                                                   loaded active     exited    PVE Query Machine Capabilities
● pvebanner.service                                                                        loaded failed     failed    Proxmox VE Login Banner
● pvedaemon.service                                                                        loaded failed     failed    PVE API Daemon
  pvefw-logger.service                                                                     loaded active     running   Proxmox VE firewall logger
  pvenetcommit.service                                                                     loaded active     exited    Commit Proxmox VE network changes
● pveproxy.service                                                                         loaded failed     failed    PVE API Proxy Server
● pvescheduler.service                                                                     loaded failed     failed    Proxmox VE scheduler
● pvestatd.service                                                                         loaded failed     failed    PVE Status Daemon
  dev-pve-swap.swap                                                                        loaded active     active    /dev/pve/swap
  pve-storage.target                                                                       loaded active     active    PVE Storage Target
  pve-daily-update.timer                                                                   loaded active     waiting   Daily PVE download activities

Code: 
journalctl -b0

Mar 17 14:36:37 hppms kernel: Linux version 6.8.12-8-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREE>
Mar 17 14:36:37 hppms kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.12-8-pve root=/dev/mapper/pve-root ro quiet
Mar 17 14:36:37 hppms kernel: KERNEL supported cpus:
Mar 17 14:36:37 hppms kernel:   Intel GenuineIntel
Mar 17 14:36:37 hppms kernel:   AMD AuthenticAMD
Mar 17 14:36:37 hppms kernel:   Hygon HygonGenuine
Mar 17 14:36:37 hppms kernel:   Centaur CentaurHauls
Mar 17 14:36:37 hppms kernel:   zhaoxin   Shanghai
Mar 17 14:36:37 hppms kernel: BIOS-provided physical RAM map:
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000997ff] usable
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x0000000000099800-0x0000000000099bff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000f1de3fff] usable
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x00000000f1de4000-0x00000000f1dedfff] ACPI data
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x00000000f1dee000-0x00000000f7ffffff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fee0ffff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
Mar 17 14:36:37 hppms kernel: BIOS-e820: [mem 0x0000000100000000-0x000000040bffefff] usable
Mar 17 14:36:37 hppms kernel: NX (Execute Disable) protection: active
Mar 17 14:36:37 hppms kernel: APIC: Static calls initialized
Mar 17 14:36:37 hppms kernel: SMBIOS 2.7 present.
Mar 17 14:36:37 hppms kernel: DMI: HP ProLiant MicroServer Gen8, BIOS J06 11/02/2015
Mar 17 14:36:37 hppms kernel: tsc: Fast TSC calibration using PIT
Mar 17 14:36:37 hppms kernel: tsc: Detected 2394.494 MHz processor
Mar 17 14:36:37 hppms kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 17 14:36:37 hppms kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 17 14:36:37 hppms kernel: last_pfn = 0x40bfff max_arch_pfn = 0x400000000
Mar 17 14:36:37 hppms kernel: MTRR map: 4 entries (3 fixed + 1 variable; max 23), built from 10 variable MTRRs
Mar 17 14:36:37 hppms kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Mar 17 14:36:37 hppms kernel: last_pfn = 0xf1de4 max_arch_pfn = 0x400000000
Mar 17 14:36:37 hppms kernel: found SMP MP-table at [mem 0x000f4f80-0x000f4f8f]
Mar 17 14:36:37 hppms kernel: RAMDISK: [mem 0x30ae5000-0x34569fff]
Mar 17 14:36:37 hppms kernel: ACPI: Early table checksum verification disabled
Mar 17 14:36:37 hppms kernel: ACPI: RSDP 0x00000000000F4F00 000024 (v02 HP    )
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20230628/tbfadt-564)
Mar 17 14:36:37 hppms kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20230628/tbfadt-564)
Mar 17 14:36:37 hppms kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20230628/tbfadt-669)
Mar 17 14:36:37 hppms kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20230628/tbfadt-669)
Mar 17 14:36:37 hppms kernel: ACPI: DSDT 0x00000000F1DE6640 001C1A (v01 HP     DSDT     00000001 INTL 20030228)
Mar 17 14:36:37 hppms kernel: ACPI: FACS 0x00000000F1DE4140 000040
Mar 17 14:36:37 hppms kernel: ACPI: FACS 0x00000000F1DE4140 000040
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: ACPI: MCFG 0x00000000F1DE4200 00003C (v01 HP     ProLiant 00000001      00000000)
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: ACPI: APIC 0x00000000F1DE4580 000252 (v01 HP     ProLiant 00000002      00000000)
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: [81B blob data]
Mar 17 14:36:37 hppms kernel: ACPI: FFFF 0x00000000F1DE63C0 00002D (v01 HP     ProLiant 00000001      00000000)
 
As you can see from the first output, most of your PVE services have failed to start.

You can further investigate by running these commands against the services that failed:
systemctl status <service-name>
journalctl -u <service-name> --no-pager
journalctl -u <service-name> -n 50
systemctl show <service-name> --property=ExecMainStatus
systemctl status <service-name> | grep -i "failed"
systemctl list-dependencies <service-name>
systemctl list-units --failed

As for your second output, it is not very useful. There are hundreds if not thousands of lines that correspond to your latest boot sequence. Interesting stuff starts around the middle. However, please try to analyze it yourself first. Read the lines, there may be human-readable useful information there.

You should also check whether you have free space on your OS disk: df -h


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
I reran the update from the CLI, removed an old kernel package, rebooted, and it started ok.

Thanks for the help - I know a bit more now!
 
You must log in or register to reply here.
Top Bottom