On a PVE cluster I noticed that xterm.js shells behave differently depending on whether the shell is opened on the node serving the Web UI or on another cluster node.
Reproduction:
* Open the PVE Web UI on node A.
* Open `Shell` for node A...
At the moment I am running on 7.0.14-14-pve. I didn't document previous version but I install updates every 4 weeks, so it can't be large jump. Installed updates on Sunday, server started to acting strange on Tuesday. Today I installed latest...
Yes, it's probably not necessary in practice but it remains ironic: that which makes check-summing redundant filesystems perfect for swap is exactly what makes them impossible to use for swap.
I guess a md-raid1 of multiple md-integrity (without...
Try removing the nvidia card and booting into the installer. If that works then you know it is the nvidia drivers. You can blacklist the module to get your normal boot and work from there.
It's not cluster.
journalctl -b | grep "system reset reason" gives no output
It's ASUS motherboard ( if I remember correctly), so sadly no Ipmi/Idrac.
On last reboot found never seen log entry:
Aug 28 13:17:44 test QEMU[2319]: ehci: PERIODIC...
Thanks @clangren.
Had the same issue on a 2-node cluster. The problem was on one node upgraded from a bookworm-installation which had still rsyslog running. Purged rsyslog and then the "vacuum-time" trick did the job.
-Did you rule out fencing in case it is a cluster node?
- Does Previous system reset reason shows something interesting?
journalctl -b | grep "system reset reason"
Do you have in IPMI/iDRAC? does it show anything in health event logs/sensor reading?
The /usr/sbin/shutdown command (run from the console or cron) will shutdown Proxmox in the same way as shutting down Proxmox from the web GUI. It also allows you to specify a specific time as well. This is a well known Linux command and there are...
And you don't need to shutdown guests before that. Just add a 0 1 * * * root /usr/sbin/shutdown -h now to /etc/crontab and it should shutdown the server each day at 1 at night. But keep in mind that this won't check if important tasks are still...
It all started when I updated to 9.2.11 using pve-no-subscription repositories. Proxmox reboots randomly after 10-20 minutes. Can't find anything meaningful in logs, except :
Aug 28 13:12:46 test pvestatd[1820]: storage 'Buffalo' is not online...
Ich sehe bei anderen Storages nach dem löschen eines LV (VM Disk) dass ein Reclaim auf dem Pool startet. Da wird Speicher frei gegeben und somit im Background ausgenullt.
Eventuell liegt das daran, dass ich eine VM Disk gelöscht habe wo Discard...
I would also like if possible to have your opinion
https://amzn.eu/d/03wJe189
should buy cheap sff , but since from experience I know that proxox does not get along with rtl and some intel I have had experience , in your opinion this model with...
Good question, it made me do a short googling. Following older stackoverflow thread from the results has some interesting points:
https://unix.stackexchange.com/questions/269098/silent-disk-errors-and-reliability-of-linux-swap
The basic argument...
> what is the recommended proxmoy (sic) way to go to have swap on servers with requirement for redundant disk (i.e. raid storage) ?
You don't need "checksums or redundancy" for swap, that makes little sense. If the server has a requirement for...
I don't really see your point, that has been the case since swap was invented (probably back in the 60's.) Any Linux system can have multiple swap partitions in addition to swap files. Or NO swap - although for Linux at least, a minimal swap...
Isn't this the same as putting a swapfile on btrfs or zfs directly but with extrasteps so not supported? And way more fragile due to the NFS layer between?I wouldn't see some hack from a raspberry forum as "supported".
Thanks for the links. I have looked into both of them in more detail now.
The fleecing patch is interesting because it demonstrates that a QEMU block-drain condition can indeed leave guest I/O stuck if the drained section is not terminated...