@olivierlambert said: I'm not sure it's a great idea, because even 64 hosts is huge in terms of VMs and fallout if you have a problem on your pool DB. Even if you drastically improve the current mechanism, the impact of a problem pool wide is far bigger with 64 hosts than 24 for example. It's more than purely tech, it's also a tech design/choice. Exactly, the failure domain just grows exponentially when going beyond a certain collective pool size. I was doing some more research and I found a few possible choices that Tesco may have moved too, but don't want to detract from this forum here.

IIUC, the Smart Reboot option found on the host's Advanced tab does what you are asking. [image: 1782309061091-3f858853-fe5c-4cd0-95c2-ce39859dedce-image.jpeg]

Hi @pierrebrunet With commit c74a8 the problem is still present but the transfer was completed again. Unfortunately my installation does not recognize the "xen-bugtool" command. And both log files are not present. Is this something that needs enabling after install of XCP-NG? Unfortunately and unnoticed my syslog-server did not receive any messages from XCP-NG in the last 30 days. Other inputs work **Edit: I have deleted and re-added the syslog-server with port and now logs are being send to Graylog.** Thanks for your assistance y'all. Regards, Marc

@Pilow pretty much

Here is the log from when xen04 last crashed xen04-jun12-journalctl-crash-summary.txt

@AlexanderK you could try to install perl-interpreter manually maybe? I happened to have a test host at hand that hasn't been updated since december, and the yum update went fine, perl interpreter was not installed before and yum update did install it on its own as a depency for openssl 3. Maybe others will have ideas as to why this would happen in your case.

@jul1an [image: 1782285080688-2026-06-24_101114.jpg] [image: 1782285186489-2026-06-24_101302.jpg] I am using a translator because my English is limited. I have 5 identical servers equipped with Adaptec 6805 controllers. Previously, I bypassed the controller issues by using an alternative kernel, but that triggered network problems—specifically, network bonding is unstable on the alt-kernel.I have tested your evaluation image, but unfortunately, it did not resolve the issue. Later today, after my work shift, I will provide the logs and output from dmesg.I am ready to fully cooperate to fix this and can even arrange remote access via IPMI if needed.

@tuxen Doing some research, it doesn't look like the Xeon's I have are affected. But I'm willing to try the next time I need to reboot. Will report back after that.