OS type and version: AlmaLinux 9.7 (Moss Jungle Cat)
Webmin version: 2.621
Virtualmin version: 8.0.0 GPL
Webserver version: Apache 2.4.62
Related packages: virtualmin-config-7.0.24, dnf/yum (standard EL9)
Issue summary:
Attempting to upgrade from Virtualmin GPL to Pro.
The upgrade fails with a 404 error when downloading repo metadata:
Status code: 404 for https://[serial:key]@download.virtualmin.com/repodata/167
b21bcc2e939a3e27b4f85c4008d5b57221e91a3c79d14f6098005169e1248-primary.xml.zst
The repomd.xml downloads successfully but references a primary.xml.zst file
that returns 404. This appears to be a CDN/repo sync issue.
It started working because something I did on the backend (plus the dnf clean all after that backend change). But, merely doing dnf clean all won’t work by itself if it persists beyond the first attempt.
It is not permanently fixed. Ilia will address the root cause tomorrow, it’s really late where he is.
I leaned on claude code for help on this one with an additional error we got during install and my install is working now. Asked claude to write it up…
…
Thanks for the CDN fix! For anyone else hitting this, we encountered two
separate issues:
Solution: sudo dnf clean all (forces fresh metadata download after CDN
flush)
Issue 2: Package file conflict during Pro install
Symptom:
Error: Transaction test error:
file /usr/libexec/webmin/at/module.info from install of
webmin-at-2.621-1.noarch
conflicts with file from package webmin-2.621-1.noarch
Cause: The webmin-at module is included in the main webmin-2.621-1 package
but also being installed as a separate dependency
Ah, I was afraid we’d still have some issues with the upgrade to the minimal Webmin install in the Virtualmin 8 repo.
@Ilia this is another issue we need to sort out before nudging Virtualmin 7 users to cross-grade to the Virtualmin 8 repos…I’m not sure I understand what’s happening here. Why would webmin-at be depended on, if the Webmin package already has the at module?
And, there’s no harm in using either Webmin package, though I think the the minimal Webmin package got pushed out a bit prematurely, as there are a lot of little surprises waiting for folks in this change.
You may find some modules you were using are removed if you switch to the new package from the Virtualmin 8 repo.
I actually fresh installed 8 GPL today thinking that switching to pro was a basic unlock I could do from within it (cpanel migrant here) So this is from 8.0.0 GPL to 8.0.0 Pro…
Yes, you can upgrade from within Virtualmin GPL. It’s a form where you fill in the serial number and password.
You just ran into an intermittent problem with our new repos (or rather, the CDN that is recently in front or our new repos). We’re working on sorting that out.
I assumed a cross-grade between Virtualmin 7 and Virtualmin 8 repos, because there should only be a minimal Webmin package in the Virtualmin 8 repo, so I don’t know why you’d get the error about webmin-at. That’s a bug, it’s just not a bug I understand (Ilia is working on the new smaller Webmin package and I haven’t had time to look at it to see how it works and what got stripped out).
@Joe, I’ll take a closer look and update this ticket with progress.
@Sologretto, Just to make sure, did you install the GPL version a while back using the old GPL repo, and now you’re trying to upgrade through the Virtualmin UI, but it failed, right?
And you still ran into that issue with webmin-at with the new repo enabled? That shouldn’t happen. Did you try any intermediate fixes to repair the repos, for example, or did you do make any other manual changes or ran any commands?
As far as I know I simply installed the 8.0.0 GPL. I messed around a bit trying to get email working cause it’s sending ok, but not receiving (still on my todo list), but I don’t recall installing software or packages.
