Installing Nginx With PHP5 And MySQL Support On Ubuntu 8.10

Version 1.0
Author: Falko Timme <ft [at] falkotimme [dot] com>
Last edited 12/09/2008

Nginx (pronounced "engine x") is a free, open-source, high-performance HTTP server. Nginx is known for its stability, rich feature set, simple configuration, and low resource consumption. This tutorial shows how you can install Nginx on an Ubuntu 8.10 server with PHP5 support (through FastCGI) and MySQL support.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100. These settings might differ for you, so you have to replace them where appropriate.

2 Installing MySQL 5.0

In order to install MySQL, we run

apt-get install mysql-server mysql-client

You will be asked to provide a password for the MySQL root user - this password is valid for the user root@localhost as well as root@server1.example.com, so we don't have to specify a MySQL root password manually later on:

New password for the MySQL "root" user: <-- yourrootsqlpassword
Repeat password for the MySQL "root" user: <-- yourrootsqlpassword

3 Installing Nginx

Nginx is available as a package for Ubuntu 8.10 which we can install as follows:

apt-get install nginx

Start nginx afterwards:

/etc/init.d/nginx start

Type in your web server's IP address or hostname into a browser (e.g. http://192.168.0.100), and you should see the nginx welcome page:

To make nginx start at boot time, run

update-rc.d nginx defaults

4 Installing PHP5

We can make PHP5 work in nginx through FastCGI. Fortunately, Ubuntu provides a FastCGI-enabled PHP5 package which we install like this (together with some PHP5 modules like php5-mysql which you need if you want to use MySQL from your PHP scripts):

apt-get install php5-cgi php5-mysql php5-curl php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-mhash php5-ming php5-pspell php5-recode php5-snmp php5-sqlite php5-tidy php5-xmlrpc php5-xsl

Then open /etc/php5/cgi/php.ini and add the line cgi.fix_pathinfo = 1 right at the end of the file:

vi /etc/php5/cgi/php.ini

[...]
cgi.fix_pathinfo = 1

There's no standalone FastCGI daemon package for Ubuntu, therefore we use the spawn-fcgi program from lighttpd. We install lighttpd as follows:

apt-get install lighttpd

You will see an error message saying that lighttpd couldn't start because port 80 is already in use. That's how it's supposed to be because nginx is already listening on port 80. Run

update-rc.d -f lighttpd remove

so that lighttpd will not start at boot time.

We've installed lighttpd because we need just one program that comes with the package, /usr/bin/spawn-fcgi, which we can use to start FastCGI processes. Take a look at

spawn-fcgi --help

to learn more about it.

To start a PHP FastCGI daemon listening on port 9000 on localhost and running as the user and group www-data, we run the following command:

/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f /usr/bin/php5-cgi -P /var/run/fastcgi-php.pid

Of course, you don't want to type in that command manually whenever you boot the system, so to have the system execute the command automatically at boot time, open /etc/rc.local...

vi /etc/rc.local

... and add the command at the end of the file (before the exit line):

[...]
/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f /usr/bin/php5-cgi -P /var/run/fastcgi-php.pid
[...]

5 Configuring nginx

The nginx configuration is in /etc/nginx/nginx.conf which we open now:

vi /etc/nginx/nginx.conf

The configuration is easy to understand (you can learn more about it here: http://wiki.codemongers.com/NginxFullExample and here: http://wiki.codemongers.com/NginxFullExample2)

First (this is optional) increase the number of worker processes and set the keepalive_timeout to a reasonable value:

[...]
worker_processes  5;
[...]
    keepalive_timeout  2;
[...]

The virtual hosts are defined in server {} containers. The default vhost is defined in the file /etc/nginx/sites-available/default - let's modify it as follows:

vi /etc/nginx/sites-available/default

[...]
server {
        listen   80;
        server_name  _;

        access_log  /var/log/nginx/localhost.access.log;

        location / {
                root   /var/www/nginx-default;
                index  index.php index.html index.htm;
        }

        location /doc {
                root   /usr/share;
                autoindex on;
                allow 127.0.0.1;
                deny all;
        }

        location /images {
                root   /usr/share;
                autoindex on;
        }

        #error_page  404  /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
                root   /var/www/nginx-default;
        }

        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
                #proxy_pass   http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        location ~ \.php$ {
                fastcgi_pass   127.0.0.1:9000;
                fastcgi_index  index.php;
                fastcgi_param  SCRIPT_FILENAME  /var/www/nginx-default$fastcgi_script_name;
                include        fastcgi_params;
        }

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        location ~ /\.ht {
                deny  all;
        }
}
[...]

server_name _; makes this a default catchall vhost (of course, you can as well specify a hostname here like www.example.com).

In the location / part, I've added index.php to the index line. root /var/www/nginx-default; means that the document root is the directory /var/www/nginx-default.

The important part for PHP is the location ~ \.php$ {} stanza. Uncomment it to enable it. Please make sure that you change the fastcgi_param line to fastcgi_param SCRIPT_FILENAME /var/www/nginx-default$fastcgi_script_name; (replace /var/www/nginx-default with your vhost's document root) because otherwise the PHP interpreter won't find the PHP script that you call in your browser.

Make sure that there are some spaces between include and fastcgi_params; - in the default file this is written as one word which is a bug.

Now save the file and restart nginx:

/etc/init.d/nginx restart

Now create the following PHP file in the document root /var/www/nginx-default:

vi /var/www/nginx-default/info.php

<?php
phpinfo();
?>

Now we call that file in a browser (e.g. http://192.168.0.100/info.php):

As you see, PHP5 is working, and it's working through FastCGI, as shown in the Server API line. If you scroll further down, you will see all modules that are already enabled in PHP5, including the MySQL module:

6 Links

• nginx: http://nginx.net/
• nginx Wiki: http://wiki.codemongers.com/Main
• PHP: http://www.php.net
• MySQL: http://www.mysql.com
• Ubuntu: http://www.ubuntu.com/

How To Upgrade Debian Etch To Lenny

Debian Etch is soon to be unsupported by the Debian team, therefore all Debian Linux Servers need to be upgraded to Debian Lenny. I work for Netzen (an IT Support company) and have upgraded many Linux servers to Debian Lenny over the past month, so I am providing this guide on how to upgrade Debian Etch to Debian Lenny to the HowtoForge community.

Backup

Backup! I took a full backup of the server which is stored off the server I am backing up of course! I also take an additional backup of  /etc which I store locally in /root this is just in case I make a mistake during the the upgrade process and over write a config file, or dpkg / aptitude makes a misstake some how and botches my configs. Worth pointing out that none of these two things have never happened, but “only the paranoid surviveâ€�.

 SSH / Screen

When I upgrade my servers remotely over SSH I always run the upgrade in screen, that way if you lose connection to your server you will still be able to reconnect to the screen session. 

To run screen type: 

screen

To reconnect to a screen session: 

screen -rd

Or if you don't have screen installed: 

aptitude install screen

Upgrade your existing Etch install

Before upgrading to Lenny, make sure your box is fully up to date using your existing apt sources for Etch, to do this:

aptitude update && aptitude dist-upgrade

If the updates you have applied include a kernel upgrade I would advise rebooting the server at this stage.

Check disk space for install

Make sure you have enough space for the upgrade.

Edit apt sources for Lenny

Edit your /etc/apt/sources.list file to use lenny instead of etch repositories, this is normally a case of replacing the word etch with lenny, however take a moment to make sure you don’t have any other entries in your sources.list file. If you have any backports or 3rd party repositories I would comment them out during the upgrade. FYI here are the mirrors I used during upgrades:

deb http://ftp.uk.debian.org/debian/ lenny main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ lenny main contrib non-free
deb http://security.debian.org/ lenny/updates main contrib non-free
deb-src http://security.debian.org/ lenny/updates main contrib non-free

Upgrade Apt & Aptitude

The first things to upgrade are apt & aptitude, this will pull a few dependencies and will automatically upgrade libc6 and locales and will pull in SELinux support libraries (libselinux1). Some services may need restarting (you will get asked to restart various services several times during the upgrade process).

aptitude update && aptitude install apt && aptitude install aptitude

The first time the lenny version of aptitude is run, it will read in its list of automatically installed packages and convert it for use with the lenny version of apt. If you have aptitude installed, you should at least issue one aptitude command to do the conversion. So go ahead and enter:

aptitude search "?false"

Minimal System Upgrade

Ok now we have aptitude updated it’s time to do what Debian call a “minimal system upgradeâ€� which basically upgrades all packages that do  require other packages to be removed or installed. To do this enter:

aptitude safe-upgrade

Quick note from Debian “The next step will vary depending on the set of packages that you have installed. These release notes give general advice about which method should be used, but if in doubt, it is recommended that you examine the package removals proposed by each method before proceeding.� However in my case it was fine and I proceeded, however you might want to check with the Debian Obsolete Packages.

This step is probably going to take a while and is going to pull down a lot of packages from the mirrors, but you will need to remain at the terminal as your going to have to tell aptitude what to do with various config files as your system upgrade progresses, the default is to use your existing configs. Which is what I did for the majority of my configs however if you want to make use of new features you will more than likely have to use the new configs or edit your existing configs to make use of the feature.

Upgrade the rest of the System

Ok, when that’s finished it is  now time to upgrade the rest of the system! Please enter:

aptitude dist-upgrade

Again, your going to need to hang around and tell aptitude what to do with your config files.

Upgrade the Kernel

Ok when that’s done you are almost finished, we need to check that aptitude upgraded your kernel during the update, in my case it didn’t. Enter the following to check:

dpkg -l "linux-image*" | grep ^ii

If you don’t see any output then you will have to install a new kernel image by hand, as I had to. Your best option is to find out what kernel you are currently running using:

uname -r

cartman:~# uname -r
2.6.26-2-686

Then do  a search using aptitude for a similar kernel using:

apt-cache search linux-image-2.6- | grep -v transition

cartman:~# apt-cache search linux-image-2.6- | grep -v transition
linux-image-2.6-486 - Linux 2.6 image on x86
linux-image-2.6-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6-686-bigmem - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6-amd64 - Linux 2.6 image on AMD64
linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4, OpenVZ support
linux-image-2.6-vserver-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4, Linux-VServer support
linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on PPro/Celeron/PII/PIII/P4, Linux-VServer support
linux-image-2.6-xen-686 - Linux 2.6 image on i686, oldstyle Xen support

So in this case I would install linux-image-2.6-686 using:

aptitude linux-image-2.6-686

I then rebooted my server and it booted fine, however I had remote access via KVMoIP standing by just in case there was a problem during boot. In the Official Debian notes they recommend re running “/sbin/lilo� and reviewing the contents of your /etc/kernel-img.conf to make sure that you have do_bootloader = Yes. That way the bootloader will always be rerun after a kernel upgrade.

Let me know how you get on, feel free to link back to this page and post in the comments if you experience problems during your upgrade and I will do my best to get back to you in a timely manor, however please remember I do already have a day job Of course you could always hire Netzen to upgrade your Debian Linux servers for your company.

Disclaimer

I take care to make sure the information I post on my blog is accurate, however there could be mistakes, if your break your server following guides found on this website, it is your fault this guide and others found here come with no guarantee. Please use at your own risk.