In case anyone has a similar need, here are the (crude) scripts I made to wake up a spare server before replication jobs and shut it down after they are finished:
The first one should be scheduled to run every 5-10 minutes via cron:
#!/bin/bash
# Wakeup other node if a sync job is pending or...
Thanks for the answer. I keep the other server turned off mainly for saving energy. I'm running a homelab and two servers running 24/7 would imply twice the impact on the energy bill. I am happy with daily replication jobs and a single server can run all my VMs with no need for true HA or...
I have a PVE cluster with a backup server which I would like to keep turned off most of the time as a "warm spare". Would it be possible to automatically issue a wake-on-lan command before replication jobs are scheduled to run, and shut the node down after all the replication jobs have been...
I don't know exactly what do you mean by "what do you have on your PVE host", but I will describe as best as I can with what might be relevant. It's a Xeon E5-2689 on a chinese X79 motherboard with 32GB of ECC RAM. Proxmox was installed on Debian 10 (buster) 64, with LUKS-encrypted root on LVM...
I can also confirm that the problem no longer happens with an Alpine 3.11 container built from the alpine-3.11-default_20200425.tar.xz template. Should I mark this as solved?
Yes, it happens all the time, consistently, across multiple reboots, and also happens with an Alpine 3.10 container, but not with a Debian ct. It took me a while to figure out cat /proc/meminfo was the cause of the kernel warnings. So far I haven't noticed any other effects, both the ct and the...
I am new to PVE, testing version 6.1-8 on Debian 10 Buster. I am encountering a weird issue using a Alpine 3.9 unprivileged LXC container built from alpine-3.9-default-20190224_amd64.tar.xz template:
I have set 1GB RAM for the container. Here is the output of free -m:
total...
I can confirm this behavior.
But $TERM gets set to vt102 regardless of the CT number (I got this issue on a freshly installed container CT100 from the alpine-3.10-default_20190626_amd64 image on Proxmox VE 6.1-8 / Debian 10, using the PVE web console).
When I login using ssh, $TERM is set...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.