I have install Virutalmin GPL on a Heart Internet (www.heartinternet.co.uk) VPS using the automated script.
There are errors in the virtualmin-install.log during the configuring stage.
When the VPS is provisioned packages such as Webmin, Apache, Postfix and Dovecot are already installed. The attached log - interesting that you cannot attach .log files in this foruam - is from an install where I first removed these packages using yum. Errors are:
Error occurred while setting Usermin theme: Failed to open PID file at …/web-lib-funcs.pl line 1360.
Missing file to read at dovecot::/usr/libexec/webmin/dovecot/dovecot-lib.pl line 213
Missing file to read at dovecot::/usr/libexec/webmin/dovecot/dovecot-lib.pl line 213
Missing file to read at dovecot::/usr/libexec/webmin/dovecot/dovecot-lib.pl line 213
Error occurred while configuring or enabling Dovecot: Missing file to open at main::web-lib-funcs.pl line 3017 at web-lib-funcs.pl line 1360.
sh: /usr/lib/sasl2/smtpd.conf: No such file or directory
sh: /usr/lib/sasl2/smtpd.conf: No such file or directory
Error occurred while configuring Procmail: Missing file to open at WebminCore::…/web-lib-funcs.pl line 3017 at …/web-lib-funcs.pl line 1360.
Error occurred while configuring and enabling BIND: Missing file to open at WebminCore::…/web-lib-funcs.pl line 3017 at …/web-lib-funcs.pl line 1360.
Error occurred while enabling status monitoring: Missing file to open at WebminCore::…/web-lib-funcs.pl line 3017 at …/web-lib-funcs.pl line 1360.
Error occurred hiding Webmin upgrade page:
Error occurred while configuring firewall rules: Missing file to open at WebminCore::…/web-lib-funcs.pl line 3017 at …/web-lib-funcs.pl line 1360.
I don’t see any obvious issues that would cause the errors/warnings you saw.
I do notice though that it was able to complete successfully.
Do things work for you?
If you log into Virtualmin on port 10000 on your server, and go into Server Configuration -> Re-Check Config, does it detect any problems?
Sometimes, VPS providers may do something non-standard when creating their OS images, and it’s possible there’s something just a little different than Virtualmin was expecting.
You may want to try it out and see if things are actually working correctly for you, in spite of the notices you saw.
Hmm, it should be able to distinguish between a 32 and 64 bit system. I may ask Jamie for a hand in figuring out what the issue you’re seeing there is, but I’m curious – what does this command output:
Sorry for the delay… Jamie and I have been going back and forth on all this, trying to figure out what might be awry… we’re never seen that happen before
I suspect there’s something atypical about the CentOS 6 VPS image that’s confusing the Virtualmin installer, but we’re not sure what yet.
However, your CentOS 5 install does look a lot better.
I suppose the big question though is – do things work for you? I know you said you saw some errors in the logs previously, are those all gone now?
On CentOS 6.5 x64, the script works – no errors. But logging in via :10000 is not possible. It is possible that there is something built into the VPS that is blocking me for the x64 install. I spent a few days on it, and finally gave up.
Since I"m running a VPS with only 512MB, I’m able to try the x32 install. It works fine., and :10000 is immediately available. A few days of work – and I didn’t feel any closer to resolution – so x32 it shall be.
Anyway, if you are hitting this problem with x64 install, you might consider x32 if your environment will work in it.