1518: I'm in the middle of the thyestes upgrade, and running into some problems, I think with systemd configuration causing it to reboot before bringing up the network interface. I have a network serial console so currently assuming I can fix this via systemd rescue (or, worst case, emergency) without requiring a manual intervention from the hosting company, which would of course take much longer.
1620: somewhat struggling with the OVH rescue options right now, because their rescue system boots with a French keyboard and also the root password for the rescue system isn't coming through to gmail for some reason. I did get thyestes to boot once or twice, suggesting that something weird is going on with systemd (what a surprise), but I'm hopeful I can reboot it now into systemd rescue and maybe figure out what's going on. (Remembering to disable OVH monitoring so it won't auto-reboot the machine should help.)
1706: turns out the entire problem was that systemd runs very very slowly if you put the kernel console parameters in a particular order (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763601). Changing that fixes it. I'm going to delay the upgrade again, but try to complete the network interface renaming to consistent names today.
Saturday, October 12, 2019
Thursday, May 08, 2014
I may have said that too soon…
Good news though, atreus was completely fine when I was able to get through to it. Happily backing things up, flushing out its disk cache. You know. Computer things.
ISP routing issues
atreus is currently unreachable at least for me, I believe due to planned maintenance on our ISP's routers which seems to be causing more significant problems than they previously anticipated. The maintenance window is planned to close midnight UK time (2014-05-08T23:00Z), so hopefully things will be back to normal by that point.
Wednesday, April 09, 2014
Atreus key fingerprints
Following Heartbleed, I've replaced the IMAP and SMTP certificates used on atreus. From now on it seems sensible to publish the fingerprints in a verifiable fashion. The key used to sign the statement below is on various keyservers; you should use normal PGP / WoT approaches to verify. (Ideally by finding me in person and verifying my identity.)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Atreus key fingerprints are currently (9th April 2014): imap: 23:F4:04:5F:9D:43:5E:1D:68:AD:6B:F6:1B:A6:62:94:C2:4E:8E:88 smtp: 44:03:75:76:EB:46:EF:90:0F:DB:41:C5:D9:59:71:96:F2:76:D9:EB ssh: 1e:5e:1f:45:5a:1b:9c:f9:89:6f:ec:e1:90:36:b7:ac -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTRT1VAAoJEHVoYzv6hIve+H4P+wY53qTxYJDRKeHERuT0gzKU XbRvy1STnBrl/jO0Jvwa52xMMNSAZ0mi+t6LIqn1JpyYvkx28pqWKptOTjNAYib0 kytk3JnbVERDkvM1PH6GkclGvxECa4h1Bv1HXtRTUxpAGGv1uuCj32PL6V0w0JAt ggi3XpzrtHz5Tv18SDp57ISWATw00Ck/BgH0J7pIZkDZrAbBk10zHSQTPj7aPa0j vG4Ddk3ZwluxUc+HswBUbs8itc+x55WegtSPNG1d369xyZ7unkfNU0ZCi0Uqp093 rydI7PQXt8peGWTMYXuWANv/CTrgEGkg9hsjCKMcD4mK5sD5YiPhWgR/e3MBJ/Dg vXSNUU3p8fNaXaoqt/EWu11hnS9AXHOQ8SSRn2stLDR+TT2slAwpgsfglAfyRWY4 ZevEEJLIt0kBb7fdn1L0b3TQG6kG0BRJ04e4qoUQ4hecrZVH0nLkdY2Bqm4pgsiz 7Qh3SDfJQDtrLgVjcRMaXDtrLQPA2VCo2zLmzUGJEbrQLLotZtP4hWmDx99A4hAt HAZ8w+6mEaZrQu72FggyTYNE5pW6i/2WC3M8SxZIPW+hANljglZo83uSKLMvXkBN Zr/X90JHtKrOq/yzhwQ0nftRFaMq+HwVgDVuE/xvC0m+tiSg4pLABtyfYuQP6td+ KjWJTwBHSihMT8TowMrH =QJHu -----END PGP SIGNATURE-----
Tuesday, September 10, 2013
atreus running again
For unknown reasons the first power cycle did nothing, ie left it down. Second one today fixed that. There are a few things I'm trying to improve uptime; there may be further downtime if I need to do anything drastic, but hopefully things will be better overall.
Monday, September 09, 2013
Unscheduled downtime
atreus is down again, suggesting a hardware problem. The ISP should reboot it fairly promptly, and I'll investigate further to try to figure out what's causing this :-(
Thursday, August 22, 2013
Monday, August 12, 2013
Subscribe to:
Posts (Atom)