Search results

  1. T

    Hetzner Proxmox Routed config.

    Hi to all. I've a dedicated on Hetzner with main ip 178.63.50.218 used for Hypervisor and a second subnet 178.63.149.0/29 for VM/LXC. For subnet Hetzner ask routed configuration without virtual macs. Using several guides and some posts from this forum i've made this conf: On Hypervisor i've...
  2. T

    Upgrade from 7 to 8 kernel issue

    As wrote on my first post: "Before i've the same error witk kernel 5.15.x and moved to /tmp folder. Now with 5.4 error still persist." Also tried with 6.1. The issue could not be fixed.
  3. T

    Upgrade from 7 to 8 kernel issue

    All kernel reported an error like this. I've also tried to install latest with: apt install pve-kernel-6.1.
  4. T

    Upgrade from 7 to 8 kernel issue

    Installed back Proxmox 7 from iso (8's iso crash), updated to 8, restored QMs from remote snapshot, now it work. :(
  5. T

    Upgrade from 7 to 8 kernel issue

    The server below is a disaster, need to be reinstalled Proxmox again like the first time. I will not update the other servers before upgrade will be safe.
  6. T

    Upgrade from 7 to 8 kernel issue

    Hi to all, i've update one servere from 7 to 8 with same errors but it work at least But, on another one server i've this error: apt update apt dist-upgrade Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://download.proxmox.com/debian/ceph-quincy...
  7. T

    QM restart with long process and report ^@^@ character in syslog

    Hi to all, i'm experiencing constantly restart on 2 VPS when any long proccess, like a backup of a user with a very large amount of files, start on server. After investigating, i've found these messages based on the null byte characters are encountered previously in /var/log/syslog and various...
  8. T

    Cluster dissmissing right procedure without data loss or damage to VPSs

    Dear users, i have to dismiss a dedicated server that is the master of a cluster of 3 machines. Later i would also like to completely delete the cluster from the 2 remaining slaves. If I'm not mistaken these are the necessary steps / commands: I remove all the restart and replication settings...
  9. T

    DirtyPipe (CVE-2022-0847) fix for Proxmox VE

    Thanks for your reply. Just updated to pve-kernel-5.13.19-6-pve without errors. ;)
  10. T

    DirtyPipe (CVE-2022-0847) fix for Proxmox VE

    Hi, i've incurred same error The package pve-kernel-5.13.19-5-pve needs to be reinstalled, but I can't find an archive for it. tried to reinstall without success. Thanks

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!