Install error on CentOS 5 / poss firewall probs


I’m trying to install Virtualmin Pro on CentOS 5 (x86_64, installed with “Server and GUI” and GNOME options, and also opted to install emacs and java. After the installation, I also installed apcupsd for UPS monitoring. Otherwise it’s a standard installation).

I should state from the outset that I’m inside a university network behind a firewall – we have a proxy with authentication that I have to go through to get out onto the net for http/https/ftp. Some ports are open – I can ssh out through the firewall, for example, and I can serve http/https/ftp to the outside world. I know this sounds weird, but we’ve got our server sitting in an office; it’s on a regular staff office subnet, not on a server subnet. Anyway, thought I should mention this, because I expect this will give me problems. Not sure if it’s causing the current problem though…

I tried running the install script, and it started spitting out errors right away. I have already searched the forum, and saw someone who reported a similar problem. In that case, as best I could tell, it was a matter of the serial and key not being in the install file correctly. I have checked mine against what’s listed on my account on the serials page, and they’re correct.

Here’s my attempt at running the script:
[root@elephant virtualmin]# /bin/sh

Welcome to the Virtualmin Professional installer, version EA4.2

WARNING: This is an Early Adopter release.

The installation is quite stable and functional when run on a freshly
installed supported Operating System, but upgrades from existing .wbm-
based systems, or systems that already have Apache VirtualHost
directives or mail users, will very likely run into numerous problems.
Please read the Virtualmin and Early Adopter FAQs before proceeding if
your system is not a freshly installed and supported OS.

This script is not intended to update your system. It should only be
used to install Virtualmin Professional, or to upgrade a Virtualmin
GPL system that was installed manually via .wbm packages. If you have
previously installed Virtualmin via this script or the GPL version of
this script, upgrades and updates should be handled within Virtualmin

The systems currently supported by our are:
Fedora Core 3-6 on i386 and x86_64
CentOS and RHEL 3-5 on i386 and x86_64
OpenSUSE 10.0 on i586 and x86_64
Mandriva 2007 on i386
Debian 3.1 and 4.0 on i386 and amd64
Ubuntu 6.06 LTS on i386 and amd64

If your OS is not listed above, this script will fail and attempting
to run it on an unsupported OS is not recommended, or supported. The
recommended operating systems for Virtualmin Professional, and more
details about them, can be found here:

Continue? (y/n) y
Checking for curl or wget…found /usr/bin/curl -s -O
Checking for perl…found /usr/bin/perl
Loading log4sh logging library…
./log4sh: line 1: !DOCTYPE: No such file or directory
./log4sh: line 2: syntax error near unexpected token newline' ./log4sh: line 2:”>’ line 425: logger_setLevel: command not found line 427: logger_addAppender: command not found line 428: appender_setAppenderType: command not found line 429: appender_setAppenderFile: command not found line 430: appender_setLevel: command not found line 431: appender_setLayout: command not found line 432: appender_setPattern: command not found line 434: logger_info: command not found line 437: logger_debug: command not found line 438: logger_debug: command not found line 439: logger_debug: command not found line 442: logger_info: command not found line 214: logger_info: command not found line 448: logger_info: command not found line 455: logger_info: command not found line 223: logger_info: command not found line 457: logger_info: command not found line 223: logger_info: command not found
Unterminated <> operator at /tmp/.virtualmin-3791/files/ line 1.
[root@elephant virtualmin]#

Any ideas? Also, any ideas on how I can avoid major problems regarding the proxy issues? I have http_proxy, https_proxy and ftp_proxy environment variables defined as:

Not sure if that’s the correct format, or if it will even help in any way.


OK, I’ve only now realised that the error message mentions the installation directory under /tmp. It seems that the binaries the installer downloads are actually html files – error messages from our proxy farm that tell me I need to authenticate.

In other words, the mandatory proxy authentication is the entire problem here.

I still have no idea how to get around this. Does anyone out there?


So it turns out I’m an idiot.

I did just have to set the proxy environment variables http_proxy / https_proxy / ftp_proxy (not sure if they’re all used, but it can’t hurt to set them all), which I had already done.

Unforunately, I had a typo in my username.

As I said above, I’m an idiot.

It’s working now.

Hehehe…Awesome. Thanks for the update!