BitFolk Users January 2022

users@mailman.bitfolk.com

7 participants
9 discussions

What do you consider the lifetime of an OpenSUSE Leap release to be?

by Andy Smith

Hello, Owing to some fine work by a customer, we will soon be able to list OpenSUSE Leap as supported: https://tools.bitfolk.com/wiki/User:Moggers87/Installing_Opensuse This prompts a perhaps somewhat philosophical question: In the context of our supported distros bit: https://bitfolk.com/techspec.html#toc_2_Available_Linux_distributions what would you consider the supported lifetime of OpenSUSE Leap to be? I don't know very much about OpenSUSE. From what I have been able to gather: - The current release is 15.3 - This was released 2021-06-30 - Support lasts for 6 months after the next minor release - "Support" means no major updates to packages, just security fixes or serious bugs fixed - A minor release roughly every year - So 15.3 support ends around December 2022, as 15.4 will be released around 2022-06 - In-place upgrade is supported to next minor release (or even through major releases?) - The last 15.x minor version is expected to be 15.5 in 2023 supported until some time in 2024 Do you consider that EOL 2022-12, or EOL 2024-XX? Since you HAVE to do an update or else don't get security fixes, I think that is EOL 2022-12. That does make OpenSUSE Leap look like a little worse option though unless you fully understand this. On the other hand, I'm not sure I can truthfully state that its EOL would be 2024-XX as that may lead someone who does not do the research to think they can only do package upgrades all the way out to 2024. So, erring on the side of caution, it should be listed as 2022-12, right? (The other entries are also complicated by the different tiers of support, and I continue to remain conflicted over listing Ubuntu's ESM which is free but requires registration.) Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

2 years, 11 months

Rescue VM updated

by Andy Smith

Hi, The Rescue VM needed updating as its 4.19.x kernel was getting too old, e.g. not able to mount XFS filesystems as created by CentOS Stream 8 and Fedora: https://tools.bitfolk.com/redmine/issues/206 It has now been updated to a Debian 11 (bullseye) system with bullseye-backports (5.15.x) kernel. I've done basic testing but please do let us know if you encounter any difficulties using it. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

2 years, 11 months

Debian users should replace ftp.uk.debian.org with deb.debian.org

by Andy Smith

Hi, We decided to make our Debian installers use the mirror host of deb.debian.org instead of ftp.uk.debian.org. This was done initially just to make the /etc/apt/sources.list look the same as the many examples in Debian's documentation. However I did then notice that at some point in the last 15 years (!) ftp.uk.debian.org has moved from London to Manchester and is now about 12ms away from BitFolk. The nearest Fastly instance for deb.debian.org is about 0.9ms away, so it's also faster to use that one. By default we do set it up to use our apt-cacher, so every URL in there is prepended with: http://apt-cacher.lon.bitfolk.com/debian/ These days it maybe has questionable benefit, when package updates will only be a small fraction of your data transfer quota, but we'll carry on using it for now. Anyway, whether or not you use the apt-cacher, you can make this switch by just doing a substitution of "ftp.uk.debian.org" with "deb.debian.org". There are still some pages on the wiki that will refer to ftp.uk.debian.org; if you spot any please feel free to update them to say deb.debian.org. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

3 years

Remaining 32-bit PV guests will be switched to pvshim on Tuesday 18 January

by Andy Smith

Hi, TL;DR: The ~30% of you still running 32-bit PV guests are going to have your config changed in a month. We've tested that on many different configurations and haven't had a problem yet but it's always possible something could go wrong, and if so you'll only find out at the next boot. If affected we recommend you instead make the change yourself at a time convenient to you. This email is only relevant to you if you're still running in 32-bit PV mode. Most customers run 64-bit. If you type "uname -m" in your VM then it will say "amd64" for 64-bit and "i686" for 32-bit. It also says it on the summary page of: https://panel.bitfolk.com/account/ You can stop reading if you're already running as 64-bit, or in PVH mode. We haven't got a simple way to check if you are PVH mode because the intention is that eventually will be a detail you don't have to care about (all VMs will be PVH and that has been the default for over a year now). You can for now log in to the Xen Shell and type "virtmode" and it will tell you. So if that says "PVH" you can also stop reading. For several years now we have been trying to encourage customers running 32-bit PV mode guests to switch to 64-bit and / or PVH mode. There are many reasons for this but the most pressing one is that it's not possible to fully protect 32-bit PV guests against the various already known speculation attacks (nor probably new ones that will be discovered). About 30% of the customer base still runs 32-bit PV mode guests even though the default has been 64-bit since about 2012. We are clearly not going to be able to force everyone to switch in a timely manner so we have been testing a different way of running legacy 32-bit PV mode guests. That testing has gone well - there haven't been any issues - so we're going to convert all remaining 32-bit PV mode guests to that configuration on Tuesday 18 January 2022. Since it's not possible to test every permutation of installed guest though, we can't rule out there being a problem, and that problem will only manifest at your next boot. If you'd like to make the config change ahead of time here is how: 1. Log in to your Xen Shell. More info: https://tools.bitfolk.com/wiki/Xen_Shell 2. Make sure the version in the "help" command is at least this: xen-shell> help xen-shell v1.48bitfolk66 The Xen Shell stays running after you disconnect so it is possible to be running an older version. If it is older, "exit" out of every window until it logs you out, then log in again. 3. Use the "arch" and "virtmode" commands to confirm that you are currently running in 32-bit PV mode: xen-shell> arch Your current install architecture is: i686 xen-shell> virtmode Your current virtualisation mode is: PV 4. Use the "arch i686" command to force a switch to i686 (32-bit) architecture again. This will update your config to use pvshim. 5. Use the "shutdown" command to shut your guest down. 6. Use the "boot" command to boot it again. It should boot pretty much the same as before. If it does not, then you will likely not be able to get it to boot again yourself and will need to put in a support ticket. This change will be made for all remaining 32-bit PV mode guests on Tuesday 18 January, without further testing, as that would involve forcible reboot. If you do want to take some action about this here are some things you could do, in order of best choices to worst choices: a) Ask for a new "migration VPS" which would be an empty account that you can do a new install into (which would be 64-bit PVH as that's the default): https://tools.bitfolk.com/wiki/Migrating_to_a_new_VPS b) Upgrade your kernel past 4.19.0 and make sure you're running grub-pc (not legacy Grub) as bootloader, with a /boot/grub/grub.cfg file, then switch to PVH mode. c) If running at least Debian 7 (wheezy) or comparable age Ubuntu you can install an amd64 (64-bit) kernel even while everything else is 32-bit. That turns your VM into a 64-bit PV guest. Follow these CrossGrading instructions only as far as installing and booting into the new kernel: https://wiki.debian.org/CrossGrading d) Do nothing and let us switch you to using pvshim. Your guest is still insecure and running with reduced performance compared to 64-bit but this only then affects you. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

3 years

Automated card payments now available

by Andy Smith

Hello, There is now support for saving payment card details for future automated charging. To save card details please see: https://panel.bitfolk.com/account/billing/ If you already have automated payments set up through Direct Debit or PayPal and want to switch to card payment, you will need to cancel that arrangement first, which you can also do from the above page. We have accepted one-off card payments through Stripe since October 2013, and it has been a regular request to enable the saving of card details so that they don't have to be input each time there is an invoice. This has finally now been done. This is a minimally working implementation. I expect once it sees greater use there will be some suggestions for improvement. Please make these on our feature tracker at: https://tools.bitfolk.com/redmine/issues/202 One-off card payments will remain available for those who prefer to pay that way. More about supported payment methods: https://tools.bitfolk.com/wiki/Payment_methods Thanks, Andy BitFolk Ltd -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

3 years

Volunteers sought to help test out Stripe continuous credit card authority

by Andy Smith

Hi, I am working on Stripe continuous credit card authority at the moment, i.e. you give your card details to Stripe and they let BitFolk charge what it wants, when it wants, so as to enable automated card payments. I will soon need some volunteers to help test it out more thoroughly. There will also be UI aspects I need feedback on. If you would be interested in helping out, please could you contact me off-list? Ideally you would: - be on a monthly contract - not mind being charged a bit early - it will renew your service early (once it works properly) - not be using any other automated method like Direct Debit or PayPal subscription, as those would have to be cancelled first. In the event of any incorrect charge I will just refund it to your card again. There might be some form of free service bonus for helping out, though we will not talk about that for some weeks as I'll want to get it all working first. After it's initially working in its most primitive form we will discuss improvements to it on the tracker at: https://tools.bitfolk.com/redmine/issues/202 If you are interested in the progress of it, whether or not you are able/willing to help, you may wish to add yourself as a watcher of that issue to receive email updates. Stuff from there also ends up here: https://tools.bitfolk.com/redmine/issues/202 Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

3 years

Buying NVMe Disks

by Samuel Bächler

Dear all, I need to buy NVMe disks for a HP DL365 server. [1] They will be used as storage for lxd (linuxcontainer)? Can anyone recommend any? Or do you know any trustworthy site with reviews? Regards, Sam [1] https://www.hpe.com/psnow/doc/a50002558enw.html

3 years

Any Oracle DBAs on the list?

by Murray Crane

Long story short, are there any "genuine Oracle DB admins" on the list? Many, many (many!) years ago, I "inherited" DB admining of SQL Server, Postgres and Oracle for my employer. SQL Server and Postgres are no problem at all, and thanks to a previous staff member that actually knew Oracle I've been able to get by in OraDB - he gave me a simple "cheatsheet" that worked until 12c released and multi-tenancy became a thing, and I've been able to tweak said cheatsheet for multi-tenancy for our very simple DB usage. But... I've now been tasked with adding an additional user to an Oracle schema/tablespace/database, and I can't for the life of me get it to "just work" like it does in SQL Server and Postgres. Happy to take this off-list at the earliest opportunity. Kind regards Murray Crane

3 years

A reminder for those upgrading 32-bit Debian guests

by Andy Smith

Hi, A reminder that if you have a 32-bit Debian guest that you are keeping up to date: The Linux kernel removed support for 32-bit PV guests at version 5.9, so it will not be possible for you to upgrade from Debian 10 (buster) to 11 (bullseye) without taking action. This was mentioned before, but since then there have been a few casualties anyway (seemingly-unbootable guests). https://lists.bitfolk.com/lurker/message/20210930.104643.2ab5f9c0.en.html As you can see, as long as you are running a kernel above 4.19.0 and are using grub-pc to boot, you can just switch to PVH mode. This isn't an issue for Ubuntu because no 32-bit support there at all for some time, nor for CentOS because no upgrades between major releases there either. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

3 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

BitFolk Users January 2022