Documentation on installation of PLESK on Centos/ Linux server:

PreChecks before the installation:

SSH to the server on which Plesk needs to be installed and check following:

1. Type nmap localhost
2. If nmap is not installed than type yum install nmap and hit enter.
3. Check if bind is installed on the server by following command:

rpm –qa |grep bind*

If bind is installed and you see any packages as a result, remove the bind by following command:

yum remove bind*

4. Check the architecture of the server( 32bit/64bit) by following command: uname –a
5. As per the OS (32bit/64bit), the plesk will be installed on the server.

Downloading and installing PLESK from Parallel’s website.

After checking the OS type, download the corresponding package in the temp directory of the server:

·         Go to https://www.parallels.com/account/flag,4/?request_url=http://www.parallels.com/download/plesk9/

Uname: abc@abc.com

Password: abc

Download the Auto-installer utility that suits your operating system from here and save it on your server's hard drive.

eg : [root@server tmp]# wget plesk_auto_installer_file_name

Set the execution permission for Auto-installer:

eg : [root@server tmp]# chmod a+x plesk_auto_installer_file_name

Run the Auto-installer:

eg : [root@server tmp]# ./plesk_auto_installer_file_name

Here's a sample of installing Plesk control panel 9.2.3 on CentOS 5.x

Select the desired products and their versions =============================================================================== The following product versions are available: 1. [*] Plesk Control Panel 2. [ ] Parallels Small Business Panel 3. [ ] Sitebuilder 4. [ ] SSO

Select the components that you wish to install by selecting the installation type for Plesk Control Panel.

By default, typical installation is selected. It includes a minimal number of packages required for Plesk to work. To install all components of Plesk including all Plesk modules and Web applications, select Full installation. To install only selected components, select Custom installation. In this screen, choose the proper installation type and press ENTER.

Select the third [Custom] option by entering 3 & press ENTER. 3. (*) Custom Custom components selection. Recommended only for experienced users.

To review the components that will be installed, type L and then press ENTER. The selected packages are marked with [*] symbols. To select or deselect a package, type the corresponding number and press ENTER.  1. [*] Base packages of Plesk  2. [*] Plesk Updater  3. [*] PHP5 support  4. [*] PostgreSQL server support  5. [*] Application vault packages  6. [ ] Plesk Professional Web Site Editor  7. [*] Plesk API [former Plesk Agent]  8. [*] Plesk migration manager  9.  [ ] SiteBuilder publishing support for Plesk 10. [ ] SiteBuilder module migration suite 11. [ ] ColdFusion support for Plesk 12. [ ] MIVA Empresa support 13. [ ] Plesk billing 14. [.] <+> Plesk hosting features // 3 of 5 components selected   Different mailservers 15. (*) Qmail mailserver 16. ( ) Postfix mailserver 17. [.] <+> Additional Plesk modules // 3 of 5 components selected 18. [ ] <+> Game servers // 0 of 3 components selected 19. [.] <+> Addition mail services // 2 of 4 components selected 20. [.] <+> Server backup solutions // 1 of 2 components selected 21. [ ] <+> Additional language packs // 0 of 9 components selected 22. [*] <+> Plesk webmails support // 2 of 2 components selected

Few of them have sub-components & they need to be selected too:

[*] <+> Plesk hosting features // 6 of 6 components selected  [*] <+> Additional Plesk modules // 5 of 5 components selected  [.] <+> Addition mail services // 4 of 5 components selected  [*] <+> Server backup solutions // 1 of 1 components selected  [*] <+> Plesk webmails support // 2 of 2 components selected

[*] <+> Plesk hosting features // 6 of 6 components selected 1. [*] Bandwidth Limiter For Apache support (mod_bw) 2. [*] Apache ASP support 3. [*] Tomcat Java Servlets support 4. [*] Apache mod_python module 5. [*] Ruby on Rails support 6. [*] FastCGI support (mod_fcgid)

[*] <+> Additional Plesk modules // 5 of 5 components selected 1. [*] Plesk Firewall module 2. [ ] Plesk VPN module 3. [*] Plesk Fileserver module and SMB file server package 4. [*] SSHTerm - SSH Terminal java applet 5. [*] Watchdog (System monitoring module)

[.] <+> Addition mail services // 4 of 5 components selected 1. [*] Mailman mailing list manager support 2. [ ] Kaspersky antivirus module 3. [ ] Dr. Web antivirus 4. [*] SpamAssassin support 5. [ ] Real-time Blackhole List client for qmail

[*] <+> Server backup solutions // 1 of 1 components selected 1. [*] Plesk Backup Manager  [*] <+> Plesk webmails support // 2 of 2 components selected  1. [*] Horde webmail support  2. [*] AtMail webmail support

To continue with installation, type 'n' and press ENTER. When prompted, confirm installing: type 'n' and press ENTER again.

The packages will be downloaded and installed automatically. Hence you can get yourself a cup of coffee in the meantime
When the installation is finished a trial license key is installed for evaluation purposes & Plesk will have started automatically..
Now to complete the initial configuration, log in to the Plesk control panel running on your host:

Quote:

https://hostname.domain.name:8443/ https://ip-address:8443/

How To Configure Nagios Monitoring Tool In Linux

How To Configure Nagios Monitoring Tool In CentOs

·       Why We Use nagios

We run Nagios to monitor roughly 35 servers and several hundred services in our environment. We even use it to monitor about 20 websites we host and notify us when SSL certificates need to be renewed. Nagios is a very robust and customizable solution, it's not the easiest thing in the world to configure, but well worth the effort. I may do a video to go a long with this article at some point.

Disable selinux

• # setenforce 0

Install required packages

• # yum install httpd gcc glibc glibc-common gd gd-devel php

Create Nagios User & Group

• # useradd -m nagios

• # groupadd nagcmd

Add nagios user and apache user to nagios group

• # usermod -a -G nagcmd nagios
• # usermod -a -G nagcmd apache

Create Directory for nagios download

• # mkdir /etc/downloads
• # cd /etc/downloads

Download Nagios and Plugins files

• # wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.3.tar.gz
• # wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.15.tar.gz

Extract files

• # tar xzf nagios-3.2.3.tar.gz
• # tar xzf nagios-plugins-1.4.15.tar.gz

Configure/Compile

• # cd /etc/downloads/nagios-3.2.3
• # ./configure --with-command-group=nagcmd
• # make all
• # make install
• # make install-init
• # make install-config
• # make install-commandmode
• # make install-webconf

Create Web Interface User account

• # htpasswd -c /usr/local/nagios/etc/htpasswd.users admin

Restart Apache:

• # service httpd restart

Install Nagios Plugins

• # cd /etc/downloads/nagios-plugins-1.4.15.tar.gz

Configure/Compile

• # ./configure --with-nagios-user=nagios --with-nagios-group=nagios
• # make
• # make install

Enable Nagios to start at system startup

• # chkconfig --add nagios
• # chkconfig nagios on
• # chkconfig httpd on

Start Nagios service

• # service nagios start

How To Open Nagios After Successfully Installing.

Log in to http://IPOFSERVER/nagios

Passwordless ssh access

The SSH protocol is recommended for remote login and remote file transfer which provides confidentiality and security for data exchanged between two computer systems, through the use of public key cryptography. The OpenSSH server provides this kind of setup under Linux. It is installed by default. But in window we need to use 3^rd party software link putty.

Here I am sharing some basic steps to create ssh keys & to access remote system via key

Case 1) for Linux to Linux box

Step a) create public private key for system

$ ssh-keygen -t rsa

Generating public/private rsa key pair.

Enter file in which to save the key (/home/user/.ssh/id_rsa): [press enter for default]

Enter passphrase (empty for no passphrase): [not shown]

Enter same passphrase again: [not shown]

Your identification has been saved in /home/user/.ssh/id_rsa.

Your public key has been saved in /home/user/.ssh/id_rsa.pub.

The key fingerprint is:                               

44:c8:07:c9:f8:f4:f5:9b:05:d1:0f:d1:05:f0:5d:bf user@localhost $

 Step b) copy public key to remote system authorized key file

$ scp ~/.ssh/id_rsa.pub user@somehost:/home/user/.ssh/authorized_keys

user@somehost's password: [not shown]

id_rsa.pub           100% |*****************************|   225 00:00

After copy you can access your remote host without asking for password

Case 2) for window to Linux box

As we know putty is most popular windows ssh client. First of all i downloaded puTTygen and putty software from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. Then I executed puttygen to generate private and public keys. I saved my public key file as user.pub and private key file as user.ppk.

Now public file has to be transferred on Linux system, after transfer i written following line on Linux system to import public key into authorized key

   root#ssh-keygen -i -f user.pub >>/root/.ssh/authorized_key

Now my ssh server is ready to accept private key for authentication.
Finally i executed putty and specify following parameters
         IP address of Linux box
         default username as 'root'
         and location of private key file.
And Linux box get connected without asking password