Dist-upgraded server 20.04.6 => 22.04.1 => 24.04.1 - Apache problems....

[Bo Berglund]

On Sat, 14 Dec 2024 16:06:47 +0100, Bo Berglund <bo.berglund at gmail.com> wrote:

>On Sat, 14 Dec 2024 15:16:21 +0100, Oliver Grawert <ogra at ubuntu.com> wrote:
>
>>Hi,
>>Am Samstag, dem 14.12.2024 um 14:51 +0100 schrieb Bo Berglund:
>>> What is it it cannot "load" and why does this happen folowing a dist-
>>> upgrade?
>>
>>it can not load php8.1 ... 
>>
>>see:
>>
>>https://askubuntu.com/questions/1500503/what-php-version-s-will-be-officially-supported-by-ubuntu-24-04
>>
>
>
>Thanks,
>I did not know thath the upgrade process would leave stop blocks in its path...
>Apparently the now non-existing php8.1 was still set in apaches configuration
>files.
>
>So I solved the problem in the following way:
>
>sudo a2dismod php8.1
>sudo a2enmod php8.3
>sudo systemctl restart apache2
>
>Now it works at least apache is running...
>
>I don't know yet if theree aree other side effects of the upgrade (2-step in the
>same operation).
>
>But both my webserver and the plugged in Subversion server work. :-)
>

But there is another thing I discovered and that is that after the release
upgrade the grub menu is not correctly updated!

I have repeatedly run the sudo update-grub command and yet the grub menu insists
on only showing the Ubuntu 20.04 entry for the now upgraded server!
Why is that so?

If I select it the server starts OK and it is the 24.04.1 version running.

I have googled to no end and seen variations like (i.e. not sudo update...):

sudo su
update-grub
exit

Like this:

$ sudo su
# update-grub
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.0-50-generic
Found initrd image: /boot/initrd.img-6.8.0-50-generic
Found linux image: /boot/vmlinuz-5.15.0-126-generic
Found initrd image: /boot/initrd.img-5.15.0-126-generic
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot
entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 20.04.6 LTS (20.04) on /dev/nvme0n1p5
Adding boot menu entry for UEFI Firmware Settings ...
Found memdisk: /boot/memdisk
Found iso image: /boot/images/gparted-live-1.6.0-10-i686.iso
# exit

Where could I set the correct name for the menu entry so it will be
recognizable?

Note: There are 4 "operating systems" involved here:
- Windows (want to get rid of thta but cannot)
- Ubuntu 20.04.1 Desktop
- Ubuntu 24.04.1 Server Shown as Ubuntu 20.04.6)
- GParted Live

NOTE:
After I have gotten this upgraded server settled with no observable problems
like the above, then I want to move the whole installation to a different PC
based on ASUS NUC 13 (to get a more capable server system with SSD drives etc
and also to get away from the Windows stuff and the Ubuntu Desktop I don't need
at all.
This probably means to use GParted to copy the involved partitions from the
server to the NUC disk and "somehow" fix the grub menu.
Can IO copy the EFI partition too or do I need to create it from scratch?


-- 
Bo Berglund
Developer in Sweden