Recent content by jebbam

I think that may have solved it. The machines had their times sync'd after boot (e.g. after running a minute), but there is a very small window where it was out of sync in the first few seconds presumably during services starting. I guess the services then don't care if the clocks get corrected...

Ok. I rebooted nh5, then created the nh5-journal-boot-fresh.txt file. Note: the PVE services start on boot, so they try to run. Then I stopped the services, this it the nh5-journal-boot-stopped.txt file. Then I started the services again, in the order in comment 8, and that is the...

Yes, only nh5 was rebooted. It didn't come up correctly when it booted up, but running the above command sequence got it going correctly again.

@fabian So everything was fine for a couple days, then I thought I would reboot nh5 to make sure things came back up ok (and checking before doing upgrades). But when it rebooted, it had the same issue. I am able to recover it by doing this: systemctl stop corosync.service pvebanner.service...

Awesome, that order did the trick. All looks good. I did the same for nh5 too, so they are all up. Thanks 100x for all your help! Do you know why this may have happened? I've rebooted Proxmox nodes many times, including entire clusters that were powered off, and I never had this issue before...

The network configs were all written last in January, 2025. So none of them have been touched in over a year. They are all the exact same size. So if it is a network issue, it could be maybe a flakey switch or something like that (?). Maybe MTU? But this network config has run perfectly fine for...

See attached. The node 2 and node 5 boot logs were "too large for the server to process" on upload. I truncated those as they just repeat the same things over and over, so they are small enough to upload. Thanks for your consideration. :)

I have a 5 node Proxmox cluster co-located in a data center with ~100 KVMs that has been running happily the last year+. The ISP needed to move the servers to another building (sigh). Everything came back online, but two of the nodes, node2 and node5, are not connecting to the cluster and give...

I have seen this in Debian bullseye, bookworm, trixie, and sid. It has been around for a lot of different kernel versions.

Ya, Proxmox doesn't have it there. In the Proxmox GUI, there is a setting, but it won't start if you set memory= over 128. So I have had it maxed at 128 on all the machines, all along, but that still gets the error. There is config settings per machine in...

Which XML file? I wasn't able to find one that had that setting. I do have this set: "vga: qxl,memory=128" Thanks!

Have you found a way to disable the "Display output is not active" that comes on after a few minutes? I haven't poked at it to see why it is coming up. It isn't the worst, but it is kind of annoying. Not as bad as crashing! :)

@ramius1984 The VirtIO-GPU workaround hasn't crashed, which is a big plus. One big drawback is it is very blocky when playing videos. I tried the various SPICE Enhancements Video Streaming options, but it didn't help. I do this on a few VMs, so it won't work for those. One minor...

Thanks! I'll give this a test run on some VMs for the next week or so. -Jeff

This is killing me. It's happening a bunch of times today. $5,000.00 USD bounty reward from me for whoever delivers a working fix for this. Payable via PayPal or credit card, if you accept credit cards. Sincerely, -Jeff Moe Loveland, Colorado, USA