Search results

Hi @Onslow Yes sure, so here is a list of the relevant processes on my system: root@jupiter:~# ps auxf | grep -A 5 dpkg root 11328 0.0 0.0 11988 6264 pts/0 T 15:05 0:00 \_ dpkg --configure -a root 11375 0.0 0.0 2688 1912 pts/0 T 15:05 0:00...

Ok after some more investigation I was able to fix it by running these commands: kill -9 13337 kill -9 11328 rm /var/lib/dpkg/lock-frontend rm /var/lib/dpkg/lock dpkg --configure -a After that the updates went through

Hi there, Today I ran a update, which does not seem to be sucessfully. Everytime I try to upgrade, the process hangs at the root@jupiter:~# dpkg --configure -a Setting up pve-manager (9.0.17) ... I tried to wait for an hour, but nothing happens. I rebooted and tried to update/upgrade, but it...

Thanks for the hint! I enabled the test repo and then run this command: apt update apt install --only-upgrade lxc-pve And after that disabled the repo again. Works like a charm, thanks!

Yea that's the same what I did now. Only think I'm wondering is, that I did not update any package within my LXC container and the issue still occurs. Is it an option to install an old containered.io package version?

Does anyone have a solution for alpine os? I have containerd.io version 2.1.3-2 installed (which is not the latest version), but I still have this issue.

Another update: Since kernel update to 6.14.8-2-bpo12-pve it seems, that the r8168-dkms driver does not work anymore (I can't get network access using this driver on the new kernel update)

@nathanhi It seems, that the kernel 6.14.8-2-bpo12-pve breaks this again (at least for me). It was working before the kernel update and now when I install that driver, the whole system has no access to the internet anymore. When I remove it and again use the r81689 driver, at least I can...

Ok the solution seems to be this: https://forum.proxmox.com/threads/unable-to-install-r8168-dkms-for-realtek-nic.137727/page-2#post-728510 # Download custom driver wget https://github.com/nathanhi/r8168/releases/download/pve8/8.054.00-1-bpo12/r8168-dkms_8.054.00-1-bpo12_all.deb # Install custom...

Hi there, After updating to PVE version 8 (currently installed version is 8.4.1 with 6.14 kernel), I occasionally have the error that my system is not reachable from one second to the other. After rebooting, everything seems to work, but the containers start very slow (while it usually takes...

Same for me. I get a email about a temperature issue every day. I added the -I option to the main line, but that does not change anything (yes I restarted the daemon, at some point even the whole machine): DEVICESCAN -d removable -n standby -m root -I 194 -M exec...

I just did a apt update && apt upgrade and the issue is now resolved on my system.

@eridian It seems that this issue still exists, right?

Hi there, Today I opened my HP ProDesk 400 G5 to dust of the fans. Then I plugged everything in again and booted proxmox. Even after 10 minutes, it was not reachable. I then hooked a monitor up to the client and this is what I saw: Found volume group "pve" using metadata type lvm2 86 logical...

Thanks for the hint! Good to see it's a bug and not something I did wrong. Then I have to wait for a bugfix and use your workaround. Thanks you very much!

Hi there, When I run apk update && apk upgrade within the console of my alpine LXC container, everything works fine. But when I run the upgrade command on my host like this: pct exec 102 -- bash -c 'apk update && apk upgrade' I get errors like this: fetch...

Thanks that worked The issue seems to be, that the USB is mounted to /dev/ttyACM0 instead of /dev/ttyUSB0 and therefore the permissions rule does not apply here. Again thank you very much!

When I do that, I can't seem to mount the device inside the docker container: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error...

Hi there, I want to run Octoprint on my proxmox server. For that I created a LXC container based on alpine OS and installed docker in it (that's what I do for all my other containers as well). I then created a USB passtrough to the lxc container by creating a...

Hi there, I added a new disk to my system and initialized it by creating a new volume group /dev/sdb Then I added a new mount point to a LXC container with 64GB of storage to the path /mnt/storage For some reason proxmox created three volumes within a couple of seconds: As you can see here...