New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
NTP isn't installed by default, I installed it on request on a few nodes.
I didn't yet install it on all nodes, I will check later though.
3932-356f-25d0-a686
Oh no, the time on my lxc is more than a day behind, and
apt updateis throwing an signature errorActually LT has chrony already installed, you sure its a time problem?
Yes
date -u
Fri Jul 3 02:57:46 AM UTC 2026
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-updates InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-07-04T01:45:00Z Verifying signature: Not live until 2026-07-04T01:45:12Z
I added local NTP servers, for some reason the default ones caused it to desync.
Sad news—I forgot Netherlands doesn't offer LXC anymore. I deleted it and lost it forever
Hello, can we have ubuntu 26.04 LXC image?
Can we bring back the Netherlands lxc, nothing is safe anymore, thanks to Januscape😂
I haven't updated all nodes to 6.8 yet, we had issues with a ancient kernel before.
Once the node is upgraded to 6.8
206e-3861-42e1-83b7
Let's jump to 7.1.3—the Zabbly kernel, maintained by the Incus developer Stéphane Graber.
Also, it seems there's a problem with the nftables module in Norway. A simple redirect rule results in the following error: /etc/nftables.conf:24:62-69: Error: Could not process rule: No such file or directory
No, there is a reason why we use the Ubuntu kernel, gets livepatching.
Best I can do right now is 6.8, maybe 26.04 with 7.0
NL got rebooted and migrated to another Node.
Live migration wasn't possible due to the cpu passthrough we got enabled.
Hence the 30 minutes downtime.
Enjoy the CPU upgrade.