A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I just woke up to all my lights on and my server off. It was a power cut, but... Checking the logs for Proxmox, it seems to have lost memory.. There were no logs for 10 days and when rebooting it said the system clock was off by as much (931,920 seconds = 10.7 days). What do? Anyone seen this before?
Thanks all, gonna replace the CMOS battery as suggested. Got a few in storage. π€
Your cmos battery is bad or your grid power was running below normal frequency
I don't think that the grid frequency is used for PC timekeeping. You have internal timekeeping circuits. AC power stops at the PSU, and I don't think that there's any cable over which a time protocol flows from the PSU to the motherboard.
I'd also bet against the CMOS battery, if the pre-reboot logs were off by 10 days.
The CMOS battery is used to maintain the clock when the PC is powered off. But he has a discrepancy between current time and pre-reboot logs. He shouldn't see that if the clock only got messed up during the power loss.
I'd think that the time was off by 10 days prior to power loss.
I don't know why it'd be off by 10 days. I don't know uptime of the system, but that seems like an implausible amount of drift for a PC RTC, from what I see online as lilely RTC drift.
It might be that somehow, the system was set up to use some other time source, and that was off.
It looks like chrony is using the Debian NTP pool at boot, though, and I donpt know why it'd change.
Can DHCP serve an NTP server, maybe?
kagis
This says that it can, and at least when the comment was written, 12 years ago, Linux used it.
The ISC DHCP client (which is used in almost any Linux distribution) and its variants accept the NTP field. There isn't another well known/universal client that accepts this value.
If I have to guess about why OSX nor Windows supports this option, I would say is due the various flaws that the base DHCP protocol has, like no Authentification Method, since mal intentioned DHCP servers could change your systems clocks, etc. Also, there aren't lots of DHCP clients out there (I only know Windows and ISC-based clients), so that leave little (or no) options where to pick.
Maybe OS X allows you to install another DHCP client, Windows isn't so easy, but you could be sure that Linux does.
My Debian trixie system has the ISC DHCP client installed in 2025, so might still be a factor. Maybe a consumer broadband router on your network was configured to tell the Proxmox box to use it as a NTP server or something? I mean, bit of a long shot, but nothing else that would change the NTP time source immediately comes to mind, unless you changed NTP config and didn't restart chrony, and the power loss did it.
I feel like other things would have misbehaved if the power frequency was too low. And I'd expect the RTC to run well while power is on, and fail to accumulate time while power is off, but still remember the time at power off.
None of what I said above explains what we are seeing with our eyes though.
It is just a dead CMOS battery. So the clock had the wrong time, which in turn also causes the log entries to have the wrong time and date. Simply replace the battery. It is most likely of the CR2032 type.
What kind of storage is it running on? Maybe the filesystem went read-only as another possibility to cmos battery issues.
Usually a cmos battery alone wouldn't cause something like logging to stop.
It went read-only because the root drive ran out of space. I've expanded its storage now. Big whoopsie on my end
In line with the possibility of your system's clock actually being wrong, can you correlate some other events in your logs to when you know they occurred? What about inside your VMs and CTs?
By any chance.... Your proxmox is not close to any source of big electromagnetic fields, right?
Close to big Transformator or electric motors, right?
Not at all but my god that sounds like that would be recipe for disaster
I've seen things.. Near the gate of TannhΓ€user, things you little people wouldn't believe.
And I am not joking...
Tell us more, wise one!
Switch to ZFS
Ext4 is way to vulnerable to power loss. It just keep a journal but it isn't nearly as robust as ZFS