Hello,
I have a mini PC running Proxmox some time ago I had two power outages in a row.
Since then I can't log into either the Proxmox web interface or AdGuard.
Proxmox is installed on a mini PC, there I have HommeAssistant as a vitrual machine and AdGuard in a container.
Through SSH I can connect to Proxmox but when I try through the site it grinds and nothing happens at the bottom left it says I am waiting for api.start.me.
I hooked up the monitor to this mini PC and I see something like this (attached photo).
The HA itself works but somehow so slow, that's the impression I get, as if something is slowing it down.
Through SSH I found a couple of errors but I don't know if they have anything to do with this behavior of Proxmox.
Maybe someone knows what could be the cause of all this?
Here some additional information:
I have a mini PC running Proxmox some time ago I had two power outages in a row.
Since then I can't log into either the Proxmox web interface or AdGuard.
Proxmox is installed on a mini PC, there I have HommeAssistant as a vitrual machine and AdGuard in a container.
Through SSH I can connect to Proxmox but when I try through the site it grinds and nothing happens at the bottom left it says I am waiting for api.start.me.
I hooked up the monitor to this mini PC and I see something like this (attached photo).
The HA itself works but somehow so slow, that's the impression I get, as if something is slowing it down.
Through SSH I found a couple of errors but I don't know if they have anything to do with this behavior of Proxmox.
Code:
[ 76.367210] usb 1-1: unable to read config index 0 descriptor/all
[ 76.367235] usb 1-1: can't read configurations, error -110
[ 76.495120] usb 1-1: new full-speed USB device number 9 using xhci_hcd
[ 81.743512] usb 1-1: unable to read config index 0 descriptor/all
[ 81.743535] usb 1-1: can't read configurations, error -110
[ 81.743651] usb usb1-port1: attempt power cycle
[ 82.399445] usb 1-1: new full-speed USB device number 10 using xhci_hcd
[ 86.861041] usb 1-1: unable to read config index 0 descriptor/all
[ 86.861064] usb 1-1: can't read configurations, error -71Maybe someone knows what could be the cause of all this?
Here some additional information:
Code:
systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-09-01 10:10:33 CEST; 38min ago
Process: 1018 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1020 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 1022 (pveproxy)
Tasks: 4 (limit: 18987)
Memory: 247.5M
CPU: 3.577s
CGroup: /system.slice/pveproxy.service
├─1022 pveproxy
├─1023 pveproxy worker
├─1024 pveproxy worker
└─1025 pveproxy worker
Sep 01 10:10:32 proxmox systemd[1]: Starting PVE API Proxy Server...
Sep 01 10:10:33 proxmox pveproxy[1022]: starting server
Sep 01 10:10:33 proxmox pveproxy[1022]: starting 3 worker(s)
Sep 01 10:10:33 proxmox pveproxy[1022]: worker 1023 started
Sep 01 10:10:33 proxmox pveproxy[1022]: worker 1024 started
Sep 01 10:10:33 proxmox pveproxy[1022]: worker 1025 started
Sep 01 10:10:33 proxmox systemd[1]: Started PVE API Proxy Server.
Code:
pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-9
pve-kernel-helper: 7.2-9
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-15
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.4.174-2-pve: 5.4.174-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1
Code:
systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-09-01 10:10:31 CEST; 41min ago
Process: 983 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 1013 (pvedaemon)
Tasks: 4 (limit: 18987)
Memory: 142.3M
CPU: 1.058s
CGroup: /system.slice/pvedaemon.service
├─1013 pvedaemon
├─1014 pvedaemon worker
├─1015 pvedaemon worker
└─1016 pvedaemon worker
Sep 01 10:10:31 proxmox systemd[1]: Starting PVE API Daemon...
Sep 01 10:10:31 proxmox pvedaemon[1013]: starting server
Sep 01 10:10:31 proxmox pvedaemon[1013]: starting 3 worker(s)
Sep 01 10:10:31 proxmox pvedaemon[1013]: worker 1014 started
Sep 01 10:10:31 proxmox pvedaemon[1013]: worker 1015 started
Sep 01 10:10:31 proxmox pvedaemon[1013]: worker 1016 started
Sep 01 10:10:31 proxmox systemd[1]: Started PVE API Daemon.
Code:
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 008: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
