![]() Now I disable it and backups seems to be workingĪlso I think I should revert back the diff file i made changes to? or should I leave it alone ? it was enabled on my cPanel VM with AlmaLinux 8.5 Seems this might be the issue /script/securetmp needs to be disabled. Later I will also set scheduled backup for 10 mins and let it backup with schedule and see if it stays working. all took about 6 mins to finish never got stuck on freeze I did so far 2 VM backup manually and also 1 manually from scheduled backup section. I do not have cloudlinux, but AlmaLinux 8.5 with cPanel which they made in the first placeĪnd so far I tested 3 times and it works, will test again 3-4 times and later in a few hours, I will turn off VM then Turn back on and test Backups again in Snapshot mode, Not sure if this helps to find the cause. ![]() I'm afraid we have no further recommendations at this point. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:ģ) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash. ![]() ![]() When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. You'll need to disable it if you want to run snapshots/backups with CloudLinux ![]()
0 Comments
Leave a Reply. |