| SYSTEM INFORMATION | |
|---|---|
| OS type and version | CENTOS 7 |
| Webmin version | 1.994 |
| Virtualmin version | 7.1 |
| Related packages | HTTPD |
How does one upgrade to httpd-2.4.6-99? And the moment I have 2.4.6-97.el7.centos.4. I did a yum update but it wasn’t there.
Thanks
Going outside of officially supplied/supported packages is always tricky. Most of your software is out of date and sticking with CentOS is going to be a problem. If you really need it then now might be the time to look at migrating off of CentOS.
Oh, I guess I missed an update. I’ll try to get it built and pushed soon.
1 Like
Thank you @Joe !
@ID10T do you mind explaining a bit more? I thought Centos 7 end of support is next year so until then they should be (and have been) releasing security patches?
They’re talking about installing random packages from elsewhere, which is not what you’re trying to do. And, yes, it’s a bad idea to install random packages from random folks on the internet.
I’m working on the update now, it should be in the repo in an hour or two.
1 Like
Should be in the repo now. At least for the /vm/6 repos. (If you’re still using the old Virtualmin 5 and before repos, you shouldn’t be, as they reached EOL something like a year ago.)
I don’t know the Centos 7 eco system. So, going outside of it is a bad idea for the most part. I didn’t realize the trusted repos were simply not up to date.
So, the implication was if it wasn’t part of the official CentOS 7 and you needed it, NOW would have been the time to move from CentOS, which, you may have to do anyhow.
The way Centos works is it keeps the same versions of software at the time it’s released, in this case Apache 2.4.6, but it patches its software with security releases. I’m not sure if it does with bugs but assume it does if something is broken. It then calls the release 2.4.6-99 for example. This way Centos claims to be a more stable OS which is why I chose it many eons ago.
In my case one of my customers did a security audit on their site which reported 2.4.6. I need to let them know it’s actually ok as it has all the security patches so the version is a red herring for their security report. Hence me raising this ticket because I noticed the patches were not up to date.
My server in this case is quite old! Over the years the way centos works annoyed me. So my newer servers use Ubuntu. But I still have these older servers. And Centos 7 is still supported until next year so I should be able to keep using it until then. I’m slowly moving websites across.
The main issue I have is with PHP. Centos won’t add new versions of PHP so that’s the bigger problem for me and why I moved to Ubuntu.
1 Like
Up until a couple years ago, we provided a custom build of Apache on CentOS (we stopped with the Virtualmin 6 for CentOS 8 release, but CentOS 7 still had it). It is identical to the CentOS/RHEL package, except it changes suexec_docroot to /home.
No install since Virtualmin 7 was released would have that custom Apache package (but, no one should have been installing CentOS 7 once 8 was available, so it should really be no install since CentOS 8 support was added).
OP has a CentOS 7 system installed more than a couple years ago, so they have a custom Apache package, and they need that custom Apache package if they are using any suexec execution mode applications. (And, if they aren’t, they could switch to the OS standard Apache packages without risk, as it is only needed when using suexec…FPM doesn’t need it.)
1 Like
Thanks a lot. I cant see any yum updates for it. So I wonder if I have the old 5 repo you mentioned. How would I find out? I have virtualmin.repo with the following in it:
[virtualmin]
name=RHEL/CentOS/Scientific $releasever - $basearch - Virtualmin
baseurl=http://GPL:GPL@software.virtualmin.com/gpl/rhel/$releasever/$basearch/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
[virtualmin-universal]
name=Virtualmin Distribution Neutral Packages
baseurl=http://GPL:GPL@software.virtualmin.com/gpl/universal/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
And if I did switch to 6 would that be risky to all of a sudden update from there?
Thanks
Yep. You have the old repos.
To update to the /vm/6 repos, download the current version of the install script, and run it with the --setup flag. It must be the current version of the install script (old one didn’t support the --setup flag and would just try to install again, which would be dangerous). The setup flag tells it to just setup the repos, and it will update the repos if old repos are currently enabled.
Thanks for letting me know.
Sorry one last question… will switching to the v6 repos be risky at all? Could there be lots of new updates which somehow break my old server!?
Thanks
No.
The vm6 repos are safe to switch to for anyone on the old repos. The vm7 repos are not perfectly safe, in particular for CentOS 7 users, because we stopped providing Apache rebuilds, so you’d be without updates unless/until you switched to running without suexec (using PHP-FPM instead for PHP apps, and some other option for CGI apps, if any).
Running with the --setup option on your system will switch to the vm6 repos.
Yay! Thanks ever so much that was the easiest thing ever! Its done, so appreciate your fast reply!
You dont suppose I should/could do something similar with Centos 6 do you? 
. I have some even older servers! I dont do any updates on them now, there are none in the old repos. I wondered if there are updates via new repos. But I imagine there is not.
Thanks
CentOS 6 is too old. It’s been EOL for nearly three years. I couldn’t even try to support it.
That’s fine I knew the answer. I wasn’t asking for you to support it, I just wanted to make sure because I had no idea the Centos 7 repos were changed, so just making sure it wasn’t the same for Centos 6!
Thanks a lot for your help it’s been brilliant and all sorted now!
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.