dakralex's latest activity
-
dakralex replied to the thread Proxmox Update von 8 ->9 defekt.Danke, ich nehme an, dass der beschriebene Fehler bei der HLS-PVE3 Node auftritt? Wenn ja, was ist denn der Output von journalctl -xeu pve-ha-lrm und journalctl -xeu pve-ha-crm auf dieser Node? Ein Verdacht ist, dass das Lock für den LRM auf... -
dakralex replied to the thread System log entries - apparmor and /usr/bin/man.FYI, one rather insecure way to mitigate this is to disable the apparmor profile for now with aa-disable /usr/bin/man or another slightly better solution is to use aa-logprof (in apparmor-utils package) which allows modifying the apparmor profile...
-
dakralex replied to the thread System log entries - apparmor and /usr/bin/man.Hi! Have you set up any man pager with the MANPAGER environment variable (echo $MANPAGER)? Either way, the audit message doesn't say much, but I can only guess that it could be about the seccomp(...) syscalls that man does make at startup to...
-
dakralex replied to the thread Proxmox Update von 8 ->9 defekt.Hi! Wird auf dem Cluster aktiv der HA Manager betrieben? Was ist der Zustand vom HA Manager (ha-manager status / ha-manager status --verbose)?
-
dakralex replied to the thread kauditd0 after pve9 upgrade.FYI, multiple (external) users reported [0] [1] [2] that processes with the name "kauditd0" were malware running on their system / containers, especially because they try to imitate a kernel thread but are clearly not a kernel thread at all. [0]...
-
dakralex replied to the thread kauditd0 after pve9 upgrade.And what does ls -lha /proc/$pid/exe show? If it's a kernel thread (and kauditd normally is a kernel thread), then it won't exist. But in your case it exists and should be a symbolic link to the executable that is running in that process.
-
dakralex replied to the thread kauditd0 after pve9 upgrade.Hi! This is just a guess, but it seems like this is a process imitating the actual kernel thread kauditd, especially because kernel threads lack information like the uptime, cpu%, mem%, etc. Could you post the output of cat /proc/$pid/cmdline...
-
dakralex replied to the thread updated to PVE 9.0 then GPU passthrough stopped working on Windows.Unfortunately, that was a false flag as the patch that introduced the bug is not in v10.0.2, but is in the upstream's staging tree. However, a quick setup with a Windows 11 VM with a 9th generation Intel UHD 630 GPU in passthrough showed similar...
-
dakralex replied to the thread [Solved] PVE Web interface not working.Hi! Assuming that JavitoVE is the Proxmox VE host, could you post the output of pveversion -v on that host?
-
dakralex replied to the thread PVE8TO9 all ok but i have broken packages after upgrade.Great that it worked out! The issue could've been that the node where the package upgrades failed because there wasn't any available source for these packages, i.e., there weren't any Debian Trixie repositories in the sources list. Anyway, it...
-
dakralex replied to the thread updated to PVE 9.0 then GPU passthrough stopped working on Windows.Thanks, so the Intel graphics driver's ctlInit fails and prints a CTL_RESULT_ERROR_NOT_INITIALIZED error (1073741825 = 0x40000001) [0], which unfortunately is quite generic and doesn't tell much about the error except that the Control API /...
-
dakralex replied to the thread Upgrading to Proxmox 9 Issues.I'm not sure about what you're trying to do here: iface vmbr0 inet6 static address 2a01:4f8:10b:2119::***/127 up ip -6 route add 2a01:4f8:10b:***::/64 dev vmbr1 But you shouldn't reference other interfaces in the command then the...
-
dakralex replied to the thread Upgrading to Proxmox 9 Issues.Yes, plymouth is not the issue but there might be an issue while generating the initramfs, installing the kernel image, etc. So you can try to regenerate the GRUB config and check if the installation of the new kernel was successful (or try...
-
dakralex replied to the thread Upgrading to Proxmox 9 Issues.There's also another warning in your bootlog that might point in a direction: Aug 08 14:37:01 server networking[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device "vmb> Aug 08...
-
dakralex replied to the thread Upgrading to Proxmox 9 Issues.Hi! There is a failing service logged in the bootlog: Aug 08 14:37:03 server (plymouth)[514]: emergency.service: Unable to locate executable 'plymouth': No such file or directory With the fact that the boot works with another kernel it's...
-
dakralex replied to the thread After upgrade to PVE 9, qm, ha-manager, pvestatd, and more fail to start (unknown file 'ha/rules.cfg').Thanks, according to the output this looks like that there was an error while upgrading the packages and the packages were only upgraded partially. Were there any issues during the upgrade when running apt update and apt dist-upgrade? Were the...
-
dakralex replied to the thread updated to PVE 9.0 then GPU passthrough stopped working on Windows.Thank you both for the thorough reports! I investigated a bit and as already noted the kernel images should be the same AFAICT, even though these have different build times the versions indicate that these have the same upstream base kernel and...
-
dakralex replied to the thread After upgrade to PVE 9, qm, ha-manager, pvestatd, and more fail to start (unknown file 'ha/rules.cfg').Hi! On which versions are the packages on pve3 (output of pveversion -v)? Edit: It seems like an error from a partial upgrade where pve-cluster is not up-to-date yet.
-
dakralex replied to the thread Upgrading from Proxmox 8 to 9 issue: GRUB error: out of memory.Hi! If that also happens for any Live CD (e.g. Debian 12/13), then check whether there are any memory-related BIOS settings that might cause this (e.g. BAR, IGD, ...). It could also help to upgrade the BIOS firmware and/or reset BIOS settings...
-
dakralex replied to the thread [SOLVED] ifupdown2 and /etc/network/interfaces issue.Are you sure? Or did I misunderstood that those errors are from within the VM? Especially with the error message above, I cannot see any reason that the host would fail with that error message if there wasn't any API breakage introduced by at...