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.
Hmm, it definitely looks like something went awry there.
You could always rename the .log file to be .log.txt if you want to attach the entire thing.
What Linux distribution / version are you using?
-Eric
I attached a log, but I cannot see an obvious link to in the post (https://www.virtualmin.com/system/files/virtualmin-install_9.txt).
uname -r returns 2.6.32-71.el6.x86_64 cat /etc/issue returns CentOS release 6.2 (Final) Kernel \r on an \m
Okay, thanks for the log information.
What do these commands output:
mount
free -m
And what kind of VPS software is on your server there... are you by chance using OpenVZ?
-Eric
mount returns
/dev/vda3 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/vda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
free -m returns
Mem: 997 482 515 0 104 162
-/+ buffers/cache: 215 782
Swap: 1023 0 1023
These values are from a fresh rebuild of the VPS with the preinstalled packages (Virtualmin not installed).
The hosting is KVM on RHEL.
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.
-Eric
I can log into Virtualmin. The Re-Check Config reports everything is OK.
One of the errors in the log is:
Enabling SMTP authentication sh: /usr/lib/sasl2/smtpd.conf: No such file or directory sh: /usr/lib/sasl2/smtpd.conf: No such file or directory
find / -name 'smtpd.conf' gives
/etc/sasl2/smtpd.conf
/usr/lib64/sasl2/smtpd.conf
Looking at virtualmin-base-standalone.pl it may be misinterpreting $libdir.
Line 359: if ( -e "/usr/lib64" && -e "/usr/lib64/perl" ) { $libdir = "/usr/lib64"; }
I don not have a /usr/lib64/perl, but there is a /usr/lib64/perl5
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:
uname -a
uname -a returns
Linux 000000.vps-10.com 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 03:51:51 BST 2011 x86_64 x86_64 x86_64 GNU/Linux
Okay, Jamie looked at your logs, and was wondering what the output of this command is:
df -hHe's quite surprised by those errors, and is wondering maybe if you're running into a disk space sort of issue.
-Eric
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda3 50068712 1392420 46132932 3% /
tmpfs 510764 0 510764 0% /dev/shm
/dev/vda1 495844 51906 418338 12% /boot
I change the VPS to CentOS 5. Running the Virtualmin script was not error free, but there where a lot less errors in the log (http://www.virtualmin.com/system/files/virtualmin-install_10.txt).
Howdy,
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?
-Eric
Was the resolution to this that the Virtualmin script must run on x86 instead of x64?
This script has so far not worked like six times on x64. Sometimes there are pid locks, sometimes not, I've tried fqdn & just hostname
Install is CentOS 6.5 x64.
Installing Virtualmin from:
http://www.virtualmin.com/download.html
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.