Yes. The upgrade will, I believe, setup the apt-get repository for you, and shouldn’t have any impact on which services you use (though you might need to turn some of the new stuff off after upgrading, since Pro has a few additional features and services that are enabled by default).
Nope. Is bug. Though I’m not sure how it would have happened. I’m not seeing that behavior on my test systems.
You need only one of those virtualmin repo definitions.
Are you saying you have no repo entry at all for Virtualmin on the upgraded box? That should only happenif Virtualmin wasn’t installed via packages (and probably not even then).
on server when i upgrade to PRO the first installation was made by wmb.gz package and not with .deb archive.
But now when i try to upgrade because System Information said: "Package updates All Virtualmin packages are up to date.
There are 1 optional Virtualmin packages that you can install."
I see this upgradable package
Package Description Status
webmin-virtual-server Webmin module Available for installation
But during the installation process i see that Webmin try to upgrade from .deb archive:
Now updating webmin-virtual-server …
Installing package(s) with command apt-get -y --force-yes -f install webmin-virtual-server ..
Reading package lists...
Building dependency tree...
Package webmin-virtual-server is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
.. install failed!
No packages were installed. Check the messages above for the cause of the error.
I’d probably suggest making sure your backups are complete and up to date, and then manually switch over to deb packaged modules. You should be able to download the packages and install with:
dpkg -i webmin-virtual-server_3.54-3_all.deb
(You can access the Pro package repository using your serial number and license key as the username and password.)
If problems persist, let me know and I’ll be happy to drop in on your box and straighten it out.
I have a backup of /etc and /home. I have first set-up new repository in sources.list then upgrade some packages (apache and webmin) from virtualmin rep.
(Reading database … 47066 files and directories currently installed.)
Unpacking webmin-virtual-server (from webmin-virtual-server_3.54-3_all.deb) …
This Webmin module is already installed on your system.
dpkg: error processing webmin-virtual-server_3.54-3_all.deb (–install):
subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
webmin-virtual-server_3.54-3_all.deb
This is a bug in our package builder for Debian. It’s not supposed to do this.
I’m looking into it. In the meantime, move /usr/share/webmin/virtual-server out of the way, and try it again. I think that’ll let you install without this error. (But you might even have to move /etc/webmin/virtual-server out of the way, as well…but be sure to copy /etc/webmin/virtual-server back into place after install, if it it necessary, as that’s where all of your virtual servers configuration is stored, and losing it would make all of your Virtualmin accounts to “disappear”.)
I am about to install VM Pro for a client. For grins, I wanted to make a dry run upgrading VM GPL version 3.47 to current GPL, 3.54 I believe.
I retained old virtual-server directory, so just moved it off to the side, ran dpkg -i and installed curretn version of VM GPL. All references to prior VM installs disappeared, and was asked to go through a recheck and reconfig of VM. Not so scary, but, will the prior accounts and info installed in the older version re-appear? Or, are they toast? I stopped the practice upgrade because I didn’t want to blow away the prior accounts. All this was in prep for the Pro version for this client which he either did purchase, or will purchase by EOB Monday.
Will these already installed accounts reappear even tho I have to do through a recheck and reconfig?
Actually, we recommend the Upgrade to Professional option found within Virtualmin GPL, rather than the install script. The install script is somewhat more likely to break things (because it knows a lot less about your existing installation than a full Webmin/Virtualmin stack knows).