Okay, doing a little digging, I think I found an example of the file that’s missing, and we may just be able to manually replace it… however, that’s a symptom that something may be awry on your server. It doesn’t appear as if the install.sh script was used to perform the installation… or if it was, something fairly drastic occurred afterwards.
However, what you’d want to do is download these two files, and place them into the directory /etc/pki/rpm-gpg/:
ls /etc/pki/rpm-gpg
RPM-GPG-KEY-CentOS-6
RPM-GPG-KEY-CentOS-Debug-6
RPM-GPG-KEY-CentOS-Security-6
RPM-GPG-KEY-CentOS-Testing-6
RPM-GPG-KEY-virtualmin
RPM-GPG-KEY-webmin
But get the following error now:
Failed to upgrade to Virtualmin Pro : No Virtualmin GPL repository was found in /etc/yum.repos.d/virtualmin.repo
*We didn’t use install.sh for the installation. There was another engineer whom installed webmin for the server, but I wanted the convenience of virtualmin pro and have been trying to install this.
I suspect it’s possible to get things to work having not used the install.sh script… but you’ll likely run into some hurdles along the way, both now and later.
What you may need to do is convert your virtualmin.repo file to point to the GPL repos, rather than the Pro repos it’s currently pointing to.
[virtualmin-universal]
name=Virtualmin Distribution Neutral Packages
baseurl=http://software.virtualmin.com/gpl/universal/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
After that, are you then able to perform the upgrade?
Note though that what you’re attempting isn’t technically supported or recommended – so I’d suggest making sure that you have a good backup of your system, just in case! I suspect it can work, but there is the possibility that things may not go expected, due to the unusual environment.
Well, I’ve tried your suggestion and yet another error.
Taking your advice that there maybe more hurdles in the future, I will re-install using install.sh
That process of running the install.sh really does configure a lot of stuff, and greatly simplifies the installation process. Without that, a lot of things are unlikely to work properly.
For example, many of the Install Scripts you get with Virtualmin Pro require a working Virtualmin repository configuration, in order to pull in various dependencies.
However, I’m not trying to be dismissive, we really can keep tackling the errors that pop up until the upgrade process completes.
Another option did strike me, that may end up being simpler, if you want a short term solution.
If the Virtualmin version that’s installed now was installed via an RPM, you can always grab the Virtualmin Pro RPM from the software repository, and use that to upgrade the current package you have installed.
That won’t solve all the issues you’re having, and some of the Pro features won’t work properly – but others will. It just depends on what you’re hoping to use
While the upgrade to Virtualmin Pro should certainly work, since you’re starting over anyhow, could I suggest starting with Virtualmin Pro, rather than doing an upgrade?
To do that, start with a fresh CentOS install (though, you might be able to get away with just uninstalling Virtualmin), browse to this URL, and download the Virtualmin Pro installer:
Tried uninstalling virtualmin with uninstall.sh and re-install using the install.sh from the license.
But after the installation, the previous configuration is still there and only shows virtualmin gpl.
So I’ll be installing a fresh copy of the os and will give it a try again.
It sounds like you’re having a real tough time getting that to work!
If you haven’t yet reinstalled your OS, if you give me your server’s login details, I can login to your system and perform the Virtualmin Pro installation, if you like.
Hopefully you saw my email regarding this as well – but your system should be correctly setup now. Whenever you log in, you should see Virtualmin Pro, and any further updates will come from the Virtualmin Pro repository.
Also Centos 6.4 - During the install of virtualmin from the CLI, I experienced contention with yum, who had left a lock file open somewhere. The problem happened twice, and I never got a fully “finished” install.
Then again, vm seemed to be working, so I went ahead with it… until I tried to upgrade
This is a brand new virtual machine, so no big deal with starting from scrap again. Just wanted you to have the data.