Install virtualmin pro fails

Hello,

I Tried to install Virtualmin Pro on a freshly centos 6.4 64bity server. The server is a vps and I installed the gpl version serveral times on a server like this without problems.

This is the response:

[root@DA-EXT005 ~]# sh install.sh

Welcome to the Virtualmin Professional installer, version 1.1.0

WARNING:

The installation is quite stable and functional when run on a freshly installed supported Operating System.

If you have existing websites, email users, or if you manually installed Virtualmin via a Webmin 'wbm' module, you are likely to run into problems. Please read the Virtualmin Administrators Guide 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 perform your initial Virtualmin installation. If you have previously run the Virtualmin installer, you can perform upgrades and updates from within Virtualmin itself, or using your system's package manager. Once Virtualmin is installed, you never need to run this script again.

The systems currently supported by install.sh are: CentOS and RHEL 5-6 on i386 and x86_64 Scientific Linux 6 on i386 and x86_64 Debian 6.0 and 7.0 on i386 and amd64 Ubuntu 8.04 LTS, 10.04 LTS, and 12.04 LTS on i386 and amd64 Amazon Linux 2012.03 on i386 and x86_64 FreeBSD 7 and 8 on i386 and amd64

If your OS is not listed above, this script will fail. More details about the systems supported by the script can be found here:

http://www.virtualmin.com/os-support.html

Continue? (y/n) y Checking for HTTP client...found /usr/bin/curl -s -O Checking for perl...found /usr/bin/perl chmod: cannot access `spinner': No such file or directory Loading log4sh logging library... Could not load logging library from software.virtualmin.com. Cannot continue. We're not just stopping because we don't have a logging library--this probably indicates a serious problem that will prevent successful installation anyway. Check network connectivity, name resolution and disk space and try again. [root@DA-EXT005 ~]#