Some Software not installed.

Hey Faisal,

Whoah! Something went horribly wrong. It appears I've utterly broken the installer sometime during the updates. All of that stuff should have been setup. You shouldn't have to touch anything beyond customizations that you want to do when it is finished. I'm looking into it right now. A new version of the virtualmin-base package will be released in an hour or two that corrects this problem. I will also send you a virtualmin-uninstall script that will allow you to start over close enough to "from scratch" to where the "already installed" checks won't come back positive and you'll have the post-installation script in virtualmin-base run again (which is where all of the configuration and stuff happens).

There is a Dovecot module in the next release of Webmin (and in the current devel package here: http://www.webmin.com/devel/rpm ). You shouldn't need it, though--the installer was supposed to set it up for you.

The installer (actually me) doesn't quite know what to do with scponly yet--it will be in EA2 in a day or two. There is nothing easy about it, unfortunately, and it is not at all a normal/simple package. It's a bear do deal with, but folks wanted a restricted shell, and it seems to be the best choice.

Procmail should already be configured. But it sounds like the post-install script didn't get run at all (one of the additions in this release was a test to be sure the virtualmin-base package isn't already installed), in which case procmail won't be configured either.

Anyway, I'll post in an hour or two after I've resolved these issues.

Hey Faisal,

Ok, I've been able to reproduce this--my earlier tests weren't catching the problem as I was only uninstalling the Virtualmin packages (and not all of the other stuff). A fresh install revealed that in the new virtualmin-base package I had removed several deps without adding them to the install script, so they never got installed, and then the postinstall script in virtualmin-base crapped out before finishing in addition to some stuff not getting installed. So, in short, everything went pear-shaped due to a few missing dependencies.

The following instructions also apply to anyone else who has run into this issue--the offending virtualmin-base package went up about 36 hours ago, so any installs during that time are probably broken in many ways, so reinstalling is a great idea if you haven't begun adding domains yet--if you have, let me know and I'll assist you with resolving all of the issues...I have a standalone script that can fix most problems without a lot of hassle.

The old installation script (install.sh) is also broken, and you'll need to download the newest one from http://www.virtualmin.com/serial . This makes me realize I need to figure out a way to automatically update to the latest version of the install script...

First, run the uninstallation script so we're starting fresh. You can get it here:

http://software.virtualmin.com/lib/virtualmin-uninstall.sh

This will remove all of our packages and flush the yum header and package caches.

Next up, just run the new install:

./install.sh

This time it should all Just Work, and if it doesn't I, of course, want to know about it.

Oh, yeah, I've also uploaded an scponly package into the repository and added it to the deps list so it gets installed during the installation process. It also gets added to the /etc/shells file, so you can access it from the dropdowns. It's not chroot-enabled yet, but it is still a very nice restricted shell. chrooted scponly will come in EA2 or EA3, or as soon as I figure out how to package it and make it work seamlessly, just like any other shell.

I have tested this pretty thoroughly on Fedora Core 4. I am now booting up my Xen kernel so I can test it on CentOS3/4 and FC3. RHEL3/4 will have to wait until I'm back in the office, as I have to set the BIOS in one of my servers to re-install (it's got SUSE on it now). If you've been burned often enough by my shoddily tested installer, you can wait an hour or two and it will be extremely well-tested and ready for mainstream consumption.

Apologies for the rough early experience with the installer...I've been so focused on issues with SUSE that I didn't even notice that the changes I was making might break installation on the already supported systems. Gotta get a better test procedure in place for the installer script and file...