Recent content by egrueda

Got it! Thanks @Chris and @HeJohn for your help. I saw those "defunct" zombie processes I just stopped service, verified no zombie processes were there and started the service again. A scheduled backup has just started, so I can confirm issue is solved. Big thanks, guys!

Thanks, Chris. I see service pvescheduler is enabled, active and running. If ths bug was the issue, should the service be stopped? This started happening last week after I updated the server on march 27th I have updated it again couple of hours ago Also: libev-perl: 4.33-1+b1...

Using proxmox 7.4-3 in all of my servers. All of them using PBS client to make daily backups with no errors. A few days ago, one of my servers stopped doing the scheduled backups. There was no error I could found, scheduled task just didn't run. Manually running the backup still runs without...

Thanks for you help, Dominik, I'll try to script it. I see command "proxmox-backup-client list" exports user when json output is selected, so I'll use that to filter by owner. Bet regards

Hi! I have 2 different users in the same PBS server. Now "user2" is no more, so I want "user1" to have access to all backups created by "user2" How can I "move" all backups from user2 to user1? Thanks

That sound great, thank you!

Well, I tried to set same numerical prority in all nodes and then restarted one node. No changes, all migrated VMs went to the same node :-( Don't know if this is normal behavior or I might be missing some point

Hi! I have only 1 ha group All 3 nodes have no priority, should I set a numerical one (same for all) instead of leaving it blank?

Hi! PVE 7.1 here with HA Cluster and CEPH storage I have 3 nodes running 3 VMs each one, all nodes same priority. Migration works great. HA policy is to migrate when a node goes maintenance mode, and its doing fine except it's moving all VMs to the same node So when I reboot a node, I go from...

Hi, rlovelett Same problem here since last night. Did you get any fix or explanation?

Thanks very much, Stoiko

Thanks, Stoiko! I was looking elsewhere, didn't see that. In fact, problems started after (failed) update, so it seems kernel was not updated but some other packages did :-/ Do you think a dist-upgrade would fix this?

Hi all. I have a problem with a proxmox server that shows all LXC containers stopped. pve-manager/5.3-5/97ae681d (running kernel: 4.4.6-1-pve) Containers are online and working, but all pct commands fail: #pct list Failed to load config for 108 Failure to retrieve information on...

And one year later, I'm facing the same problem! It happens with centos7 template, but not with centos6 template. I downloaded a centos7 alternative template from https://us.images.linuxcontainers.org/ and got the same result. Can't find what's wrong :-(

Hi! Time ago we used FSCKFIX=yes in /etc/default/rcS to automatically repair defect filesystems during boot. (https://manpages.debian.org/stretch/initscripts/rcS.5.en.html) Later, Debian moved to systemd so we started using systemd-fsck@.service to force repair on check...