[SOLVED] different service timeouts

D

Dorgyver

New Member
Feb 25, 2025
2
0
1
Hello everyone,

I've been experiencing slowness and timeouts on Proxmox for several days now. It's hosted on a Lenovo ThinkBook 15 laptop.

I haven't changed any configurations; I just restarted it because it seemed a bit slower than usual (after being up for more than six months). But now, nothing is working at all. :/

Any help would be greatly appreciated, thanks.

Code: 
root@pve:~# systemctl status pve*
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:17:39 CET; 13min ago
    Process: 1093 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 1161 (pmxcfs)
      Tasks: 11 (limit: 28505)
     Memory: 58.0M
        CPU: 342ms
     CGroup: /system.slice/pve-cluster.service
             └─1161 /usr/bin/pmxcfs

Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/102: -1
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/102: /var/lib/rrdcached/db/pve2-vm/102: illegal attempt to update using time 1740515271 when last update time is 1740515271 (minim>
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/10000: -1
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/10000: /var/lib/rrdcached/db/pve2-vm/10000: illegal attempt to update using time 1740515271 when last update time is 1740515271 (m>
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/200: -1
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/200: /var/lib/rrdcached/db/pve2-vm/200: illegal attempt to update using time 1740515271 when last update time is 1740515271 (minim>
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local: -1
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local: /var/lib/rrdcached/db/pve2-storage/pve/local: illegal attempt to update using time 1740515271 when last update tim>
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: -1
Feb 25 21:27:51 pve pmxcfs[1161]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: illegal attempt to update using time 1740515271 when last up>

● pvescheduler.service - Proxmox VE scheduler
     Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:20:26 CET; 10min ago
    Process: 1321 ExecStart=/usr/bin/pvescheduler start (code=exited, status=0/SUCCESS)
   Main PID: 1326 (pvescheduler)
      Tasks: 1 (limit: 28505)
     Memory: 110.9M
        CPU: 527ms
     CGroup: /system.slice/pvescheduler.service
             └─1326 pvescheduler

Feb 25 21:20:18 pve systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Feb 25 21:20:26 pve pvescheduler[1326]: starting server
Feb 25 21:20:26 pve systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:20:14 CET; 11min ago
    Process: 1250 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1300 (pvedaemon)
      Tasks: 6 (limit: 28505)
     Memory: 181.0M
        CPU: 838ms
     CGroup: /system.slice/pvedaemon.service
             ├─1300 pvedaemon
             ├─1301 "pvedaemon worker"
             ├─1302 "pvedaemon worker"
             ├─1303 "pvedaemon worker"
             ├─1589 "task UPID:pve:00000635:000191C8:67BE283A:vncshell::root@pam:"
             └─1590 /usr/bin/termproxy 5900 --path /nodes/pve --perm Sys.Console -- /bin/login -f root

Feb 25 21:20:14 pve pvedaemon[1300]: worker 1301 started
Feb 25 21:20:14 pve pvedaemon[1300]: worker 1302 started
Feb 25 21:20:14 pve pvedaemon[1300]: worker 1303 started
Feb 25 21:20:14 pve systemd[1]: Started pvedaemon.service - PVE API Daemon.
Feb 25 21:25:48 pve pvedaemon[1302]: <root@pam> successful auth for user 'root@pam'
Feb 25 21:29:03 pve pvedaemon[1302]: <root@pam> successful auth for user 'root@pam'
Feb 25 21:29:46 pve pvedaemon[1589]: starting termproxy UPID:pve:00000635:000191C8:67BE283A:vncshell::root@pam:
Feb 25 21:29:46 pve pvedaemon[1303]: <root@pam> starting task UPID:pve:00000635:000191C8:67BE283A:vncshell::root@pam:
Feb 25 21:29:46 pve pvedaemon[1301]: <root@pam> successful auth for user 'root@pam'
Feb 25 21:29:46 pve login[1597]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)

● pvebanner.service - Proxmox VE Login Banner
     Loaded: loaded (/lib/systemd/system/pvebanner.service; enabled; preset: enabled)
     Active: active (exited) since Tue 2025-02-25 21:13:40 CET; 17min ago
    Process: 674 ExecStart=/usr/bin/pvebanner (code=exited, status=0/SUCCESS)
   Main PID: 674 (code=exited, status=0/SUCCESS)
        CPU: 146ms

Feb 25 21:13:36 pve systemd[1]: Starting pvebanner.service - Proxmox VE Login Banner...
Feb 25 21:13:40 pve systemd[1]: Finished pvebanner.service - Proxmox VE Login Banner.

● pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon
     Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:20:14 CET; 11min ago
    Process: 1248 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=0/SUCCESS)
   Main PID: 1299 (pve-ha-crm)
      Tasks: 1 (limit: 28505)
     Memory: 112.0M
        CPU: 541ms
     CGroup: /system.slice/pve-ha-crm.service
             └─1299 pve-ha-crm

Feb 25 21:19:09 pve systemd[1]: Starting pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon...
Feb 25 21:20:14 pve pve-ha-crm[1299]: starting server
Feb 25 21:20:14 pve pve-ha-crm[1299]: status change startup => wait_for_quorum
Feb 25 21:20:14 pve systemd[1]: Started pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.
Feb 25 21:31:01 pve pve-ha-crm[1299]: loop take too long (59 seconds)

● pve-ha-lrm.service - PVE Local HA Resource Manager Daemon
     Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:20:15 CET; 11min ago
    Process: 1310 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=0/SUCCESS)
   Main PID: 1314 (pve-ha-lrm)
      Tasks: 1 (limit: 28505)
     Memory: 107.5M
        CPU: 482ms
     CGroup: /system.slice/pve-ha-lrm.service
             └─1314 pve-ha-lrm

Feb 25 21:20:14 pve systemd[1]: Starting pve-ha-lrm.service - PVE Local HA Resource Manager Daemon...
Feb 25 21:20:15 pve pve-ha-lrm[1314]: starting server
Feb 25 21:20:15 pve pve-ha-lrm[1314]: status change startup => wait_for_agent_lock
Feb 25 21:20:15 pve systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
Feb 25 21:24:11 pve pve-ha-lrm[1314]: loop take too long (195 seconds)
Feb 25 21:25:51 pve pve-ha-lrm[1314]: loop take too long (100 seconds)
Feb 25 21:29:07 pve pve-ha-lrm[1314]: loop take too long (52 seconds)
Feb 25 21:31:01 pve pve-ha-lrm[1314]: loop take too long (67 seconds)

● pvenetcommit.service - Commit Proxmox VE network changes
     Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; preset: enabled)
     Active: active (exited) since Tue 2025-02-25 21:13:36 CET; 17min ago
    Process: 678 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
    Process: 683 ExecStart=sh -c if [ -f ${FN}.new ]; then mv ${FN}.new ${FN}; fi (code=exited, status=0/SUCCESS)
   Main PID: 683 (code=exited, status=0/SUCCESS)
        CPU: 1ms

Feb 25 21:13:36 pve systemd[1]: Starting pvenetcommit.service - Commit Proxmox VE network changes...
Feb 25 21:13:36 pve systemd[1]: Finished pvenetcommit.service - Commit Proxmox VE network changes.

● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:27:29 CET; 3min 47s ago
    Process: 1457 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
   Main PID: 1461 (pvestatd)
      Tasks: 2 (limit: 28505)
     Memory: 137.5M
        CPU: 803ms
     CGroup: /system.slice/pvestatd.service
             ├─1461 pvestatd
             └─1640 /sbin/vgs --separator : --noheadings --units b --unbuffered --nosuffix --options vg_name,vg_size,vg_free,lv_count

Feb 25 21:27:26 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
Feb 25 21:27:29 pve pvestatd[1461]: starting server
Feb 25 21:27:29 pve systemd[1]: Started pvestatd.service - PVE Status Daemon.
Feb 25 21:27:51 pve pvestatd[1461]: status update time (12.404 seconds)
Feb 25 21:29:13 pve pvestatd[1461]: status update time (71.404 seconds)
Feb 25 21:29:19 pve pvestatd[1461]: status update time (6.346 seconds)
Feb 25 21:29:46 pve pvestatd[1461]: status update time (22.813 seconds)
Feb 25 21:31:13 pve pvestatd[1461]: status update time (77.253 seconds)

● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon
     Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:13:36 CET; 17min ago
   Main PID: 719 (pve-lxc-syscall)
      Tasks: 5 (limit: 28505)
     Memory: 1.3M
        CPU: 2ms
     CGroup: /system.slice/pve-lxc-syscalld.service
             └─719 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock

Feb 25 21:13:36 pve systemd[1]: Starting pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon...
Feb 25 21:13:36 pve systemd[1]: Started pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon.

× pve-firewall.service - Proxmox VE firewall
     Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; preset: enabled)
     Active: failed (Result: timeout) since Tue 2025-02-25 21:24:10 CET; 7min ago
    Process: 1351 ExecStartPre=/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy (code=exited, status=0/SUCCESS)
    Process: 1352 ExecStartPre=/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy (code=exited, status=0/SUCCESS)
    Process: 1353 ExecStartPre=/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy (code=exited, status=0/SUCCESS)
    Process: 1354 ExecStart=/usr/sbin/pve-firewall start (code=killed, signal=TERM)
        CPU: 379ms

Feb 25 21:22:40 pve systemd[1]: Starting pve-firewall.service - Proxmox VE firewall...
Feb 25 21:24:10 pve systemd[1]: pve-firewall.service: start operation timed out. Terminating.
Feb 25 21:24:10 pve systemd[1]: pve-firewall.service: Failed with result 'timeout'.
Feb 25 21:24:10 pve systemd[1]: Failed to start pve-firewall.service - Proxmox VE firewall.

● pve-daily-update.timer - Daily PVE download activities
     Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; preset: enabled)
     Active: active (waiting) since Tue 2025-02-25 21:15:16 CET; 16min ago
    Trigger: Tue 2025-02-25 21:33:27 CET; 2min 10s left
   Triggers: ● pve-daily-update.service

Feb 25 21:15:16 pve systemd[1]: Started pve-daily-update.timer - Daily PVE download activities.

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:20:14 CET; 11min ago
    Process: 1249 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1264 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1304 (pveproxy)
      Tasks: 4 (limit: 28505)
     Memory: 202.8M
        CPU: 1.949s
     CGroup: /system.slice/pveproxy.service
             ├─1304 pveproxy
             ├─1305 "pveproxy worker"
             ├─1306 "pveproxy worker"
             └─1307 "pveproxy worker"

Feb 25 21:19:09 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Feb 25 21:20:14 pve pveproxy[1304]: starting server
Feb 25 21:20:14 pve pveproxy[1304]: starting 3 worker(s)
Feb 25 21:20:14 pve pveproxy[1304]: worker 1305 started
Feb 25 21:20:14 pve pveproxy[1304]: worker 1306 started
Feb 25 21:20:14 pve pveproxy[1304]: worker 1307 started
Feb 25 21:20:14 pve systemd[1]: Started pveproxy.service - PVE API Proxy Server.

● pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; preset: enabled)
     Active: active (exited) since Tue 2025-02-25 21:20:18 CET; 10min ago
    Process: 1315 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 1316 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=0/SUCCESS)
   Main PID: 1316 (code=exited, status=0/SUCCESS)
        CPU: 679ms

Feb 25 21:20:15 pve systemd[1]: Starting pve-guests.service - PVE guests...
Feb 25 21:20:15 pve pve-guests[1316]: <root@pam> starting task UPID:pve:00000525:0000B2D1:67BE25FF:startall::root@pam:
Feb 25 21:20:18 pve pve-guests[1316]: <root@pam> end task UPID:pve:00000525:0000B2D1:67BE25FF:startall::root@pam: OK
Feb 25 21:20:18 pve systemd[1]: Finished pve-guests.service - PVE guests.

● pvefw-logger.service - Proxmox VE firewall logger
     Loaded: loaded (/lib/systemd/system/pvefw-logger.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-02-25 21:13:36 CET; 17min ago
    Process: 676 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
   Main PID: 706 (pvefw-logger)
      Tasks: 2 (limit: 28505)
     Memory: 1.9M
        CPU: 350ms
     CGroup: /system.slice/pvefw-logger.service
             └─706 /usr/sbin/pvefw-logger

Feb 25 21:13:36 pve systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Feb 25 21:13:36 pve pvefw-logger[706]: starting pvefw logger
Feb 25 21:13:36 pve systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.

● pve-storage.target - PVE Storage Target
     Loaded: loaded (/lib/systemd/system/pve-storage.target; static)
     Active: active since Tue 2025-02-25 21:14:31 CET; 16min ago

Feb 25 21:14:31 pve systemd[1]: Reached target pve-storage.target - PVE Storage Target.
lines 178-234/234 (END)

Code: 
root@pve:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1
 

Attachments

  • Capture d’écran 2025-02-25 213816.png
    Capture d’écran 2025-02-25 213816.png
    18.5 KB · Views: 3
  • Capture d’écran 2025-02-25 213816.png
    Capture d’écran 2025-02-25 213816.png
    18.5 KB · Views: 3
The problem was with my disk, which was 52% worn (via a smartctl).

So I cloned my installation on a new disk and everything's working again.
 
You must log in or register to reply here.
Top Bottom