Recent content by RobFantini

Hello, I am not sure what fixed the issue. The hangs stopped coming . Probably the way I brought down the node to be replaced caused the issue , related to removing the osd's from cluster. It has been a year and not certain on that. I did check the ext4 drives with smartctl. No issues...

Have you already purchased the motherboards? If not price out single cpu systems with plenty of memory. The savings over dual cpu ( assuming you were pricing that out) may leave cash to afford nvme’s or data a center grade ssd

you are correct . I was trying to convert an unprivileged to privileged . I had mis read the instruction at the wiki page https://pve.proxmox.com/wiki/Unprivileged_LXC_containers . it mentions ' It is possible to convert an existing CT into an unprivileged CT by doing a backup, then a...

I see , had thread name wrong. Just fixed that unable to restore an privileged CT as unprivileged is the issue

there is another thread named 'unable to restore an unprivileged CT as unprivileged' ( https://forum.proxmox.com/threads/unable-to-restore-an-unprivileged-ct-as-unprivileged.80004/ ) . so I have a privileged container I want to convert to unprivileged. tried these: # pct restore 181...

changing backup start time away from midnight solved the issue.

After today's updates I get that message when I click on a node on pve screen # ll /etc/subscription -rw-r----- 1 root root 367 Jun 1 03:58 /etc/subscription this fixed the issue chmod 644 /etc/subscription

I moved the backup time to 00:10 . Will keep you posted on the results. I'll put to my calendar to report back if there are no issues in a week.

at midnight. Should I move that 10 minutes forward?

also during backups other nodes had the following errors. however the backups succeeded May 26 00:00:12 pve7 pve-ha-lrm[3892712]: VM 101 qmp command failed - VM 101 qmp command 'query-status' failed - got timeout May 26 00:00:10 pve2 pve-ha-lrm[2594781]: VM 106 qmp command failed - VM 106...

journalctl -b --since "yesterday" > journalctl.txt

note that all 5 nodes use the same pve backup job. so they run at the same time. perhaps I should make a backup job spread out for each node?

journalctl -b -p3 -u proxmox-backup-proxy --since "yesterday" May 26 00:00:15 pbs-new proxmox-backup-proxy[2419]: error writing task result to the tasklog May 26 00:00:16 pbs-new proxmox-backup-proxy[2419]: GET...

Hello . I've seen mention of this at the German forum and a thread here [ which the poster never replied to the help given]. on one of 5 nodes in the last week the first vm fails a pbs backup. from backup fail emails: pve-15 107: 2026-05-18 00:00:16 ERROR: VM 107 qmp command 'backup'...

I have not tried the following but am posting for future reference. from grok : https://grok.com/share/bGVnYWN5LWNvcHk_d940cfad-264d-46e6-a144-3e3e02625ae5 Recommended command for full cluster shutdown 1 Run this on any one node (it affects the whole cluster): ha-manager crm-command...