Archive for the tag 'Parallels'

SBDavid
Nov 25th, 2009

Using CLI to Restart Parallels Plesk Panel

Using CLI to Restart Parallels Plesk Panel

Login to the server as user root.

Parallels Plesk Panel for Linux:

# /etc/init.d/psa stop
# /etc/init.d/psa start

Parallels Plesk Panel on FreeBSD since.

# /usr/local/etc/rc.d/psa.sh stop
# /usr/local/etc/rc.d/psa.sh start
SBDavid
Nov 24th, 2009

Stopped Parallels Plesk Panel service starts automatically

Stopped Parallels Plesk Panel service starts automatically

Resolution: Make sure you did not remove the Parallels Plesk Panel event handlers that are required for the proper work of the module:

Service started lowest (0) psaadm /usr/local/psa/admin/bin/php /usr/local/psa/admin/bin/modules/watchdog/wd –monit-service= –plesk-name

Service stopped lowest (0) psaadm /usr/local/psa/admin/bin/php /usr/local/psa/admin/bin/modules/watchdog/wd –unmonit-service=

Note: If you use Debian Linux or Ubuntu Linux, the path to Watchdog’s system files is /opt/psa/admin/modules/watchdog/

Source : http://parallels.com/Plesk/

SBDavid
Nov 20th, 2009

Installing Parallels Plesk Panel on Numerous Servers

Download a distribution that suits your operating system from the URL http://www.parallels.com/en/download/plesk9/ and save it on your server’s hard drive.

To install Parallels Plesk Panel on a number of servers, you may want to set up a mirror of the official Parallels Plesk Panel update server (http://autoinstall.plesk.com) inside your network so as not to download the distribution files through the Internet each time, and then install Parallels Plesk Panel.

If you have Parallels Plesk Panel installed on the server, you can use the parallels_installer binary file, which is stored in the directory /usr/local/psa/admin/bin/ on RPM-based Linux, FreeBSD and Mac OS systems, and /opt/psa/admin/bin/ on deb-based Linux systems.

Prepare the installation script based on the example below. Replace the options in the example script with the ones you prepared, and specify server names in the ‘SERVERS_LIST=’ string separated by white spaces:

#!/bin/sh
SERVERS_LIST=”node1.example.com node2.example.com”
for current_server in $SERVERS_LIST; do
scp parallels_installer root@current_server:
ssh -f root@current_server “parallels_installer –source-type network –source http://updates.example.com/ –target /tmp/plesk –select-release-id PLESK_9_0_0 –install-component base –install-component postgresql –install-component asp –notify-email admin@example.com”
done

Run the script. It will copy the Parallels Products Installer to the specified servers and install Parallels Plesk Panel. Keep the passwords for access to the servers at hand, as you may be required to specify them.

Document Source : http://parallels.com/Plesk/

SBDavid
Nov 5th, 2009

SELinux Policy for Your Parallels Plesk Panel Server

SELinux Policy for Your Parallels Plesk Panel Server

To configure SELinux you need to know the rules that should be added into the system policy.

SELinux reports all denied messages into the /var/log/audit/audit.log file and these messages can be easily converted into the rules using the /usr/bin/audit2allow utility.

cat /var/log/messages | /usr/bin/audit2allow

Also, /var/log/messages.* files can be examined for the SELinux deny messages.

SBDavid
Oct 4th, 2009

How to Install Parallels Pro Control Panel into Virtuozzo Containers

Install Parallels Pro Control Panel into Virtuozzo Containers.

Steps:

Install the Containers and then install Parallels Pro CP.

Download the respective Parallels Pro Virtuozzo Container Template.

For CentOS 5 i386:

http://download.pro.parallels.com/ensim/apt/ensim/EPL/10.3.4/ez/ppcpl10-centos-5-x86-ez-4.0.0-3.parallels.noarch.rpm

Before installing Parallels Pro CP from Parallels Virtuozzo Containers Templates, prepare your Virtuozzo Containers according to the requirements below.

Important: before proceeding with the Containers installation, make sure that the hostname –i command doesn’t return 127.0.0.1 IP.

Before creating the Containers and installing Parallels Pro CP, log in as root to your Hardware Node. Open the /etc/sysconfig/vz file and change the value of the VZPRIVRANGE to “1 N” where N is max ID of Container you will be using, for example:

VZPRIVRANGE=”1 10000”

Refer to the log file /var/log/ensim/installer..-.log for errors during the installation.

« Prev - Next »