The first time you use the Perl module CPAN, a script is executed in order to properly configure several options (like the location of tar, gzip and unzip files, the cache size for the build directory, etc).

If you want to modify these configuration options at a later time, you can do it in 2 ways:

- Manually, modifying the configuration files

You can either modify the user-specific file (usually ~/.cpan/CPAN/MyConfig.pm) or the system-wide configuration file (stored somewhere in the perl module directory tree, look for a directory named CPAN that holds a file named Config.pm)

- Automatically, using the CPAN module

To do this, execute the following:

perl -MCPAN -e shell

When you’re in the cpan shell, execute:

cpan> o conf init

UPDATED: January 31st, 2011: Python 2.6 now is in the normal EPEL repositories. There are some changes in the explanations below

I’ve always hated Centos, probably because I’ve never been in a situation where I had to deal with the network security (other than the obvious stuff to ward off cross-site-scripting attacks and the such). Of course, that being the case, I did wind up dealing with CentOS at work and I had to get Django, Python 2.6 and the such functional.

Centos throws a few curveballs your way.. YUM is built on Python 2.4, and upgrading to a newer version supposedly breaks the program. Going back to Python 2.4 was not an option, mainly because all my python experience is on Python 2.5 / 2.6, and I don’t want to go back and learn an older non-maintained version of the language for a server. On the other hand, I didn’t want to lobby to just install Ubuntu.

This assumes you already have a normal LAMP setup. Furthermore, I’m assuming you do not have mod_python installed. This threw me for a loop for the longest time, so take this for what its worth.

The VERY FIRST STEP (if you are running a clean install of CentOS) is to get the dev tools installed.


# sudo yum groupinstall 'Development Tools'


After that, install Python 2.6 (or anything else newer in the 2.x series). As of January 31st, these are in the EPEL repositories; if you don’t have the EPEL repositories enabled, do the following:


# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
# yum repolist


Once that’s done, run yum update to get everything setup, and then install Python & the MySQL dependencies (if they aren’t already installed)


# yum install python26* mysql-devel mysql-server


This installs pretty much everything Python- & MySQL-related that you need. You will need to run the following to get an extra piece of information:


Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.prefix
'/usr'


The prefix (/usr) is important for later. Set it aside and finish up.


# cd ~
# wget http://sourceforge.net/projects/mysql-python/files/mysql-python/1.2.3/MySQL-python-1.2.3.tar.gz/download
# sudo tar xzvf MySQL-python-1.2.3.tar.gz
# cd MySQL-python-1.2.3*
# python26 setup.py install


(Don’t forget to create a user for use by Django in the database)


# cd ~
# wget http://modwsgi.googlecode.com/files/mod_wsgi-3.3.tar.gz
# sudo tar xzvf mod_wsgi-3.3.tar.gz
# cd mod_wsgi-3.3*
# ./configure --with-python=/usr/bin/python2.6
# make
# make install


Now you need to fix up your Apache configuration. I won’t pretend to be an expert with WSGI (although I’ve managed to get it running on 3 different OSes running Apache), but make sure you include the following, somewhere near the Module block in the httpd.conf file.


WSGIPythonHome /usr/


As long as you have this setup, and a proper WSGI script, you should be able to get up and running.

The Django installation is quite easy. Go into the Django source directory and type in

# python2.6 setup.py install

That will take care of making sure Python2.6 also has access to django.

If you don’t want to install using the source code, you can also do this through pip. Follow the instructions here to install pip (while updating the version of pip to 0.8.2) and then type in

# pip install django

That’s pretty much it. I’m sure there is something unclear, but I’ve got to get back to work -_-

What is LiteSpeed Web Server ?

LiteSpeed Web Server is the leading high-performance, high-scalability web server. It is completely Apache interchangeable so LiteSpeed Web Server can quickly replace a major bottleneck in your existing web delivery platform. With its comprehensive range of features and easy-to-use web administration console, LiteSpeed Web Server can help you conquer the challenges of deploying an effective web serving architecture.

In this tutorial we will upgrade current litespeed PHP to support PHP 5.3.0, Mail header patch and suhosin patch

What is Suhosin ?

Suhosin is the big brother to the Hardened-PHP patch which adds an extra level of protection to PHP.

In this tutorial, i’ve tried to compile all packages from litespeed web server web interface but it’s failed.
so i prefer to configured it manually.

Download All Sources

Login as root

#cd /root
#wget http://uk.php.net/distributions/php-5.3.0.tar.gz
#wget http://download.suhosin.org/suhosin-patch-5.3.0-0.9.8-BETA-1.patch.gz
#wget http://choon.net/opensource/php/php-5.3.0-mail-header.patch
#wget http://www.litespeedtech.com/packages/lsapi/php-litespeed-4.10.tgz
#wget http://ftp.gnu.org/gnu/autoconf/autoconf-2.13.tar.gz

Extract Packages

#cd /root
#tar -zxvf php-5.3.0.tar.gz
#gunzip suhosin-patch-5.3.0-0.9.8-BETA-1.patch.gz
#tar -zxvf autoconf-2.13.tar.gz

Install autoconf

#cd /root
#cd autoconf-2.13
#./configure && make && make install

Compile PHP 5.3.0 with PHP mail header , Suhosin and PHP-Litespeed

#cd /root
#cd php-5.3.0

Patching PHP mail header & Suhosin

#patch -p1 < /root/php-5.3.0-mail-header.patch
#patch -p1 < /root/suhosin-patch-5.3.0-0.9.8-BETA-1.patch

Exctract and Compile PHP-litespeed

#cd /root
#cp php-litespeed-4.10.tgz /root/php-5.3.0/sapi
#tar -zxvf php-litespeed-4.10.tgz
#cd /root/php-5.3.0
#touch ac*
#./buildconf --force

Compile All

#cd /root/php-5.3.0
# ./configure --with-litespeed --prefix=/usr/local/lsws/lsphp5 --with-mysql --with-zlib --with-gd --enable-shmop --enable-track-vars --enable-sockets --enable-sysvsem --enable-sysvshm --enable-magic-quotes --enable-mbstring --with-iconv --with-mcrypt --with-curl --with-ftp --with-gettext --with-ttf --enable-suhosin --enable-gd-native-ttf --with-jpeg-dir=/usr/local/lib --with-freetype-dir=/usr/local/lib --with-kerberos --with-openssl --with-mhash --with-pcre-regex=/usr/local --with-pear --with-png-dir=/usr/local/lib --enable-zip -enable-bcmath --enable-calendar --with-mysqli=/usr/bin/mysql_config
#make

If make is running successfully then stop here.

Copy PHP Binary to litespeed fcgi-bin Directory

#cd /usr/local/lsws/fcgi-bin
#unlink lsphp5
#cp /root/php-5.3.0/sapi/litespeed/php lsphp-5.3.0
#ln -s ./lsphp-5.3.0 lsphp5

Verify PHP Version

#./lsphp5 -v
PHP 5.3.0 with Suhosin-Patch (litespeed) (built: Sep 13 2009 22:29:50)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies

If you see any error like below :

#./lsphp5 -v
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/suhosin.so’ – Cannot open "/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/suhosin.so" in Unknown on line 0PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/xcache.so’ – Cannot open "/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/xcache.so" in Unknown on line 0PHP 5.3.0 with Suhosin-Patch (litespeed) (built: Sep 13 2009 22:29:50)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies

IMPORTANT :
This is mean you need to recompile XCACHE and SUHOSIN Packages.

Restart Litespeed Webserver

#/usr/local/lsws/bin/lswsctrl stop
#/usr/local/lsws/bin/lswsctrl start

Here is the PHPINFO result :

Download RPMForge Package. Check your system with uname -a command to get the suitable package. Below is the current one I got :

32-bit system:
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm

64-bit system
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm

If you want to check for the latest one, check it from -> http://packages.sw.be/

My instruction will base on x86_64 package.

2. Install GPG Key for DAG
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
Verify the package
rpm -K rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm

After verification, install RPMForge package.
rpm -i rpmforge-release-0.5.2-2.el5.rf.x86_64.rp

Run command below : Basically, it will install Munin, set it to run at startup, start munin, create folder for munin to access through the web. (You can just copy and paste into your SSH)

yum install munin munin-node
chkconfig –levels 235 munin-node on
/etc/init.d/munin-node start
chown -R munin:munin /var/www/munin
ln -s /var/www/munin /var/www/html/munin
service httpd restart && service crond restart

That’s it. You may also want to protect your munin directory so that no one without password will not be able to access. What you have to do is

nano /var/www/html/munin/.htaccess

AuthType Basic
AuthName “Members Only”
AuthUserFile /var/www/munin/.htpasswd

require valid-user

Then, save it.

7. Create .htpasswd file contains username and password to allow to access your munin (Here munin-admin is a username)

htpasswd -c /var/www/munin/.htpasswd munin-admin

Then enter your password and that’s it. Alternatively, if you don’t have htpasswd program on your server, you can just create .htpasswd file and put username and password in it. The password has to be encoded in MD5 format. (You can google and find any htpasswd generator. The format will be :

username:password

Troubleshoot : If there is no graph and you see /var/log/munin/munin-html.log like below

Jul 24 11:50:10 – processing domain: localhost
Jul 24 11:50:10 – processing node: localhost
Jul 24 11:50:10 – processing service: apache_accesses
Jul 24 11:55:11 – Starting munin-html, checking lock
Jul 24 11:55:11 – could not copy style.css into htmldir
Jul 24 11:55:11 – could not copy logo.png into htmldir
Jul 24 11:55:11 – could not copy definitions.html into htmldir
Jul 24 11:55:11 – processing domain: localhost
Jul 24 11:55:11 – processing node: localhost
Jul 24 11:55:11 – processing service: apache_accesses

or error in /var/log/munin/munin-graph.log

Jul 24 11:55:11 – Unable to graph /var/lib/munin/localhost/localhost-ntp_clock_nectec_or_th-jitter-g.rrd: Could not save png to ‘/var/www/munin/localhost/localhost-ntp_clock_nectec_or_th-year.png’
Jul 24 11:55:11 – Graphed service : ntp_clock_nectec_or_th (0.08 sec * 4)
Jul 24 11:55:11 – Unable to graph /var/lib/munin/localhost/localhost-vmstat-sleep-g.rrd: Could not save png to ‘/var/www/munin/localhost/localhost-vmstat-month.png’
Jul 24 11:55:11 – Unable to graph /var/lib/munin/localhost/localhost-vmstat-sleep-g.rrd: Could not save png to ‘/var/www/munin/localhost/localhost-vmstat-week.png’
Jul 24 11:55:11 – Unable to graph /var/lib/munin/localhost/localhost-vmstat-sleep-g.rrd: Could not save png to ‘/var/www/munin/localhost/localhost-vmstat-day.png’
Jul 24 11:55:11 – Unable to graph /var/lib/munin/localhost/localhost-vmstat-sleep-g.rrd: Could not save png to ‘/var/www/munin/localhost/localhost-vmstat-year.png’
Jul 24 11:55:11 – Graphed service : vmstat (0.07 sec * 4)
Jul 24 11:55:11 – Processed node: localhost (2.94 sec)
Jul 24 11:55:11 – Processed domain: localhost (2.94 sec)
Jul 24 11:55:11 – Munin-graph finished (2.95 sec)

Then, check ownership of your munin file and directory. I got the problem with a directory (www) above munin directory. Original is :

dr-xr-x— 10 webapps apache 4096 Jul 25 13:54 www

I, then, have to chmod 755 /var/www to make it work. After I chmod it, below is what it will look like :

drwxr-xr-x 10 webapps apache 4096 Jul 25 13:54 www

Tested with :
CentOS 5.6 – 64 bits
DirectAdmin 1.39.1 – With Custombuild 1.2
PHP 5.3.6

Update : 2011.08.08
You may want to use EPEL repository instead which will give you a newer version of Munin (1.4.5 vs 1.2.x). If you do, then, do the following :

Download EPEL repository
wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Install it
rpm -Uvh epel-release-5-4.noarch.rpm
Then, continue with step 5 above.

I try to use Nginx as a reverse proxy to see if there is any improvement over Apache Worker MPM or not. I found an instruction from DirectAdmin webboard but it’s quite old. So, I just tried to follow their steps and do some modification to match what I have read. Below is what I did

1. You need to compile Nginx. Nginx version 0.8.54 is the lastest stable release as of today. So, just copy and paste below code into your SSH

wget http://sysoev.ru/nginx/nginx-0.8.54.tar.gz
tar xvfz nginx-0.8.54.tar.gz
cd nginx-0.8.54
./configure --with-http_stub_status_module --with-http_gzip_static_module
make
make install

After installed, path related to Nginx is shown below : (Note that since you compile Nginx, there is no nginx.pid file there. You need to write it.)

nginx path prefix: "/usr/local/nginx"
nginx binary file: "/usr/local/nginx/sbin/nginx"
nginx configuration prefix: "/usr/local/nginx/conf"
nginx configuration file: "/usr/local/nginx/conf/nginx.conf"
nginx pid file: "/usr/local/nginx/logs/nginx.pid"
nginx error log file: "/usr/local/nginx/logs/error.log"
nginx http access log file: "/usr/local/nginx/logs/access.log"
nginx http client request body temporary files: "client_body_temp"
nginx http proxy temporary files: "proxy_temp"
nginx http fastcgi temporary files: "fastcgi_temp"
nginx http uwsgi temporary files: "uwsgi_temp"
nginx http scgi temporary files: "scgi_temp"

2. Edit configuration file:

nano -w /usr/local/nginx/conf/nginx.conf

Code is like below :

user apache apache;

worker_processes 4; # Set it according to what your CPU have. 4 Cores = 4
worker_rlimit_nofile 8192;

pid /var/run/nginx.pid;

events {
worker_connections 1024;
}

http {
include mime.types;
default_type application/octet-stream;

log_format main ‘$remote_addr – $remote_user [$time_local] ‘
‘”$request” $status $body_bytes_sent “$http_referer” ‘
‘”$http_user_agent” “$http_x_forwarded_for”‘;

server_tokens off;
access_log /var/log/nginx_access.log main;
error_log /var/log/nginx_error.log debug;

server_names_hash_bucket_size 64;
sendfile on;
tcp_nopush on;
tcp_nodelay off;
keepalive_timeout 30;
gzip on;
gzip_comp_level 9;
gzip_proxied any;

proxy_buffering on;
proxy_cache_path /usr/local/nginx/proxy_temp levels=1:2 keys_zone=one:15m inactive=7d max_size=1000m;
proxy_buffer_size 16k;
proxy_buffers 100 8k;
proxy_connect_timeout 60;
proxy_send_timeout 60;
proxy_read_timeout 60;

server {
listen xxx.xxx.xxx.xxx:81 default rcvbuf=8192 sndbuf=16384 backlog=32000; # Real IP here
server_name domain.name _ ; # “_” is for handle all hosts that are not described by server_name
charset off;
access_log /var/log/nginx_host_general.access.log main;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://xxx.xxx.xxx.xxx; # Real IP here
client_max_body_size 16m;
client_body_buffer_size 128k;
proxy_buffering on;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 120;
proxy_buffer_size 16k;
proxy_buffers 32 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
}
}
# below is include so that you can have separate setting per vhost.
include /usr/local/nginx/vhosts/*.conf;
}

In the above config, it’s general reverse proxy for all domain name on DirectAdmin server. If you need to have a separate configuration like domain A to really use Nginx as a web server, not reverse proxy, then, you can just create that configuration file inside “/usr/local/nginx/vhosts/”. Or you may need to change something different from global setting. Just create a new configuration file for that specific Virtualhost.

Also, insert code below if you want to monitor Nginx from Munin or anything similar :

server {
listen 127.0.0.1:81;
server_name localhost;
location /nginx_status {
stub_status on;
access_log off;
allow xxx.xxx.xxx.xxx; # Real IP here
allow 127.0.0.1;
deny all;
}
}

Here, I have to set localport to use port 81 since it’s the port that we use to monitor this Nginx setup.

3. Create init.d script to be able to start stop nginx service.

nano -w /etc/init.d/nginx

Copy and paste the code below :

#!/bin/sh
#
# nginx – this script starts and stops the nginx daemin
#
# chkconfig: – 85 15
# description: Nginx is an HTTP(S) server, HTTP(S) reverse \
# proxy and IMAP/POP3 proxy server
# processname: nginx
# config: /usr/local/nginx/conf/nginx.conf
# pidfile: /usr/local/nginx/logs/nginx.pid

# Source function library.
. /etc/rc.d/init.d/functions

# Source networking configuration.
. /etc/sysconfig/network

# Check that networking is up.
[ "$NETWORKING" = "no" ] && exit 0

nginx=”/usr/local/nginx/sbin/nginx”
prog=$(basename $nginx)

NGINX_CONF_FILE=”/usr/local/nginx/conf/nginx.conf”

lockfile=/var/lock/subsys/nginx

start() {
[ -x $nginx ] || exit 5
[ -f $NGINX_CONF_FILE ] || exit 6
echo -n $”Starting $prog: ”
daemon $nginx -c $NGINX_CONF_FILE
retval=$?
echo
[ $retval -eq 0 ] && touch $lockfile
return $retval
}

stop() {
echo -n $”Stopping $prog: ”
killproc $prog -QUIT
retval=$?
echo
[ $retval -eq 0 ] && rm -f $lockfile
return $retval
}

restart() {
configtest || return $?
stop
start
}

reload() {
configtest || return $?
echo -n $”Reloading $prog: ”
killproc $nginx -HUP
RETVAL=$?
echo
}

force_reload() {
restart
}

configtest() {
$nginx -t -c $NGINX_CONF_FILE
}

rh_status() {
status $prog
}

rh_status_q() {
rh_status >/dev/null 2>&1
}

case “$1″ in
start)
rh_status_q && exit 0
$1
;;
stop)
rh_status_q || exit 0
$1
;;
restart|configtest)
$1
;;
reload)
rh_status_q || exit 7
$1
;;
force-reload)
force_reload
;;
status)
rh_status
;;
condrestart|try-restart)
rh_status_q || exit 0
;;
*)
echo $”Usage: $0 {start|stop|status|restart|condrestart|try-restart|reload|force-reload|configtest}”
exit 2
esac

As the init file is a shell script, it needs to have executable permissions.

chmod +x /etc/init.d/nginx

Now you can start, stop , reload Nginx through command below :

service nginx start
service nginx stop
service nginx restart
service nginx reload

Now we have the base script prepared, we need to add it to the default run levels:

/sbin/chkconfig nginx on

4. Once you’re done, try to run the website with port 81. Type in your regular URL but end with :81 Such as ..

http://www.domainname.com:81/test/information

5. If your website loaded as usual, then, it’s time to redirect all the traffic from port 80 to port 81. Just copy and paste the code below :

iptables -t nat -A PREROUTING -p tcp -s ! xxx.xxx.xxx.xxx --dport 80 -j REDIRECT --to-ports 81

Now, access your website normally, no need to add port 81.

But if your website doesn’t work as it should be. You may need to run command below to disable port forwarding so that you can check your configuration again.

iptables -t nat -D PREROUTING -p tcp -s ! xxx.xxx.xxx.xxx --dport 80 -j REDIRECT --to-ports 81

Actually, I also try to serve cache static file using code below :

location ~* ^.+.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf)$ {
root /home/admin/public_html;
expires 30m;
}

I don’t know if I really need that code to make Nginx works properly or not. Still, I tried both configurations. Now…. how about load?? performance??? Is it worth to do it? … Since I don’t have any program to test it. I just base on my feeling alone. I feel that with Nginx as a reverse proxy doesn’t really help much compare to Apache Worker MPM. The server load is quite the same. The only thing I found it’s better is memory consumption. (~ 18 M for NginX vs ~ 200 M for Apache)

Note :
1. About nginx.pid, I found that when restart service, sometime it work, sometime it doesn’t. So, check it carefully.
2. I also tested Reverse proxy cache and it seems to work pretty good. However, most of my websites are Drupal and with Reverse proxy cache, it doesn’t play well together. When I update content with image, I usually end up with Repeating loop. This will only happen once I do the port forwarding. But if I work on the site with port 81, it works correctly.

Tested with below software :
CentOS 5.4 / 5.5 – 64 bits
DirectAdmin 1.37 – With Custombuild 1.2
Apache 2.2.17 – Worker MPM
Nginx 0.8.5
PHP 5.2.17 / 5.3.5
PHP-FPM in PHP 5.3.5
APC 3.1.7

Source :
- http://www.directadmin.com/forum/showthread.php?t=27344
- http://articles.slicehost.com/2009/2/2/centos-adding-an-nginx-init-script

Updated : 2011.06.04
When compile Nginx to use as HTTP server and has a reverse proxy in front of the Nginx, you may need “http_realip_module”. (Comparable to mod_rpaf in Apache) So, compile with below command.

wget http://nginx.org/download/nginx-1.0.4.tar.gz
tar xvfz nginx-1.0.4.tar.gz
cd nginx-1.0.4
./configure --with-http_stub_status_module --with-http_gzip_static_module --with-http_realip_module
make
make install