Hello,
Unfortunately some security flaws have been discovered in the hypervisor
software we use (Xen) so we will need to patch and reboot everything
before the public release of the details on 5 March.
We will do this work in the early hours of the morning (UK time) between
Saturday 2 March and Monday 4 March. You should already have received an
individual email confirming the hour-long maintenance window specific to
your server(s). The actual work for each server is expected to take
10–30 minutes within that window.
As before we should be able to do a suspend/restore of your guest if you
have enabled that at:
<https://panel.bitfolk.com/account/config/>
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi,
For a long time I've been assuming that you prefer scheduled maintenance
to take place in the early hours of weekends so that there is less
disruption. But sometimes people say they don't prefer this, and I
realise I don't actually know what your preferences are.
So, please help me out, let me know:
https://twitter.com/bitfolk/status/1099260516579622912
(If you don't have a twitter account you can just let me know by direct
email off-list)
Thanks!
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi all,
I’m exploring the idea of using two VPSs on different hosts to implement some sort of failover mechanism. Is anyone here doing something similar, or have any recommendations?
Regards,
Chris
—
Chris Smith <space.dandy(a)icloud.com>
I have in the back of my mind that there's an email thread that may be
related to this, but I can't find it in my mail archives unfortunately -
it may even not be this list. Anyway...
I've just been looking to do a do-release-upgrade from Ubuntu 16.04 to
18.04 and come across a raft of error messages along the lines of:
Err http://apt-cacher.lon.bitfolk.com/ubuntu/gb.archive.ubuntu.com/ubuntu bionic/main Sources
403 Forbidden file type or location: /ubuntu/gb.archive.ubuntu.com/ubuntu/dists/bionic/main/source/by-hash/SHA256/0e05b8e93cbdfe5d41306e9d34c893fa23f3087a58c637b882cb0f133375a133 [IP: 2001:ba8:1f1:f079::2 80]
My Google-fu is failing me at the moment as nothing I'm finding is quite
matching up, so I thought I'd see if the collective knowledgebase of
fellow Bitfolk folks had come across this.
One way around, I guess, would be to bypass the Bitfolk cache, but that
doesn't seem to make sense, particularly in the long run if the change
ends up needing to be permanent. Is there a change I can make locally,
or is it down to the Bitfolk cache itself, possibly waiting for a file
to be re-cached? I'm guessing it is likely related to recent updates to
apt.
--
Paul Tansom | Aptanet Ltd. | https://www.aptanet.com/ | 023 9238 0001
Vice Chair, FSB Portsmouth & SE Hampshire Branch | http://www.fsb.org.uk/
=============================================================================
Registered in England | Company No: 4905028 | Registered Office: Ralls House,
Parklands Business Park, Forrest Road, Denmead, Waterlooville, Hants, PO7 6XP
Hello,
Here is an example of me using the Xen Shell rescue environment to
diagnose and fix a booting issue with a customer's VPS.
Sorry about the long pauses. It's recorded in realtime, I needed to look
some things up, and you can't edit an asciinema.
https://asciinema.org/a/RXb6KGR7aXGZwRhfQkeUi8RUj (7m47s)
For those wanting to avoid spoilers, the next email is going to contain
some comments about what the problem here actually was.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
