Search results

That hook script comes out of source control so I just updated the path and everywhere its in use it will just read the new path. Its still hardcoded, I'll fix it when I get around to it. But for now it should work.

Terrific response! I will get those updated ASAP. I only updated from PVE 7 - 8 a couple of months back so that is probably why I didn't notice it.

I have been using a guest hookscript for a few years that runs fsck on disks on the pre-start hook. It does this because the VM I am running uses a kernel boot file and so there is no opportunity to check the disk from within it. Anyway, the script ran but didn't find the disks. Long story...

You can mount any backup server anywhere and restore it. I literally do that all the time. Unless I misunderstood your question? If you mean you can't see the remote namespace locally, then no - but you can go to datacentre and add your local backup and this time specify the namespace you...

Todays entry: Mar 14 06:26:24 proxmoxy5 kernel: INFO: task php8.1:588542 blocked for more than 120 seconds. Mar 14 06:26:24 proxmoxy5 kernel: Tainted: P O 6.5.13-1-pve #1 Mar 14 06:26:24 proxmoxy5 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this...

The syslog inside the container indicates nothing unusual but stops at 06:30:02 This and the previous issue indicates that its probably the replication which takes place every 15 mins that is probably the cause. The backup ran at 5:40 and completed ok. This container is privileged because it has...

command just hangs. The issue you are referring to is another bug - which has been talked about since 2020 - thats the one where the filesystem becomes unwritable to the guest even though its still mounted you cannot recover from that until you reboot the VM - but you can reboot the VM. People...

resorted to rebooting the node. There's obviously a bug here in the new latest proxmox. and now, I have completely lost control of the node: System is going down. Unprivileged users are not permitted to log in anymore. For technical details, see pam_nologin(8). X11 forwarding request failed...

I don't think its backing up at the time. I use PBS using snapshot mode like I have done on this container for the last 12 months. Only since 8.1.4 installed are we now having an issue

root@proxmoxy5:~# pct list hangs root@proxmoxy5:~# pct stop 123 command 'lxc-stop -n 123 --kill' failed: received interrupt received interrupt root@proxmoxy5:~# pct destroy 123 There is a replication job '123-3' for guest '123' - Please remove that first. root@proxmoxy5:~# lxc-info 123...

I moved the CT to new node and its happened again today on that node and brought it down. I can get on the console of the node as root.

My colleague has informed me that he could connect to node 3 and get to the web gui, but that the node and the machines were just numbers showing no names exactly as above. I only tried the ssh on to the bad node and I got "connection refused". Even though he could get to the web interface...

I have a 5 node system where only 1 - 3 have any workload, a mixture of imported KVM VM's and new containers. This morning something wasn't right with one of the containers which was responsible for a couple of intranet websites. As we couldn't ssh to the container we went to look to see if it...

Ah - very good. Yes, it does exactly the same and should cause the issue. But, we have dozens of VM's backing up hourly for over a year now and not one issue - which is why I said we have not seen it for a while. And instead of cloning or snapshotting in the GUI I tend to use the closest...

Actually - you'll probably find that its common to have multiple nodes shoved into a switch relying on that. For HA of course, this is no good because loss of that switch will mean all of your nodes start rebooting. For me, this is where Proxmox documentation could be better - it makes it very...

TLDR: No. However, I haven't seen the issue for some time now yet I don't think it's fixed. I could never understand why replication which effectively does the same thing doesn't cause an issue - but now we are many versions down the road for PVE and ZFS. Instead of snapshots, I now tend to...

Visited the site. There had been a delivery and boxes were placed in such a way as to snag the UPS outlet cable. So this was a power off. The servers have redundant power and someone had put them all on the same UPS circuit, so now I split them and locked the server room door. Proxmox wasn't...

All, have a cluster of 3 dell servers running about a dozen VM's and containers rebooted itself and I cannot find a reason why. At the moment it looks like all 3 rebooted at precisely the same time. Previously, I have had this happen (as expected) due to watchdog timeout should networking be...

Nope - but: # qm rescan rescan volumes... VM 101 add unreferenced volume 'local-zfs:subvol-101-disk-0' as 'unused0' to config VM 101 add unreferenced volume 'local-zfs:subvol-101-disk-1' as 'unused1' to config Then I removed it and disks are gone and disk space is looking healthier.

These disks are not from this VM, they are from a container that used to have ID 101. I just checked the hostname. There's a root disk and a /var disk which is what they are. So how to remove these disks? Is it safe to just remove them from the pool?