Installation Checklist
You must install the RPM spamassassin-3 or later on the server before you install Ensim Pro Control Panel.
Verify that you have set up the yum repository containing the operating system RPMs, RPM updates, and RPM extras (required only if using yum to obtain and update RPMs).
Set up a yum repository on your local FTP server or on the server on which you are installing Parallels Pro Control Panel. The installer obtains the operating system RPMs, required RPM updates, and RPM extras from the repository.
Ensim Pro Control Panel and Yum version
Ensim Pro is compatible with yum version 2.4 or later. If an earlier version is installed, the installer tries to install/update the installed version; however, to avoid installation failures, it is recommended that you verify the version of yum installed on the server. To verify the yum version, run the following command at the prompt:
List of packages that should not be upgraded on an Ensim Pro for Linux server.
Ensim RPMs you should leave alone: Some of these application RPMs have an tag in the build number (”ensimized RPMs”). This denotes that Parallels Pro Control Panel for Linux has made modifications to the RPM for various reasons such as fixing bugs, adding additional security, or improving performance for hosting domains. The detailed list of these RPMs is shown below.
Package Name
apache-mod_fastcgi
ensim-perl
frontpage
tomcat-connectors
analog
chartdirector-python
imap
majordomo
Miva-empresa
Mivamerchant
Mivamerchant-5.00
miva-empresa-5.02
phpMyAdmin
poprelay
squirrelmail
vacation
webdav
tomcat4
Zope
Reference :http://www.parallels.com/products/pro/
Scheduled backup fails on Ensim Pro X for Linux
Once you edit the scheduled backup on Ensim Pro X for Linux v10.0.0, scheduled backup fails to function. Primary reason logged is ftp login failure. To fix this problem download the script and execute on the server.
Download :
http://download.swsoft.com/ensim/download/pro/linux/kb/2332/fix_schback_KB2332.pl
wget http://download.swsoft.com/ensim/download/pro/linux/kb/2332/fix_schback_KB2332.pl
# perl fix_schback_KB2332.pl
Reference : http://parallels.com
When the cron file /etc/cron.daily/1hup_apache_logs is executed the httpd service is not able to reload properly and it get stuck. The service is dead and it needs to be restarted manually. Even the server load goes high. And in some cases the server even crashes.
To Resolve this issue.
Change “reload” to “restart” in /etc/cron.daily/1hup_apache_logs
Content of /etc/cron.daily/1hup_apache_logs are as follows:
#!/bin/bash
#/etc/rc.d/init.d/httpd_app_init reload-grc
# XXX Fix of the “lost child came home” issue
! /sbin/chkconfig httpd || /etc/rc.d/init.d/httpd_app_init reload
And then change to
#!/bin/bash
#/etc/rc.d/init.d/httpd_app_init reload-grc
# XXX Fix of the “lost child came home” issue
! /sbin/chkconfig httpd || /etc/rc.d/init.d/httpd_app_init restart
Reference: http://parallels.com
