Recent content by dengolius

  1. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    FYI: it works without any issue after applying recommendations from you link. Thank you, one more time!
  2. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    I've applied recommendations from https://forum.proxmox.com/threads/kernel-9203-691567-watchdog-bug-soft-lockup-cpu-15-stuck-for-6802s-systemd-timesyn-639.146368/#post-665192 so my server is running smoothly for the latest month. PS: I also failed in issue with Kernel 6.8 on my laptop on...
  3. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    Thanks! I've applied all recommendations to my server and will test the server. I'll add new information.
  4. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    Hetzner support upgraded BIOS for motherboard to the latest version but the bug is still appears.
  5. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    Looks like I've solved it by disabling systemd-timesyncd service: sudo systemctl disable systemd-timesyncd and enabling sudo timedatectl set-ntp true+ uncomment line with FallbackNTP cat /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can...
  6. D

    kernel:[ 9203.691567] watchdog: BUG: soft lockup - CPU#15 stuck for 6802s! [systemd-timesyn:639]

    I've just upgrade PVE server from 8.1.3 to the latest 8.2.2 and got this: sudo apt autoremove [sudo] password for dengolius: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: pve-kernel-5.15...
  7. D

    do_start: 1272 Failed to setup container "100" sync_wait: 34 An error occurred in another process (expected sequence number 4) __lxc_start: 2107 Faile

    I've installed the latest version 8.1 yesterday and didn't saw this issue. It looks like a bug with starting systemd service which appears randomly...
  8. D

    do_start: 1272 Failed to setup container "100" sync_wait: 34 An error occurred in another process (expected sequence number 4) __lxc_start: 2107 Faile

    As I said before, LXC containers didn't start out-of-the-box after Proxmox has been installed. So I think that there is some bug with installation process. sudo journalctl -b-1 -u lxcfs.service Jul 01 11:15:12 ox2 systemd[1]: Started lxcfs.service - FUSE filesystem for LXC. Jul 01 11:15:12 ox2...
  9. D

    do_start: 1272 Failed to setup container "100" sync_wait: 34 An error occurred in another process (expected sequence number 4) __lxc_start: 2107 Faile

    systemctl status lxcfs.service systemctl status lxcfs.service ○ lxcfs.service - FUSE filesystem for LXC Loaded: loaded (/lib/systemd/system/lxcfs.service; enabled; preset: enabled) Active: inactive (dead) Docs: man:lxcfs(1) So I've started LXC service by running systemctl...
  10. D

    do_start: 1272 Failed to setup container "100" sync_wait: 34 An error occurred in another process (expected sequence number 4) __lxc_start: 2107 Faile

    Proxmox 8, freshly installed at this night on hetzner bare metal server https://www.hetzner.com/dedicated-rootserver/ex44 . Old LXC containers whic I've restored from backup don't work to. The next log and screenshots are from newly created LXC container: lxc-start 110 20230701090146.130 INFO...
  11. D

    Monitoring Proxmox

    FYI: https://victoriametrics.com/blog/graphite-query-language-opensource/ so users can use graphite/influx monitoring for PVE server with VictoriaMetrics open source Cluster or Single
  12. D

    Proxmox on aarch64 (arm64)

    Here is the answer https://discord.com/channels/1040085308223520819/1089221423148568627/1095669133997260902
  13. D

    Proxmox on aarch64 (arm64)

    Better to ask it via issue at https://github.com/pimox/pimox7