Tag Archives: upgrade

Downgrade Virtualmin pt3

Okay its seems that the virtualmin downgrade has settled down now.
I’m still working out exactly how much functionality I have lost by going to the free GPL version but this is what I did:
After installing the RPM I downloaded the repo and installed it with:
rpm -Uvh –oldpackage virtualmin-release-latest.rpm
I then ran a
yum clean all
This will clean up the repo settings left over from the downgrade and reset to the gpl version.
You then need to go into the webmin control panel
WEBMIN>SYSTEM>Scheduled Cron Jobs
and disable the following cron jobs that are not offered in the gpl version:
sendratings.pl
maillog.pl
fcgiclear.pl
The last one is a clean up program for fastcgi but , I haven’t found out what the other 2 jobs do.
I just know that they give me errors in my logs if left enabled.
Ted

Okay its seems that the Virtualmin downgrade has settled down now.

I’m still working out exactly how much functionality I have lost by going to the free GPL version but this is what I did:

  • I downloaded the repo rpm and installed it with:

rpm -Uvh –oldpackage virtualmin-release-latest.rpm

  • I then ran a

yum clean all

This will clean up the repo settings left over from the downgrade and reset to the gpl version.

I then went into the webmin control panel:

WEBMIN>SYSTEM>Scheduled Cron Jobs

and disabled the following cron jobs (these are apparently not valid in the gpl version of Virtualmin):

  1. sendratings.pl
  2. maillog.pl
  3. fcgiclear.pl

That last one is a clean up program for fastcgi but , I haven’t found out what the other 2 jobs do.

I just know that they give me errors in my logs if left enabled.

I have since discovered that it might be possible to change the username and password to “GPL” and the re-run the install script. I have not tested this and don’t know what that would do to the existing servers, mailpacks , etc.

Downgrade Virtualmin

I recently had to downgrade our Virtualmin package from PRO to GPL because our license expired and we didn’t seem to need the features of the PRO version any more.

Time will tell if this turns out to be a foolish move but this is what I did.
Basically you just install the GPL version over top of the PRO version.
Exactly how you downgrade depends on your OS, and how you installed.
For an RPM-based Distro like Centos 5, you’ll have to use the “–old-package”
option to RPM to install the GPL version. Because upgrading is the far more
common path, Professional has a higher Epoch than GPL, which means it always
looks like a newer version to rpm/yum, even if it isn’t.
The GPL repository has the exact same URL as the Professional one, except it
has “/gpl/” at the beginning of the path.
Steps I took:
ONE
First install the GPL version over the PRO version;
Download from
http://software.virtualmin.com/gpl/centos/5/i386/
e.g. wbm-virtual-server-3.73.gpl-1.noarch.rpm
rpm -Uvh –oldpackage wbm-virtual-server-“VERS#”.noarch.rpm
Obviously, with GPL, you don’t need a serial number or license key in the URL
TWO
Then upgrade the repo with:
rpm -Uvh –oldpackage http://software.virtualmin.com/gpl/
centos/5/i386/virtualmin-release-latest.noarch.rpm
THREE
Then do a
yum update
…and finally REBOOT if a new kernel was installed.
I recently had to downgrade our Virtualmin package from PRO to GPL because our license expired and we didn’t seem to need the features of the PRO version any more.
Time will tell if this turns out to be a foolish move but this is what I did.
Basically you just install the GPL version over top of the PRO version.
Exactly how you downgrade depends on your OS, and how you installed.
For an RPM-based Distro like Centos 5, you’ll have to use the “–old-package”
option to RPM to install the GPL version. Because upgrading is the far more
common path, Professional has a higher Epoch than GPL, which means it always
looks like a newer version to rpm/yum, even if it isn’t.
The GPL repository has the exact same URL as the Professional one, except it
has “/gpl/” at the beginning of the path.
Steps I took:
ONE
First install the GPL version over the PRO version;
Download from
http://software.virtualmin.com/gpl/centos/5/i386/
e.g. wbm-virtual-server-3.73.gpl-1.noarch.rpm
rpm -Uvh –oldpackage wbm-virtual-server-“VERS#”.noarch.rpm
Obviously, with GPL, you don’t need a serial number or license key in the URL
TWO
Then upgrade the repo with:
rpm -Uvh –oldpackage http://software.virtualmin.com/gpl/
centos/5/i386/virtualmin-release-latest.noarch.rpm
THREE
Then do a
yum update
…and finally REBOOT if a new kernel was installed.

Time will tell if this turns out to be a foolish move but this is what I did.

Basically you just install the GPL version over top of the PRO version, how you downgrade depends on your OS. For an RPM-based Distro like Centos 5, you’ll have to use the “–old-package” option to RPM to install the GPL version. Because upgrading is the far more common scenario, PRO has a higher Epoch than GPL, which means it always looks like a newer version to rpm/yum, even if it actually  isn’t.

The GPL repository will have the same URL as the Professional one, except it

has “/gpl/” in the path.

Steps I took:

ONE

First install the GPL version over the PRO version;

Download from

http://software.virtualmin.com/gpl/centos/5/i386/

e.g. wbm-virtual-server-3.73.gpl-1.noarch.rpm

rpm -Uvh –oldpackage wbm-virtual-server-“VERS#”.noarch.rpm

Obviously, with GPL, you won’t need a serial number to download it.

TWO

Then upgrade the repo with:

rpm -Uvh –oldpackage http://software.virtualmin.com/gpl/

centos/5/i386/virtualmin-release-latest.noarch.rpm

THREE

Then do a

yum update

…and finally REBOOT if a new kernel was installed.