Debian 11 (bullseye) now supported for self-install and new orders

List overview All Threads
Download

newer

older

Broken Courier SSL after upgrade...

Routing issues?

Andy Smith

16 Aug 2021 16 Aug '21

2:14 p.m.

Hi, The new stable release of Debian, bullseye, was released over the weekend: https://bits.debian.org/2021/08/bullseye-released.html This is now supported for self-install: https://tools.bitfolk.com/wiki/Using_the_self-serve_net_installer#Debian by doing "install debian_bullseye", and also of course as a new order. If upgrading in-place from buster to bullseye please make sure to read the release notes as there are a few things to be aware of: https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.… There aren't any known BitFolk-specific issues with bullseye, though we do suggest that if you're running buster or beyond that you do so in PVH mode: https://tools.bitfolk.com/wiki/PVH I *think* it is still possible to install the new testing release (bookworm) by doing "install debian_testing" but we have to check that and fix it if necessary, which will happen later this week. If you're desperate to do a clean install of Debian testing and you find that "install debian_testing" doesn't work then I recommend installing bullseye and doing an in-place upgrade from there (will be almost identical right now). Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

Attachments:

signature.asc (application/pgp-signature — 195 bytes)

Show replies by date

Andy Smith

17 Aug 17 Aug

noon

Hello, On Mon, Aug 16, 2021 at 02:14:05PM +0000, Andy Smith wrote:

...

The new stable release of Debian, bullseye, was released over the weekend: https://bits.debian.org/2021/08/bullseye-released.html This is now supported for self-install: https://tools.bitfolk.com/wiki/Using_the_self-serve_net_installer#Debian by doing "install debian_bullseye", and also of course as a new order.

A couple of people have hit this issue: You need to be using at least version v1.48bitfolk64 of the Xen Shell to see the "debian_bullseye" option. As the Xen Shell remains running when you disconnect, if you reconnect then you may be seeing an older version of it. You can check the version by typing "help". You can force a new version to run by exiting properly from every window you have open to it and then connecting again. The version immediately previous to this one did not have "debian_bullseye" as an option, but it did have "debian_testing", which at that time was the same as bullseye, so if you don't want to log out then I think that doing "install debian_testing" from there should still het you an install of Debian 11 bullseye. But I haven't tested this myself. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Conrad Wood

18 Aug 18 Aug

7 a.m.

On Tue, 2021-08-17 at 12:00 +0000, Andy Smith wrote:

...

Hello, On Mon, Aug 16, 2021 at 02:14:05PM +0000, Andy Smith wrote: > The new stable release of Debian, bullseye, was released over the > weekend: > > https://bits.debian.org/2021/08/bullseye-released.html > > This is now supported for self-install:

FWIW, I upgraded 5 machines yesterday. It wasn't as straight forward as debian upgrades usually ARE IMHO. Issues I ran into 1) exim4 configuration broke. paths such as /srv/mail/{$domain}/${local_part} no longer work (and probably should never have ;) ). 2) 2 out of 5 machines failed to reboot until I used the console to disable selinux (kernel parameter selinux=0). I am not certain how to re-enable it and make it reboot ;( 3) cgroups v1 no longer supported (I had some old code that broke due to that) essentially /sys/fs/cgroup/.. no longer supported During the upgade ssh connections don't work (connection refused) for some time (>1 hour in my case), which is a bit scary. I used telnet- over-vpn for some machines. Hope that helps others to avoid the trouble I ran into. Conrad

Mike Zanker

7:17 a.m.

Conrad Wood wrote on 18/08/2021 08:00:

...

I upgraded 5 machines yesterday. It wasn't as straight forward as debian upgrades usually ARE IMHO. Issues I ran into 1) exim4 configuration broke. paths such as /srv/mail/{$domain}/${local_part} no longer work (and probably should never have ;) ).

Thanks for the heads-up! I'm expecting exim4 config to break as it has been mentioned a few times in various fora and there's also a section in the release notes about it. I've only made minimal changes to the standard config so I'll be using the new default config and merging my few changes. Cheers, Mike

Andy Smith

10:28 a.m.

Hello, On Wed, Aug 18, 2021 at 08:00:18AM +0100, Conrad Wood wrote:

...

During the upgade ssh connections don't work (connection refused) for some time (>1 hour in my case), which is a bit scary. I used telnet- over-vpn for some machines.

This is mentioned in the release notes: https://www.debian.org/releases/bullseye/mips64el/release-notes/ch-informat… I'm not sure what the proper procedure would be to upgrade openssh-server first. I guess download the .deb file manually and install it before doing the "apt upgrade"? If this is the relevant bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990069 then it seems like ssh must be restarted after a new libc is installed, so I don't see how upgrading ssh first avoids that, but maybe I misunderstand. The fix at the end of that bug is to glibc making it aware that it has to restart ssh: * debian/script.in/nsscheck.sh: restart openssh-server even if it has been deconfigured during the upgrade. Closes: #990069. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Andy Bennett

10:37 a.m.

Hi,

...

Has anyone tried doing an `apt-get update` to the new release and then `apt-get intall openssh-server`? That's what I was expecting to have to do but if it forces a libc upgrade as well then perhaps that makes it difficult to restart any other binaries on the machine whilst the upgrade is in progress?

...

If this is the relevant bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990069 then it seems like ssh must be restarted after a new libc is installed, so I don't see how upgrading ssh first avoids that, but maybe I misunderstand. The fix at the end of that bug is to glibc making it aware that it has to restart ssh: * debian/script.in/nsscheck.sh: restart openssh-server even if it has been deconfigured during the upgrade. Closes: #990069.

Best wishes, @ndy -- andyjpb(a)ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF

Andy Smith

11:27 a.m.

Hello, On Wed, Aug 18, 2021 at 11:37:02AM +0100, Andy Bennett wrote:

...

I will probably have time to test it in a couple of days or at least over the weekend. Anyway, it is worth keeping a connection open to the Xen Shell for the console. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Andy Smith

10:33 a.m.

Hello, On Wed, Aug 18, 2021 at 08:00:18AM +0100, Conrad Wood wrote:

...

1) exim4 configuration broke. paths such as /srv/mail/{$domain}/${local_part} no longer work (and probably should never have ;) ).

Oh, and this one also in the release notes: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information… Looks like that is the taint checking, which can be temporarily disabled. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Conrad Wood

11:54 a.m.

On Wed, 2021-08-18 at 10:33 +0000, Andy Smith wrote:

...

Hello, On Wed, Aug 18, 2021 at 08:00:18AM +0100, Conrad Wood wrote:

1) exim4 configuration broke. paths such as /srv/mail/{$domain}/${local_part} no longer work (and probably should never have ;) ).

Yes, I should have mentioned - all the issues I mentioned are described in debians upgrade issues list. It is just me being spoilt by the usual smoothness and backwards compatibility by debian upgrades that caught me out.

982

days inactive

984

days old

users@mailman.bitfolk.com

Manage subscription

8 comments

4 participants

tags (0)

participants (4)

Andy Bennett
Andy Smith
Conrad Wood
Mike Zanker