Dear Support,
I am having the following problem stating that the GPG key retrieval failed upon upgrading to Pro license. Could you advise a solution?
Running Cent OS 6.4
Thank you and regards. Eric
Transaction SummaryInstall 30 Package(s) Upgrade 1 Package(s)
Total download size: 20 M
Total 158 kB/s | 20 MB 02:09
warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID a0bdbcf9: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin .. done
Some errors occurred while upgrading your system to Virtualmin Pro. Please check the messages above for possible causes.
Howdy,
Hmm, what is the output of this command:
ls /etc/yum.repos.d/I'm curious if there are any repositories setup that might be causing a problem of some sort.
-Eric
Hi Eric,
The output is as follows:
> ls /etc/yum.repos.d/CentOS-Base.repo
CentOS-Debuginfo.repo
CentOS-Media.repo
CentOS-Vault.repo
virtualmin.repo
I had created the virtualmin.repo following a solution on the forum for the following error:
Virtualmin has been installed from an RPM, but not using the Virtualmin GPL repository. Upgrading is not possible at this time.content of the virtualmin.repo:
[virtualmin]
name=Red Hat Enterprise $releasever - $basearch - Virtualmin
baseurl=http://SERIAL:KEY@software.virtualmin.com/rhel/$releasever/$basearch/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
[virtualmin-universal]
name=Virtualmin Distribution Neutral
baseurl=http://SERIAL:KEY@software.virtualmin.com/universal/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
Thank you and regards, Eric
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/:http://software.virtualmin.com/lib/RPM-GPG-KEY-virtualmin
http://software.virtualmin.com/lib/RPM-GPG-KEY-webmin
I've added the suggested files as seen below:
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.
Your support is appreciated.
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.
Try changing it to look like the following:
[virtualmin]
name=RHEL/CentOS/Scientific $releasever - $basearch - Virtualmin
baseurl=http://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://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.
-Eric
Hi Eric,
Thanks for the support.
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
Best regards, Eric
Howdy,
Sure, we're happy to help!
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 :-)
You can grab that from here:
http://software.virtualmin.com/universal/wbm-virtual-server-4.02-1.noarc...
You can enter your Virtualmin serial number as the username, and the license key as the password, when prompted.
-Eric
Hi Eric,
Well, I attempted to uninstall and reinstall virtualmin pro with install.sh
On the surface it looked liked it installed fine, but when I upgraded to virtualmin pro I am stuck at the same place again.
It's giving me the same error: Failed to upgrade to Virtualmin Pro : No Virtualmin GPL repository was found in /etc/yum.repos.d/virtualmin.repo
I tried with the file you have suggested above and the following that was there;
[virtualmin] name=RHEL/CentOS/Scientific $releasever - $basearch - Virtualmin baseurl=http://SERIAL:KEY@software.virtualmin.com/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://SERIAL:KEY@software.virtualmin.com/universal/ enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin gpgcheck=1
I'm still a newbie with all this and I'm hoping to use virtualmin pro to help manage a few domains that I own and run some installation scripts.
Not sure if any old files created this conflict.
Could you advise how to resolve? Your help is appreciated.
BR's Eric
Howdy,
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:
http://virtualmin.com/serial/
Then, run that installer, which will give you a working version of Virtualmin Pro.
-Eric
Hi Eric,
Just an update.
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.
Thanks for the advice's! Eric
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.
You can send your login details to eric@virtualmin.com.
-Eric
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.
Let us know if you have any other questions!
-Eric
Dear Eric,
Thank you very much for your support!
BR's Eric
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.
Cheers!