Web interface no longer works - access via SSH still possible - data lost?

[iceweasel]

Hello all,

I can no longer access the Proxmox web interface. Accordingly, LXC containers and VMs no longer work. (Screenshot)

Access via SSH is still possible.

I had previously performed updates of Proxmox directly, as I do at regular intervals. Then did a complete restart of Proxmox and since then the problem occurs.

The IP address has not changed. At that time I had assigned a static one in Proxmox itself and in the network as well, permanently assigned to Proxmox. With the IP address, as mentioned, I can get to Proxmox at least via terminal.

The services or directories and data seem to still exist. (Screenshot). One part is LXC and another part is VMs.

How can I solve the problem that I can get back to the web interface and start and use the LXC containers and VMs again?

Thanks and greetings
ice

 

[Matthias.]

in ssh, which error messages do you see in journalctl -b --priority=4?
Output of systemctl status pveproxy?

 

[pille99]

what is the output locally telnet to 8006 ?

 

[iceweasel]

Thank you @Matthias. For the first command I get the following answer:

root@server:~# journalctl -b --priority=4
-- Logs begin at Mon 2023-03-20 21:46:37 CET, end at Mon 2023-03-20 21:52:39 CET. --
Mar 20 21:46:37 server kernel: secureboot: Secure boot could not be determined (mode 0)
Mar 20 21:46:37 server kernel: secureboot: Secure boot could not be determined (mode 0)
Mar 20 21:46:37 server kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Mar 20 21:46:37 server kernel:
                               Initialized Local Variables for Method [_CRS]:
Mar 20 21:46:37 server kernel:   Local0: 000000005239a752 <Obj>           Integer 0000000000000000
Mar 20 21:46:37 server kernel:   Local1: 000000000b556e40 <Obj>           Integer 0000000000000000
Mar 20 21:46:37 server kernel: No Arguments are initialized for method [_CRS]
Mar 20 21:46:37 server kernel: ACPI Error: Aborting method \_SB.PCI0.SPI1.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20190816/psparse-531)
Mar 20 21:46:37 server kernel: ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20190816/uteval-69)
Mar 20 21:46:37 server kernel:
                               Initialized Local Variables for Method [_CRS]:
Mar 20 21:46:37 server kernel:   Local0: 0000000013dcc561 <Obj>           Integer 0000000000000000
Mar 20 21:46:37 server kernel:   Local1: 000000000f72c0b2 <Obj>           Integer 0000000000000000
Mar 20 21:46:37 server kernel: No Arguments are initialized for method [_CRS]
Mar 20 21:46:37 server kernel: ACPI Error: Aborting method \_SB.PCI0.SPI2.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20190816/psparse-531)
Mar 20 21:46:37 server kernel: ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20190816/uteval-69)
Mar 20 21:46:37 server kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Mar 20 21:46:37 server kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Mar 20 21:46:37 server kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Mar 20 21:46:37 server kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20190816/psargs-330)
Mar 20 21:46:37 server kernel: No Local Variables are initialized for Method [_PLD]
Mar 20 21:46:37 server kernel: No Arguments are initialized for method [_PLD]
Mar 20 21:46:37 server kernel: ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.HS09._PLD due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
Mar 20 21:46:37 server kernel: ata2.00: supports DRM functions and may not be fully accessible
Mar 20 21:46:37 server kernel: ata2.00: supports DRM functions and may not be fully accessible
Mar 20 21:46:37 server systemd[1]: /lib/systemd/system/logrotate.service:16: Unknown lvalue 'ProtectClock' in section 'Service', ignoring
Mar 20 21:46:37 server systemd[1]: /lib/systemd/system/logrotate.service:18: Unknown lvalue 'ProtectHostname' in section 'Service', ignoring
Mar 20 21:46:37 server systemd[1]: /lib/systemd/system/logrotate.service:19: Unknown lvalue 'ProtectKernelLogs' in section 'Service', ignoring
Mar 20 21:46:37 server kernel: spl: loading out-of-tree module taints kernel.
Mar 20 21:46:37 server kernel: znvpair: module license 'CDDL' taints kernel.
Mar 20 21:46:37 server kernel: Disabling lock debugging due to kernel taint
Mar 20 21:46:37 server kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Mar 20 21:46:38 server kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq failed with error -2
Mar 20 21:46:38 server kernel: Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq (-2)
Mar 20 21:46:38 server kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2
Mar 20 21:46:38 server kernel: Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.8.bseq
Mar 20 21:46:38 server kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Mar 20 21:46:44 server kernel: new mount options do not match the existing superblock, will be ignored
Mar 20 21:46:44 server systemd-udevd[457]: Could not generate persistent MAC address for vmbr0: No such file or directory
Mar 20 21:46:44 server systemd[1]: logrotate.service: Failed with result 'exit-code'.
Mar 20 21:46:44 server systemd[1]: Failed to start Rotate log files.
Mar 20 21:46:48 server corosync[2134]:   [WD    ] Watchdog not enabled by configuration
Mar 20 21:46:48 server corosync[2134]:   [WD    ] resource load_15min missing a recovery key.
Mar 20 21:46:48 server corosync[2134]:   [WD    ] resource memory_used missing a recovery key.
root@server:~#

And on the second command, the following response:

root@server:~# systemctl status pveproxy
● pveproxy.service
   Loaded: masked (Reason: Unit pveproxy.service is masked.)
   Active: inactive (dead)
root@server:~#

 

[bbgeek17]

One possibility is that a Kernel upgrade happened but only took effect when you rebooted the system. The new Kernel may be incompatible in some way with your hardware.
You can try to downgrade the Kernel. The first step may even be a reboot and select a different kernel when booting, ie older one.

https://forum.proxmox.com/threads/proxmox-7-1-downgrading-kernel.104588/#post-450376
https://forum.proxmox.com/threads/how-to-pin-unpin-a-specific-kernel.111732/

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[iceweasel]

Thanks first of all for the last feedback @bbgeek17 .

I did not get to it currently earlier than just now. I have now tried the following.

First I entered this apt-install pve-kernel-5.4.203-1-pve

root@server:~# apt install pve-kernel-5.4.203-1-pve
Reading package lists... Done Building dependency tree.
Building dependecy tree... Done
Reading state information... Done
pve-kernel-5.4.203-1-pve is already the newest version (5.4.203-1).
pve-kernel-5.4.203-1-pve set to manually installed.
The following packages were automatically installed and are no longer required:
libqrencode4 librgw2 proxmox-archive-keyring proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image python3-ceph-argparse python3-cephfs python3-rados python3-rbd python3-rgw grencode
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 154 not upgraded.

Then entered proxmox-boot-tool kernel list and got the following feedback:

root@server:~# proxmox-boot-tool kernel list
Manually selected kernels:
5.4.203-1-pve

Automatically selected kernels:
5.4.34-1-pve
root@server:~#

Also after that typed the following update-grub and got that as a response:

root@server: ~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.203-1-pve
Found initrd image: /boot/initrd.img-5.4.203-1-pve
Found linux image: /boot/vmlinuz-5.4.34-1-pve
Found initrd image: /boot/initrd.img-5.4.34-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ..
done root@server:~#

After that reboot made.

The /etc/default/grub looks like this: (have not changed anything in it yet)


My /boot/grub/grub.cfg looks like this: (Screenshots "cfg_1... to cfg_6.png) (have not changed anything in it yet)

Screen 1



Screen 2



Screen 3



Screen 4



Screen 5



So far, even after several reboots, I still can't get to the proxmox web interface to start/set up the containers or virtual machines.

What am I (still) doing wrong?

Forgive me if I have to ask so much.