JosKlever
Verified User
You don't need a clean install, but can use the Elevate procedure as documented on https://almalinux.org/elevate/
AlmaLinux 10 support
- Thread starter JosKlever
- Start date
zEitEr
Super Moderator
My DirectAdmin setup is fully configured, and everything is ready.
Would it be okay if I used the following commands?
systemctl restart directadmin
systemctl restart lsws
imunify360-agent restart
cd /usr/local/directadmin/custombuild
./build update
./build php n
Active8
Verified User
- Joined
- Jul 13, 2013
- Messages
- 1,815
Thanks for your response.
I asked because I wanted to make sure everything (DirectAdmin, LiteSpeed, Imunify360, and my custom PHP builds 8.3 / 8.4) would run smoothly after upgrading from AlmaLinux 9 to 10 using ELevate.
I understand that the upgrade process already rebuilds the core system with all installed packages, but since I have some manually compiled PHP versions and LiteSpeed integrations, I thought running:
cd /usr/local/directadmin/custombuild
./build update
./build php n
./build rewrite_confs
after reboot could help re-link PHP with the new system libraries just to be safe.
So, basically I just wanted to double-check whether running those commands after the OS upgrade is harmless or unnecessary.
zEitEr
Super Moderator
Thanks both @Active8 and @zEitEr for clarifying!
Just to explain my situation a bit better — I’m running a personal DirectAdmin setup with LiteSpeed, Imunify360, and custom PHP builds (8.3 / 8.4).
Mail services like Exim/Dovecot/Rspamd are completely disabled, because my domains use external MX records (Namecheap).
The server is fully updated, CSF/firewalld disabled, and everything works perfectly on AlmaLinux 9.
My main goal after upgrading from AlmaLinux 9 → 10 via ELevate is to keep all configurations and integrations exactly the same, without doing a full rebuild of every component.
That’s why I was thinking of just running these after reboot:
cd /usr/local/directadmin/custombuild
./build update
./build php n
./build rewrite_confs
This should only recompile PHP and refresh configurations with the new system libraries — no reset, no configuration loss.
From what I understand,
build all d would indeed rebuild everything (including mail services I don’t use),
while build php n + rewrite_confs is enough to safely re-link PHP/LiteSpeed with AlmaLinux 10.
So I just wanted to confirm that in a non-mail, LiteSpeed-based personal setup, doing a light rebuild like this should be perfectly fine and safer than a full “build all d”.
Thanks again for your guidance — this discussion helped clear up the differences between “rebuild” and “reset” after an OS upgrade!
zEitEr
Super Moderator
da build all respects options.conf and skips disabled services, no options.conf will be effected. Run da build options to see which services are enabled, and only they will be re-compiled with the command. It is not reset of DA settings. For resetting DA options.conf one can use another command, it was never offered by me here.Thanks a lot for the clarification, @zEitEr — that makes perfect sense now.
So the correct and safe approach would be:
cd /usr/local/directadmin/custombuild
./build update
./build all d
This way I’ll have the latest CustomBuild scripts before rebuilding,
and since build all d respects my options.conf (mail disabled, LiteSpeed and PHP enabled),
it will only recompile the active services without touching my configs.
I’ll apply this later today after the upgrade to AlmaLinux 10.
Appreciate your help — that explanation really cleared every
thing up.
[ELevate] AlmaLinux 9 to 10 Upgrade Failed – Mixed Repositories, RPM DB Rebuild, and Leapp Errors
Hello everyone,
I’ve been trying to upgrade my DirectAdmin server from AlmaLinux 9.6 (Sage Margay) to AlmaLinux 10 using the ELevate / Leapp tool, but the process became very complicated and eventually failed.
Here’s a summary of what happened:
At this point, I decided to stop the upgrade and restore from my AlmaLinux 9 snapshot, because it’s no longer safe or stable to continue.
The server technically works, but it’s not a clean upgrade environment anymore.
Has anyone here successfully upgraded DirectAdmin + Imunify360 servers from AlmaLinux 9 → 10?
If yes, what was your exact step-by-step process?
Did you have to manually create AlmaLinux 10 repos, or did ELevate handle that automatically?
Any guidance or working example would be appreciated — I’d rather prepare a clean 9.6 → 10 migration path than risk breaking production again.
Thanks in advance!
– Can
Hello everyone,
I’ve been trying to upgrade my DirectAdmin server from AlmaLinux 9.6 (Sage Margay) to AlmaLinux 10 using the ELevate / Leapp tool, but the process became very complicated and eventually failed.
Here’s a summary of what happened:
- I started the upgrade with the usual leapp preupgrade and leapp upgrade steps.
- The first problem appeared with duplicate YUM/DNF repositories and unsupported upgrade warnings.
- I manually disabled several Imunify360 rollout repos and created custom .repo files for AlmaLinux 10 BaseOS and AppStream.
- DNS resolution failed multiple times during the process (Curl error 6 - couldn’t resolve host repo.almalinux.org), so I had to manually add Google DNS entries to /etc/resolv.conf.
- Later, the RPM database got corrupted and I had to rebuild it manually using:
systemctl stop packagekit
rm -f /var/lib/rpm/__db*
rpm --rebuilddb -v
- After that, dnf started working again, but the Leapp upgrade stopped several times with messages like:
- “Upgrade is unsupported”
- “Unable to install RHEL 10 userspace packages”
- “A YUM/DNF repository defined multiple times”
- “Actor rpm_scanner unexpectedly terminated with exit code 1”
- Even after running with:
LEAPP_UNSUPPORTED=1 LEAPP_UNSUPPORTED_INHIBITOR=1 LEAPP_DEVEL_SKIP_RHSM=1 leapp upgrade --reboot
…the system never actually created the leapp-upgrade initramfs, and the GRUB menu didn’t show any upgrade option.
- After several attempts, the system became a hybrid between EL9 and EL10 packages — some updated (rpm, python3, systemd) but others still from EL9.
Network and repository configurations were partially broken, and dnf metadata conflicted.
At this point, I decided to stop the upgrade and restore from my AlmaLinux 9 snapshot, because it’s no longer safe or stable to continue.
The server technically works, but it’s not a clean upgrade environment anymore.
Has anyone here successfully upgraded DirectAdmin + Imunify360 servers from AlmaLinux 9 → 10?
If yes, what was your exact step-by-step process?
Did you have to manually create AlmaLinux 10 repos, or did ELevate handle that automatically?
Any guidance or working example would be appreciated — I’d rather prepare a clean 9.6 → 10 migration path than risk breaking production again.
Thanks in advance!
– Can
JosKlever
Verified User
@Can It sounds like you have modified so much, it has become a mess. This isn't a DirectAdmin issue though, so you should probably be able to find more help on https://forums.almalinux.org
This topic is about the support of AlmaLinux 10 and DirectAdmin, not for upgrading AlmalLinux.
This topic is about the support of AlmaLinux 10 and DirectAdmin, not for upgrading AlmalLinux.
I had taken a snapshot from Hetzner, so I quickly rolled back to it. I’ll try my luck on the AlmaLinux forum instead. Thanks a lot! I’ll stick with AlmaLinux 9 for now —
