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.
https://superuser.com/questions/656695/which-clients-accept-dhcp-option-42-to-configure-their-ntp-servers
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.