Failed upgrade to Virtualmin Pro

After purchasing a virtualmin pro licence for 100 domains I ran as root the command displayed:

wget -O install.sh http://software.virtualmin.com/cgi-bin/install.cgi?serial=99999999\&key=XXXXXXXXXX; /bin/sh install.sh

The upgrade appears to be successful apart from some errors in updating spamassassin rules

INFO - Updating SpamAssassin rules...
...in progress, please wait...
....
sa-update failed.  Error (if any): 0

Displaying the last 15 lines of /root/virtualmin-install.log to help troubleshoot this problem:
Reading state information...
postfix is already the newest version.
postfix-pcre is already the newest version.
webmin is already the newest version.
usermin is already the newest version.
ruby is already the newest version.
libapache2-mod-ruby is already the newest version.
libxml-simple-perl is already the newest version.
libcrypt-ssleay-perl is already the newest version.
unzip is already the newest version.
zip is already the newest version.
quota is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
INFO - 2010-10-28 11:54:02 - /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install postfix postfix-pcre webmin usermin ruby libapache2-mod-ruby libxml-simple-perl libcrypt-ssleay-perl unzip zip quota: Succeeded.
INFO - 2010-10-28 11:54:02 - Updating SpamAssassin rules...
INFO - Rule updates failed

After the above, virtualmin still shows its version as the GPL version although the correct serial number and licence key are displayed in the Virtualmin licence section. When I click on Re-check Virtualmin licence I get Error - file not found.

Cheers,

David.

Status: 
Closed (fixed)

Comments

So did you already have the GPL version installed, using our install script?

If so, the better way to upgrade is at System Settings -> Upgrade Virtualmin. You can just enter your new serial and key, and it will download all the needed packages for the upgrade.

Let us know how that goes..

Thanks for your reply. Prior to seeing it, I did the below to resolve the matter.

As this was a testing server, we did not have many vdomains setup, I did a fresh install of ubuntu 10.04 server, than ran the pro install script and all appears to be as it should.

Cheers David

That would also work just fine ..

Automatically closed -- issue fixed for 2 weeks with no activity.