Skip to main content

CLOUDLINUX INSTALLATION

1) Download the cloud linux auto installer from http://www.cloudlinux.com/downloads/index.php
For cpanel servers, use the following steps
a) For IP-based CloudLinux license
#  /usr/local/cpanel/cpkeyclt 
# /usr/local/cpanel/bin/cloudlinux_system_install -k
b) For license key based CloudLinux ( for getting key go to https://cln.cloudlinux.com/clweb/register.html and register )
wget http://repo.cloudlinux.com/cloudlinux/sources/cln/cpanel2cl
sh cpanel2cl -k $key
2) Now reboot your server into the Cloud linux kernel
root@kate ~]# uname -r
2.6.18-374.12.1.el5.lve0.8.54
It have few issues with the RAM memory so we need to install PAE kernel for the Cloud linux
yum install kernel-PAE-2.6.18-374.12.1.el5.lve0.8.54
after installing the Cloud linux kernel we  will get the kernel as
And reboot the server.
root@kate ~]# uname -r
2.6.18-374.12.1.el5.lve0.8.54PAE
Then Recompile apache using /scripts/easyapache
3) Install the lve cPanel modules and Plugin as follows,
yum  -y install cpanel-lve   cpanel-lvemanager
4) Compile apache and php with the following minimal requirements, - Make sure to use Apache 2.2.x version - Suexec must be enabled - Apache MPM will be Prefork, Worker or Event . Better to user preforker
5) Now go to WHM -> Plugins -> LVE Manager and monitor the use . You can set the limits per domain from here
6) Memory limit is disabled by default in cl5. Please check it and enable it by ( lvectl ubc status/enable/disable )

7) If the client provides us with the activation key to license clould linux which is already installed as trial version in the server, use the following command:
rhnreg_ks --activationkey=<key>--force
This will license the cloud linux installed.
8) to check if the server where we installed cloudlinux is licensed and is not in its trial period use the following:
- install a package named rhn-setup
 yum install rhn-setup
- use command "rhn_check". If this command does not yield any result, the server is licensed. If an error is obtained as output, its trial version.

Reference:

Comments

Popular posts from this blog

How to tweak linux server harddisk using hdparm

hdparm switches explained http://manpages.ubuntu.com/manpages/intrepid/man8/hdparm.8.html   First of all you have to install hdparm in linux. apt-get install hdparm #hdparm /dev/sda /dev/sda: readonly = 0 (off) readahead = 120 (on) geometry = 8850/255/63, sectors = 142182912, start = 0 Hard disk Performance Information # hdparm -tT /dev/hda /dev/hdd: Timing cached reads: 496 MB in 2.00 seconds = 247.42 MB/sec Timing buffered disk reads: 60 MB in 3.03 seconds = 19.81 MB/sec Hard drive set to low, slow settings # hdparm -cuda /dev/hda /dev/hda: IO_support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 0 (off) readahead = 256 (on) Use below tweaks to increase disk read write performance. For sda drive ~]# hdparm -a 2048 /dev/sda /dev/sda: setting fs readahead to 2048 readahead = 2048 (on) For sdb drive [root@439298a ~]# hdparm -a 2048 /dev/sdb /dev/sdb: setting fs readahead to 2048 readahead = 2048 (on) ]# echo “anticipatory” >...

Modsecurity block rule for XMLRPC and wp-login attack

SecAction phase:1,nolog,pass,initcol:ip=%{REMOTE_ADDR},initcol:user=%{REMOTE_ADDR},id:5000134  <Locationmatch "/wp-login.php">  SecRule user:bf_block "@gt 0" "deny,status:401,log,id:5000135,msg:'ip address blocked for 5 minutes, more than 10 login attempts in 3 minutes.'"  SecRule RESPONSE_STATUS "^302" "phase:5,t:none,nolog,pass,setvar:ip.bf_counter=0,id:5000136"  SecRule RESPONSE_STATUS "^200" "phase:5,chain,t:none,nolog,pass,setvar:ip.bf_counter=+1,deprecatevar:ip.bf_counter=1/180,id:5000137"  SecRule ip:bf_counter "@gt 10" "t:none,setvar:user.bf_block=1,expirevar:user.bf_block=300,setvar:ip.bf_counter=0"  </Locationmatch>  SecAction phase:1,nolog,pass,initcol:ip=%{REMOTE_ADDR},initcol:user=%{REMOTE_ADDR},id:5000234  <Locationmatch "/xmlrpc.php">  SecRule user:bf_block "@gt 0" "deny,status:401,log,id:5000235,msg:'ip address blocked for 5 m...

Apache tuning documentation

Apache bench marking ======================= Things or checklist to be considered before the test     CPU: avoid power-saving mode. cpufreq-set -g performance.     File descriptors: raise the limit to (at least) the number of concurrent connections you wish to handle, using ulimit -n in your shell, or setrlimit(RLIMIT_NOFILE) in your server. Beware, some systems forbid you to raise the limit, you might need to investigate a bit to find how to unlock it.     Disable the logs of your server (you do not want to lose time logging thousands of requests instead of answering them).     Raise /proc/sys/net/somaxconn to the number of concurrent connections you want to handle. To understand why this is necessary, read the technical report or the excellent paper Measuring the Capacity of a Web Server (Banga and Druschel, Usenix 97). More on the fascinating topic of the accept() queue can be found in accept()able Strategies for Im...