I just bought the Virtualmin and while I am very excited, I can't get it to install.
I didn't even think about his but is 10.1 supported? I saw 10.0 and figured that was close enough.
When running the install script, I get an error about connection to package source. Log posted below....
2006-09-17 00:06:59 INFO - Started installation log in virtualmin-install.log 2006-09-17 00:06:59 DEBUG - Install mode: full 2006-09-17 00:06:59 DEBUG - Virtualmin Meta-Packages list: virtualmin-base 2006-09-17 00:06:59 INFO - Loading OS selection library... 2006-09-17 00:06:59 INFO - Succeeded. 2006-09-17 00:06:59 INFO - *********************************************************************** 2006-09-17 00:07:00 INFO - Operating system name: SuSE Linux 2006-09-17 00:07:00 INFO - Operating system version: 10.0 2006-09-17 00:07:00 INFO - *********************************************************************** 2006-09-17 00:07:00 INFO - Installing virtualmin-release package for SuSE Linux 10.0... 2006-09-17 00:09:47 FATAL - Fatal Error Occurred: Unable to add yast2 installation source. 2006-09-17 00:09:47 FATAL - Cannot continue installation. 2006-09-17 00:09:47 FATAL - Attempting to remove virtualmin-release, so the installation can be 2006-09-17 00:09:47 FATAL - re-attempted after any problems have been resolved. 2006-09-17 00:10:09 FATAL - If you are unsure of what went wrong, you may wish to review the log 2006-09-17 00:10:09 FATAL - in /root/virtualmin-install.log.
Hey Jim,
Heheheh...I'm afraid the old saying, "close only counts in horseshoes and hand grenades" applies here.
The install for Virtualmin Professional doesn't do "close", and probably never will (I can't imagine how it could)...it's not the install.sh that is picky, it's the OS itself. We have to install about a half dozen binary packages, and if we installed 10.0 versions on 10.1, something is bound to go wrong. Professional isn't like Webmin or Virtualmin GPL, which are both pure Perl products and nothing can go wrong except paths and simple configuration problems. With binary packages, there can huge swaths of missing or incorrect dependencies, compatibility issues against existing system libraries and tools, and bad breath. ;-)
The good news is that I'm within a few hours (or a bugfix in rug from the SUSE folks) away from a working installer for 10.1. The software is all built, but the SUSE folks broke package management (and also made it a lot better at the same time, but one thing that we must have working for our install does not work in pug, while it did work in the old yast based package manager).
I'm pretty confident I'll be announcing support by Monday night. Not because I believe pug will be fixed, because so far they've just closed the bug I filed as a duplicate of a completely unrelated issue.* But because I'll write in a workaround that'll do the job until they fix their issues.
*-On a fun "bitch and moan" side note, the up2date package manager on Red Hat Enterprise Linux has an identical bug with yum repository support. I'm not sure who is responding in the least helpful way to the bugs I've filed about the issue. Red Hat has made no comment in over a year, but the bug is still open. SUSE commented and closed the bug within 24 hours, calling it a duplicate of an unrelated bug. Neither seems inclined to fix it. Oh, well.
--
Check out the forum guidelines!
Joe thanks for your very timely response. I'll be on pins and needles Monday night!
I didn't think about this at the time but how do I access the 10.1 version of the install? I have been working on getting a control panel up and running and am anxious to get it up and running for my soon to be customers.
Hey Jim,
Once the new version is available, you can just re-download the install.sh file from your Serial Numbers page (http://www.virtualmin.com/serial). The install.sh automatically detects OS version, and if it supports your OS, it'll try to perform the installation (as you've noted, even if it doesn't support the OS, but it has some knowledge of your OS it'll try, but it'll fail pretty abysmally--that's actually a bit of a bug in the install.sh, as it should just bail politely if the OS isn't actually supported).
The install.sh is OS and version neutral (within the supported systems), and so you can at any time move to a different supported OS without having to ask our permission or buy a "cross-grade" license, or anything silly like that. The "select your OS" during purchase is merely for information gathering purposes. We like to know what kind of paying demand there is for various supported Operating Systems, so we have some clue about trends in OS usage.
--
Check out the forum guidelines!
I saw the news that new versions of Virtualmin are being released but the install file doesn't appear to have changed.
Also the links on the detailed change log for webmin/usermin are broken.....
http://www.virtualmin.com/news/changes-1.300.html
shows file not found.
Hey Jim,
Sorry, this is merely Webmin, Usermin and the Virtualmin module updates. All of the components are released on an as-finished-and-tested-basis. A new install.sh release is the update you're looking for and that didn't quite get finished yesterday (my girlfriend is having some car troubles occupying my time a bit), but I'm expecting to wrap it up soon.
--
Check out the forum guidelines!