Ubuntu 22.04 LTS to Ubuntu 24.04 LTS upgrade

Just to let anyone interested know that on the 29th August 2024, Ubuntu released the 1st update of 24.04.1 LTS, and servers can be upgraded from 22.04 LTS to 24.04 LTS via terminal.

The JumpCloud website has a pretty good “how to” section, if anyone is interested.

How to Upgrade from Ubuntu 22.04 LTS to Ubuntu 24.04 LTS - JumpCloud)

I have updated 6 servers so far (all using Virtualmin gpl), and each upgrade has taken about 20-30 minutes. I always back up offsite, just in case there are issues, but no need to re-install so far.

There were four issues I came across after the install’s were completed, and all were easily corrected, either via terminal, or in Virtualmin.

The 1st issue was that the Cyrus SASL Authentication Server would not start. This
needed to be linked between postfix and saslauthd. This was fixed in terminal by using the symbolic link as follows:
ln -s /var/spool/postfix/var/run/saslauthd /var/run/saslauthd
In the Virtualmin Servers status area, restart the SASL server, and at least for all six of my upgrades, the SASL server restarted with no issues.

The 2nd issue was that permissions need to be set/checked for the following folder (folder only)
/var/spool/postfix/var/run/saslauthd and set permissions to 0755 (- -rwxr-xr-x) (The folder permissions were initially set at 0710, which only allowed root access, not group access, such as postfix/sasl. Ubuntu 22.04 LTS had this correctly set to 0755)

The 3rd issue is not really an issue, but after the install, in the system
settings area of Virtualmin re-run the “re-check configuration”. At least for me, all
was well except I needed to setup the virtualmin repos again (version 24.04
tweeked the repos area, so old setup did not work)
From terminal, just type:
virtualmin setup-repos
This quickly re-linked the virtualmin repos.

And, the last issue was that on a few of my older servers, the FPM portion of PHP was not found. This was remedied by going to to the PHP Options section under Web Configuration, and re-saving. So if your web page is not accessible after upgrade, this may be why.

All in all, a fairly smooth transistion to the new kernel. Supposedly this LTS version is good for 12 years, instead of the usual 5.

7 Likes

To add to this, upgrading always disables all third-party repositories. They’re not just picking on our repos.

2 Likes

Just wondering at what point the virtualmin team advises moving up from 22.04 to 24.04 releases?

Why would/should they do that?!

1 Like

Why should they?
This is above and well beyond the team’s responsibility.
It is your/your company’s/your organisation’s decision.
Just as is the decision on which box, VM supplier, OS it is run on.

I for one will upgrade my VM OS when I/my company choose to do so.

Before 22.04 reaches end of life. This is always the same answer for all distros. Don’t run EOL distros, and if you want newer software use a newer distro.

Personally, depending on the complexity, in the last year of support for the LTS version you are on, start planning and upgrade your server with no less than 6 months left on your LTS version.

What i meant more so was to confirm virtualmin is ready for 24.04 and that the team recommends using 24.04 in a stable production environment. There was a time when 22.04 wasnt yet on the grade A supported os list even.

Obviously don’t run out of date software. My interests were based in wanting to know when it is safe to move forward with what would be a smooth (as smooth as upgrades can go - murpheys law not withstanding) and hopefully tested transition by the virtualmin team before they signed off on supporting that transition for others.

You mean, is there a list of verified and working Grade A OS so you can then decide Virtualmin is ready for the upgrade.

You mean OS Support | Virtualmin — Open Source Web Hosting Control Panel ?
But as a side note I have a vps that does nothing just my POC server which I am going to do a distribution upgrade to see how virstualmin handles it . I would guess the repros will need turning back on but I hope no serious errors

Brace yourself getting hit with a super stupid question… It definitely is me sitting in my pitch-black office long after the stroke of midnight wondering: Where the heck did he restart Cyrus from within Virtualmin?

Please, enlighten and release me from being my own brain fart’s hostage and point me into the right direction… Please!

I’ve seen this table, not only once. And I do recall that I even started one or another service there.

The table was collapsed in front of me - not a good excuse, I know, and a clear sign to go to bed immediately, crying myself to sleep and hoping this evidence of stupidity will magically vanish into thin air.

This is sooooooo embarrassing!!!

Webmin also allows you to restart any service.

1 Like

Update to 22.04 LTS to 24.04 LTS Upgrade:

The info originally posted allowed for a successful upgrade from Ubuntu 22.04 LTS to 24.04 LTS.

What I found was that the SASL Authentication Server would still not automatically start after a reboot, so I checked into this a bit further.

What I discovered is that the upgrade from 22.04 to 24.04 did not create a key directory and associated file for the new 24.04 LTS SASL server configuration.

In the /etc/systemd/system directory create a new directory called saslauthd.service.d (0755 permissions). Within the new directory, create a new file called override.conf (0644 permissions). Open the file and enter the following info:
[Service]
PIDFile=/var/spool/postfix/var/run/saslauthd/saslauthd.pid

Save the file.

In the Webmin tab, under System, Bootup and Shutdown, scroll down to saslauthd.service, click on it, and make sure that this service is set to start at boot time.

Save settings.

Once the service is started, you should be good.

To be sure I rebooted my system to verify the SASL Authentication server came online without any further intervention. This worked for my system.

4 Likes

Thanks for your notes which have been of great assistance.

With regard to the SASL Authentication Server and your notes followed above, I did not reboot then system again but in order to get the service started I had to:

systemctl daemon-reload

before the service started. I also made sure that I had checked that the service would start at boot when I next rebooted the system.

2 Likes

Thank you very much. Very well described. I’m sure Ubuntu fans will all appreciate it.

Maybe @Joe can temporary pin this topic ?

1 Like

@ingram : Thank you so much. This post exactly described the issues I noticed after the upgrade, except for the php bit.

To add: I have had one issue not described here, but for those who (like me) use SSH with key based authentication for backups (in my case to a synology NAS): If you encounter the issue that all of a sudden the backup fails with the message “subsystem request failed on channel 0” there is a simple fix for this.

Go to Virtualmin > System settings > Virtualmin configuration > Backup & Restore > Additional parameters to SSH and SCP, and add -O (letter O) to the field.

2 Likes

As I can’t edit the previous reply:

I have checked the backup, and it appears to fail on the cleanup stage. Backups are successfully created, but the cleanup phase shows: ... failed to list directory via SSH : Invalid multiplex command.

The relevant part of the log:

2 servers backed up successfully, 0 had errors. 7 Virtualmin configuration settings backed up successfully.
Backup is complete. Final size was 929.8 MiB.

Deleting backups from /volume1/backup/<backup dir> on SSH server host.example.com matching .*-.*-.* older than 7 days ..

.. failed to list directory via SSH : Invalid multiplex command.

I’ll open a new post for this, but for those who find my reply, it’s not solved entirely, but I’ll leave it here as it at least solves not having a backup at all.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.