English Español Deutsch Français Italiano

mirrors: kaizushigdv5mrnz.onion bzznfzwjjeiwzrsy6xxlsahswldtq2jcfydq7qhopjctt327qlna.b32.i2p kaizushih5iec2mxohpvbt5uaapqdnbluaasa2cmsrrjtwrbx46cnaid.onion


Site logo image

<Home | Services | Blog | Price List | Canary | About | User Policy | Guides | FAQ | Contact>
<Account FAQ | Hosting | Service Management | Relays | Shell Accounts | ViewPVS | Virtual Private Servers>


I cook a delicious onion stew, without any chilli peppers.



Massive time fuckup

As those who keep up to date on this blog know, we have moved to better hardware. This was something to celebrate, however I forgot an important step in setting up. The hypervisor had never ahd its clock set, and the hardware was brand new. Thus, the time was out.

We can kind of blame Microsoft, the server time would have been right for the East Coast on the USA. Yet the hypervisor system was expecting the system time to be in UTC. So the clocks have been out this whole time, and one should blame me. I failed to consider this aspect of configuration.

The new system has a special server that does a TCP VPN to the Infantile relays. This tunnel will thus provide time, but it also gets DNS queries. I used to use tlsdate but it is depreciated, and on the old system time was kept in sync by the hypervisor when the stack boots.

Anyway, this is a big fuckup which could affect all kinds of things including databases. I hope that now I have resolved the issue that we can move forward.

If your database is trashed the good news is a I have a few weeks worth of daily backups. We can go back in time! Anyway support with all time-fuckup related issues is on the house.

Update: I had to restart the whole damn stack, and there were MySQL issues. Sorry if I fucked your site!







2020 Kaizu Shibata, server time 3:08:39 22/10/20 UTC

Powered by Kaizu's Picosite!, and nginx running on Gentoo Hardened.