Recent content by ulzha

  1. U

    Proxmox broken at upgrade to 4.4-5.

    Yes, this is correct. Everything is up and running. Will be more careful next time. Thank you!
  2. U

    Proxmox broken at upgrade to 4.4-5.

    Hi! We have 2 nodes in a cluster. After running upgrade we received message: Setting up pve-manager (4.4-5) ... Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details. dpkg: error processing package pve-manager (--configure): subprocess...
  3. U

    Proxmox node consumes RAM and reboots

    Hi! We are running PVE 4.2 with two nodes in a cluster: ProLiant DL320 G5p with HDDs, RAM 8 GB and ZFS Dell PowerEdge R530 with SSDs, RAM 16 GB and ZFS Old ProLiant works like a charm. It hosts some 7 light LXC containers and RAM usage is 50% from total. There are no issues with this old...

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!