PLESK SERVER ADMINISTRATOR 5.0

Chapter 5. Installing Plesk Server Administrator on Your System

Before You Install Plesk Server Administrator

Only install Plesk Server Administrator (PSA) on a clean server that serves as one dedicated server. Plesk Inc. will not be held liable for any damages occurring as a result of installing PSA on a server that has been installed with anything other than a fresh installation of the operating system for which the PSA installation was intended. You must have root privileges to install PSA on your server.

The PSA Self-Extracting install includes the following components:

  • Admin server

  • Web server

  • MySQL database

  • Mail server

  • DNS server

  • FTP server

The PSA RPM install is designed in general to treat all packages separately. For detailed information on all the packages included in the distribution and what packages PSA can work with see Installing the Plesk Server Administrator later in this section.

NOTE

PSA requires that the network components including inetd/xinetd be properly installed in the system before installation of the PSA software.

What Happens During Install?

This section reviews the functions performed as well as the structure created on the server as it is configured during PSA installation.

PSA Self-Extracting Install

The following services run under PSA:

  • named - BIND 9.2.1

  • MySQL - 3.23.51

  • Qmail - 1.03

  • courier-imap - 1.4.6

  • Apache - 1.3.26

  • ProFTPD - 1.2.5

  • stunnel - 3.22

NOTE

Additional services controllable under Apache are mod_throttle 3.12, mod_perl 1.26, PHP 4.2.2, apache::asp 2.33, Front Page 2000 and Front Page 2002.

Directory Structure

PSA creates the directory /usr/local/psa/ as its root software directory. The location of this directory is defined and changeable within the /etc/psa/psa.conf file. Several subdirectories are also created, including:

  • /usr/local/psa/admin/...

  • /usr/local/psa/apache/...

  • /usr/local/psa/bin/...

  • /usr/local/psa/courier-imap/...

  • /usr/local/psa/etc/...

  • /usr/local/psa/frontpage/...

  • /usr/local/psa/ftpd/...

  • /usr/local/psa/home/...

  • /usr/local/psa/lib/...

  • /usr/local/psa/logrotate/...

  • /usr/local/psa/mysql/...

  • /usr/local/psa/named/...

  • /usr/local/psa/qmail/...

  • /usr/local/psa/rc.d/...

  • /usr/local/psa/share/...

  • /usr/local/psa/stunnel/...

  • /usr/local/psa/tmp/...

  • /usr/local/psa/webalizer/...

Also, during PSA functioning a directory is created: /usr/local/psa/var/...

Accounts and Groups

PSA creates accounts for Apache, MySQL and qmail pseudo-users. These pseudo-users do not have shells in which to operate, alleviating security concerns involving the users.

Services

The following changes in services take place:

  • PSA disables the sendmail service and replaces it with qmail.

  • PSA replaces your named database and configuration files. Then PSA restarts the named daemon.

  • PSA also edits the inetd/xinetd configuration file and comments out the comsat service record.

  • PSA adds the FTP service, using ProFTPD to handle it. If you had a previous FTP service on the server, PSA comments out the old version and uses the new FTP version.

  • PSA adds a SMTP service record, handled by the qmail daemon. If you had a previous SMTP service record, PSA comments it out and replaces it with the new version.

  • The inetd/xinetd daemon is restarted to read its new configuration file.

Using an external DNS server

You can use an external DNS service with PSA, but you should follow these manual configuration steps:

  1. During operating system installation, a remote DNS server can be specified. Or after installation, the remote DNS can be specified in the /etc/resolv.conf file.

  2. The line search localdomain must be removed from the /etc/resolv.conf file on the Plesk server.

  3. Any DNS configurations on the local PSA server must be reflected on the external DNS server.

Other Changes

PSA creates some links to the MySQL libraries in the /usr/lib subdirectory and adds the @psacln string to /etc/ftpchroot.

Also, it adds a string to the file /etc/shells:

/bin/false

or

/usr/bin/false

If the POP3 service record is not in /etc/services, PSA adds it. PSA moves the sendmail binary file to sendmail.plesk. The PSA startup script is placed in the appropriate location to start PSA; this script will enable PSA to start each time the server is booted up.

PSA RPM Install

The following services will be controllable under PSA:

For the RedHat® 7.1

  • named - BIND 9.1.0

  • MySQL - 3.23.36

  • Qmail - 1.03

  • Apache - 1.3.26

  • ProFTPD - 1.2.4

  • stunnel - 3.13

For the RedHat® 7.2

  • named - BIND 9.1.3

  • MySQL - 3.23.41

  • Qmail - 1.03

  • Apache - 1.3.26

  • ProFTPD - 1.2.4

  • stunnel - 3.19

NOTE

Additional services controllable under Apache are mod_throttle 2.11, mod_perl 1.26, PHP 4.1.0, apache::asp 2.29, Front Page 2000 and Front Page 2002.

Directory Structure

PSA creates the directory /usr/local/psa/ as its root software directory. The location of this directory is defined and changeable within the /etc/psa/psa.conf file. Several subdirectories are also created, including:

  • /usr/local/psa/admin/...

  • /usr/local/psa/bin/...

  • /usr/local/psa/etc/...

  • /usr/local/psa/var/...

Other directories, such as /usr/local/psa/lib/... can be created when installing various PSA add-ons.

Accounts and Groups

PSA creates accounts for Apache, MySQL and qmail pseudo-users. These pseudo-users do not have shells in which to operate, alleviating security concerns involving the users.

Using an External DNS Server

You can use an external DNS service with PSA, but you should follow these manual configuration steps:

  1. During operating system installation, a remote DNS server can be specified. Or after installation, the remote DNS can be specified in the /etc/resolv.conf file.

  2. The line search localdomain must be removed from the /etc/resolv.conf file on the Plesk server.

  3. Any DNS configurations on the local PSA server must be reflected on the external DNS server.

Other Changes

PSA creates some links to the MySQL libraries in the /usr/lib subdirectory and adds the @psacln string to /etc/ftpchroot.

Also, it adds a string to the file /etc/shells:

/bin/false

or

/usr/bin/false

If the POP3 service record is not in /etc/services, PSA adds it. PSA moves the sendmail binary file to sendmail.plesk. The PSA startup script is placed in the appropriate location to start PSA; this script will enable PSA to start each time the server is booted up.

IMPORTANT

You must install Plesk Server Administrator on a clean server; specifically only the operating system should be installed. Plesk Inc. will not be held liable for damages as a result of installing PSA on a server with anything other than a fresh installation of the operating system for which the PSA installation was intended.

Installing the Plesk Server Administrator

PSA Self-Extracting Install Procedure

Download the PSA software file to your server from http://www.plesk.com/downloads.

  1. Log in as "root" and change your working directory to the directory where the Server Administrator install script resides; for example: #cd /home/admin/psa

  2. Run the install script, for example: #sh."psa_install_file_name.sh"

  3. If you have a previous version of Plesk Server Administrator installed in the /usr/local/psa directory, the install script will detect it and stop.

  4. You will see several messages as the install script prepares for the installation.

  5. Next the script will display a series of messages showing the progress of the installation. At this time all of the components of Plesk Server Administrator will be installed and properly configured on the server. Depending on the speed of the server, there may be times when the installation seems to be stuck. The entire install procedure should take only a few minutes. Do not attempt to cancel the install script. The installation logs all of the changes made to the system in the /tmp/ directory. The install script will backup any system configuration files before making the changes.

  6. When the installation is complete, you will receive a message notifying you that psa is now running on your server. You will be able to use the Plesk Server Administrator on your host at: https://machine.domain.name:8443/ or https://IP-Address: 8443/

    The default username is "admin" and the default password is "setup". Both are case sensitive. For security reasons this password should be changed upon initial login.

    NOTE

    During installation mysql user 'root' is renamed to user 'admin' with appropriate password 'setup'. If the file /etc/.psa.shadow already existed in the system by the moment of installation then the password will not be 'setup' but will be the same as the one indicated in that file.

  7. Upon initial login to Plesk Server Administrator you will be required to complete the final steps in the installation process.

  8. You will first be asked to accept the Plesk, Inc. End User License Agreement. Select the appropriate checkbox at the end of the agreement and select Accept.

    NOTE

    You have the option to leave the license agreement active on the server if you wish.

  9. You will then be asked to verify the IP-address to be used for name-based hosting and the hostname and domain name associated with your server. These fields will be populated based on items already defined within your server parameters. Edit this information appropriately and select Update.

  10. You will then be asked to fill in the appropriate Administrator information. Once you have completed this, you will be able to utilize the full functionality of Plesk Server Administrator.

PSA RPM Install Procedure

The PSA 5.0 RPM installations require either RedHat® Linux 7.1 or RedHat® Linux 7.2 already installed on your system.

Installing PSA 5.0 for Linux RedHat® 7.1:

  1. You will first need to log in as "root" to your system.

  2. Before the installation, make sure that all the required libraries are installed.

    You can check whether a particular rpm is already installed by entering the following command: rpm -q 'rpmname'.

    For example:

    bash$ rpm -q pam

    pam-0.74-22

    You can also use our script 'query_rpm_for_prod.sh -vvv' to check the complete configuration of the system.

    Following is the list of required libraries and packages. You can check for their presence in the system: bash$ rpm -q db1 db3 freetype gd gdbm glibc krb5-libs libjpeg libpng libstdc++ libtermcap ncurses pam readline sharutils xinetd zlib

    If one or more of these libraries are not installed in the system it can be installed from the system installation CD or downloaded from ftp://ftp.redhat.com or from any of its mirrors and installed by entering the following command: rpm -Uvh 'rpm_name'.rpm

  3. Install the rpm's of indicated versions or higher from the RedHat® 7.1 disc:

    apache-1.3.19-5.i386.rpm

    bind-9.1.0-10.i386.rpm

    bind-utils-9.1.0-10.i386.rpm

    binutils-2.10.91.0.2-3.i386.rpm

    mod_perl-1.24_01-2.i386.rpm

    mod_ssl-2.8.1-5.i386.rpm

    mysql-3.23.36-1.i386.rpm

    mysql-devel-3.23.36-1.i386.rpm

    mysql-server-3.23.36-1.i386.rpm

    ntp-4.0.99k-15.i386.rpm

    openssl-0.9.6-3.i386.rpm

    openssl095a-0.9.5a-1.i386.rpm

    perl-5.6.0-12.i386.rpm

    php-4.0.4pl1-9.i386.rpm

    php-imap-4.0.4pl1-9.i386.rpm

    php-mysql-4.0.4pl1-9.i386.rpm

    shadow-utils-20000826-4.i386.rpm

    textutils-2.0.11-7.i386.rpm

    stunnel-3.13-3.i386.rpm

    From PowerTools disc: perl-libnet-1.0703-5.i386.rpm, webalizer-2.01_06-5.i386.rpm

    We also recommend to install:

    perl-DBI-1.14-10.i386.rpm

    perl-DBD-MySQL-1.2215-1.i386.rpm

    All of these rpm's are available on the RedHat® 7.1 installation CDs, at ftp://ftp.redhat.com or any of its mirrors, or from the directory 'std.rh-7.1' in your PSA archive (PSA-RPMS-full-rh7.1.buildXXXXXX.tar), or from the "Downloads" section at: http://www.plesk.com/

    For installation use the following command: rpm -Uvh 'rpm_name'.rpm

    IMPORTANT

    Pay attention to the options used. Utilizing -U instead of -i will help you avoid some problems during PSA installation.

  4. Install the base PSA rpm's from the directory 'base' in your PSA archive (PSA-RPMS-'...'-rh7.1.buildXXXXXX.tar), or from the "Downloads" section at: http://www.plesk.com/

    courier-imap-1.3.12-1psa.rh7.1.i586.rpm

    psa-courier-imap-add-2.5.0-rh7.1.build'...'.i586.rpm

    psa-locale-2.5.0-rh7.1.build'...'.noarch.rpm

    psa-proftpd-1.2.4rel-rh7.1.build'...'.i586.rpm

    psa-proftpd-xinetd-1.2.4rel-rh7.1.build'...'.i586.rpm

    psa-qmail-1.03-rh7.1.build'...'.i586.rpm

    psa-2.5.0-rh7.1.build'...'.i586.rpm

    For installation use the following command: rpm -Uvh 'rpm_name'.rpm

    IMPORTANT

    Pay attention to the options used. Utilizing -U instead of -i will help you avoid some problems during PSA installation.

  5. In order for your Apache to support FrontPage extensions and Apache::ASP it is necessary to install rpm's from the directories 'opt/fp' and 'opt/perl' respectively in your PSA archive (PSA-RPMS-'...'-rh7.1.buildXXXXXX.tar), or from the "Downloads" section at: http://www.plesk.com/

    However these packages are not required for PSA to function properly.

  6. When the installation is finished, Plesk Server Administrator will have started automatically. In order to complete the PSA initial configuration, you need to login to PSA on your host at: https://machine.domain.name:8443/ or https://IP-Address:8443/

    The default username is "admin" and the default password is "setup". Both are case sensitive. For security reasons this password should be changed upon initial login.

Installing PSA 5.0 for Linux RedHat® 7.2:

  1. You will first need to log in as "root" to your system.

  2. Below is the list of the needed rpm's:

    apache-1.3.20-16.i386.rpm

    bind-9.1.3-4.i386.rpm

    bind-utils-9.1.3-4.i386.rpm

    binutils-2.11.90.0.8-9.i386.rpm

    mod_perl-1.24_01-3.i386.rpm

    mod_ssl-2.8.4-9.i386.rpm

    mysql-3.23.41-1.i386.rpm

    mysql-devel-3.23.41-1.i386.rpm

    mysql-server-3.23.41-1.i386.rpm

    ntp-4.1.0-4.i386.rpm

    openssl-0.9.6b-8.i386.rpm

    openssl095a-0.9.5a-11.i386.rpm

    perl-5.6.0-17.i386.rpm

    php-4.0.6-7.i386.rpm

    php-imap-4.0.6-7.i386.rpm

    php-mysql-4.0.6-7.i386.rpm

    shadow-utils-20000902-4.i386.rpm

    textutils-2.0.14-2.i386.rpm

    stunnel-3.19-1.i386

    From the PowerTools disc:

    perl-libnet-1.0703-6.noarch.rpm

    webalizer-2.01_06-11.i386.rpm

    We also recommend to install:

    perl-DBI-1.18-1.i386.rpm

    perl-DBD-MySQL-1.2216-4.i386.rpm

    Necessary packages for the Apache-ASP:

    perl-Digest-MD5-2.13-1.i386.rpm

    perl-HTML-Parser-3.25-2.i386.rpm

    perl-HTML-Tagset-3.03-3.i386.rpm

    perl-libwww-perl-5.53-3.noarch.rpm

    perl-MIME-Base64-2.12-6.i386.rpm

    perl-Storable-0.6.11-6.i386.rpm

    perl-URI-1.12-5.noarch.rpm

    You can check whether a particular rpm is already installed by entering the following command: rpm -q 'rpmname'.

    For example:

    bash$ rpm -q pam

    pam-0.75-14

    You can also use our script 'query_rpm_for_prod.sh -vvv' to check the complete configuration of the system.

    For installation use the following command: rpm -Uvh 'rpm_name'.rpm

    IMPORTANT

    Pay attention to the options used. Utilizing -U instead of -i will help you avoid some problems during PSA installation.

  3. Install the base PSA rpm's from the directory 'base' in your PSA archive (PSA-RPMS-'...'-rh7.2.buildXXXXXX.tar), or from the "Downloads" section at: http://www.plesk.com/

    courier-imap-1.3.12-1psa.rh7.2.i586.rpm

    psa-courier-imap-add-2.5.0-rh7.2.build'...'.i586.rpm

    psa-locale-2.5.0-rh7.2.build'...'.noarch.rpm

    psa-proftpd-1.2.4rel-rh7.2.build'...'.i586.rpm

    psa-proftpd-xinetd-1.2.4rel-rh7.2.build'...'.i586.rpm

    psa-qmail-1.03-rh7.2.build'...'.i586.rpm

    psa-2.5.0-rh7.2.build'...'.i586.rpm

    For installation use the following command: rpm -Uvh 'rpm_name'.rpm

    IMPORTANT

    Pay attention to the options used. Utilizing -U instead of -i will help you avoid some problems during PSA installation.

    Before installation of the base rpm's make sure that xinetd is already started.

    For example:

    bash$ ps -ax|grep xinetd

    4377 ? S 0:00 xinetd

    If you do not find it working, make sure that it is installed in the system by means of a command:

    rpm -q xinetd

    and if it is not installed in the system, install it.

    start it yourself:

    bash$ service xinetd start

  4. In order for your Apache to support FrontPage extensions and Apache::ASP it is necessary to install rpm's from the directory 'opt/fp' and 'opt/perl' respectively in your PSA archive 'PSA-RPMS-'...'-rh7.2.buildXXXXXX.tar', or from the "Downloads" section at: http://www.plesk.com/

    However these packages are not required for PSA to function properly.

  5. When the installation is finished, Plesk Server Administrator will have started automatically. In order to complete the PSA initial configuration, you need to login to PSA on your host at: https://machine.domain.name:8443 or https://IP-Address:8443/

    The default username is "admin" and the default password is "setup". Both are case sensitive. For security reasons this password should be changed upon initial login.

Error Messages

You may receive the following error message when installing the Plesk Server Administrator:

===> Installing MySQL Server

Checking for the group 'mysql'...

ERROR:

It seems that there is group 'mysql' in your system. PSA uses the same group name but with another group ID ('3306'). Sorry, but this situation is not properly handled yet. Please contact support@plesk.com'

This situation indicates that whomever is installing the Plesk Server Administrator is probably installing it remotely via Telnet. If this error occurs, the 'su-' (superuser) command was not executed. Please contact us at support@plesk.com or 1-703-815-5670 for technical assistance.

Installing the Key License

To activate PSA for the purchased number of domains, you must install the key license that is sent to you in an email. Key installation instructions are as follows:

  1. Transfer the key file to the server.

  2. Change to super-user with the "su -" command.

  3. Access the directory where you transferred the key file.

  4. Execute the key file shell script PLSK.dddddddddd.vvvv.sh.

    'sh PLSK.dddddddddd.vvvv.sh'

    NOTE

    PLSK.dddddddddd.vvvv - where dddddddddd is the key number consisting of ten digits, and vvvv is the key version consisting of four digits.

  5. The script will automatically restart the Plesk server with the new key.

Uninstalling Plesk Server Administrator

The process of uninstalling Plesk Server Administrator for systems that run under RedHat® Linux slightly differs from that of the systems that run under FreeBSD. One of the following sections will guide you through the process of uninstalling PSA depending on the type of Operating System you are running.

NOTE

Exercise extreme caution. The whole PSA directory will be deleted without confirmation. This action is not reversible. Make sure you have anything you want to save placed safely somewhere else before you run the uninstall function, as it will return your server to the state that it was in before PSA was installed. HTML documents, log files, outstanding email, and mySQL databases will all be deleted.

Uninstalling self-extracted PSA for RedHat® Linux

  1. First, log in through telnet and change to super-user with the "su -" command, if you have local access, log in as root.

  2. Run /usr/local/psa/admin/bin/deinstall.sh deinstall. This will remove PSA 5.0 from the system.

  3. Delete /etc/psa directory.

  4. Delete PSA users and groups from:

    • /etc/ftpchroot

    • /etc/ftpusers

    • /etc/passwd

    • /etc/shadow

    • /etc/group

    PSA system users:

    • bind

    • mysql

    • apache

    • psaadm

    • psaftp

    • qmaild

    • qmaill

    • qmailp

    • qmailq

    • qmailr

    • qmails

    • popuser

    • +all users with group=psacln (ftpusers and webusers)

    PSA system groups:

    • psaftp

    • qmail

    • popuser

    • psaadm

    • psacln

  5. Delete PSA startup scripts located in /etc/rc.d/init.d/

  6. Delete PSA services ftp, and smtp from /etc/xinetd.conf and /etc/xinetd.d directory, restart xinetd.

  7. Delete /etc/sysconfig/named

  8. Restore link to your sendmail /usr/lib/sendmail and /usr/sbin/sendmail

  9. Delete link /etc/named.conf

  10. Delete /tmp/.state directory

Uninstalling RPM-installed PSA for RedHat® Linux

  1. First, log in through telnet and change to super-user with the "su -" command. If you have local access, log in as 'root'.

  2. Run the following command:

    rpm -e --nodeps psa psa-proftpd psa-proftpd-xinetd psa-qmail courier-imap psa-courier-imap-add psa-locale psa-locale-ru

    This will remove PSA 5.0 modules from the system.

  3. Delete /usr/local/psa directory, if it still remained after the previously executed command.

    Delete /usr/lib/courier-imap directory.

    Delete /var/qmail directory.

    Delete /etc/psa directory.

  4. Delete PSA users and groups from:

    • /etc/ftpchroot

    • /etc/ftpusers

    • /etc/passwd

    • /etc/shadow

    • /etc/group

    PSA System Users:

    • psaadm

    • psaftp

    • qmaild

    • qmaill

    • qmailp

    • qmailq

    • qmailr

    • qmails

    • popuser

    • +all users with group=psacln (ftpusers and webusers)

    PSA System Groups:

    • psaftp

    • qmail

    • popuser

    • psaadm

    • psacln

  5. Delete PSA startup scripts located in /etc/rc.d/init.d/

  6. Delete PSA services ftp, and smtp from /etc/xinetd.conf and /etc/xinetd.d directory, restart xinetd.

  7. Delete /etc/sysconfig/named

  8. Restore link to your sendmail /usr/lib/sendmail and /usr/sbin/sendmail

  9. Delete /tmp/.state directory

Uninstalling PSA for FreeBSD

  1. First, log in through telnet and change to super-user with the "su -" command. If you have local access, log in as 'root'.

  2. Run usr/local/psa/admin/bin/deinstall.sh deinstall. This will remove PSA 5.0 from the system.

  3. Delete /etc/psa directory.

  4. Delete PSA users and groups from

    • /etc/ftpchroot

    • /etc/ftpusers

    • /etc/passwd

    • /etc/master.passwd

    • /etc/group

    PSA system users

    • bind

    • mysql

    • apache

    • psaadm

    • psaftp

    • qmaild

    • qmaill

    • qmailp

    • qmailq

    • qmailr

    • qmails

    • popuser

    • +all users with group=psacln (ftpusers and webusers)

    PSA system groups:

    • psaftp

    • qmail

    • popuser

    • psaadm

    • psacln

  5. Delete PSA startup scripts located in /usr/local/etc/rc.d/.

  6. Delete PSA services ftp, and smtp from /etc/inetd.conf, restart inetd.

  7. Delete /etc/sysconfig/named

  8. Restore link to your sendmail /usr/lib/sendmail and /usr/sbin/sendmail

  9. Delete link /etc/named.conf

  10. Delete /tmp/.state directory.

to top