The Perfect Server - CentOS 5.4 x86_64 [ISPConfig 3]

Version 1.1
Author: Falko Timme
Follow me on Twitter
Last edited 03/16/2010

This tutorial shows how to prepare a CentOS 5.4 x86_64 server for the installation of ISPConfig 3, and how to install ISPConfig 3. ISPConfig 3 is a webhosting control panel that allows you to configure the following services through a web browser: Apache web server, Postfix mail server, MySQL, MyDNS nameserver, PureFTPd, SpamAssassin, ClamAV, and many more.

Please note that this setup does not work for ISPConfig 2! It is valid for ISPConfig 3 only!

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

 

1 Requirements

To install such a system you will need the following:

 

2 Preliminary Note

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

 

3 Install The Base System

Boot from your first CentOS 5.4 CD (CD 1) or the CentOS 5.4 DVD. Press <ENTER> at the boot prompt:

It can take a long time to test the installation media so we skip this test here:

The welcome screen of the CentOS installer appears. Click on Next:

Choose your language next:

Select your keyboard layout:

I'm installing CentOS 5.4 on a fresh system, so I answer Yes to the question Would you like to initialize this drive, erasing ALL DATA?

Now we must select a partitioning scheme for our installation. For simplicity's sake I select Remove linux partitions on selected drives and create default layout. This will result in a small /boot and a large / partition as well as a swap partition. Of course, you're free to partition your hard drive however you like it. Then I hit Next:

Answer the following question (Are you sure you want to do this?) with Yes:

On to the network settings. The default setting here is to configure the network interfaces with DHCP, but we are installing a server, so static IP addresses are not a bad idea... Click on the Edit button at the top right.

In the window that pops up uncheck Use dynamic IP configuration (DHCP) and Enable IPv6 support and give your network card a static IP address (in this tutorial I'm using the IP address 192.168.0.100 for demonstration purposes) and a suitable netmask (e.g. 255.255.255.0; if you are not sure about the right values, http://www.subnetmask.info might help you):

Set the hostname manually, e.g. server1.example.com, and enter a gateway (e.g. 192.168.0.1) and up to two DNS servers (e.g. 213.191.92.86 and 145.253.2.75):

Choose your time zone:

Give root a password:

Share this page:

20 Comment(s)

Add comment

Comments

From: Anonymous at: 2009-12-17 17:10:17

If you are following this tutorial to the tee like you should, be advised a newer kernel update is available and will be upgraded and will affect the compiling of courier etc, you will not see a problem until after a subsequent reboot. I would either recommend disabling kernel updates before doing the yum update in step 7 Install Some Software or rebooting after the yum update in step 7 Install Some Software and then disabling kernel updates. Took me quite a while to figure out this problem as I am a newbie to Linux. I hope this helps out other people.

From: AJ at: 2010-02-09 14:21:37

After the group install of Development Tools, you should probably add the following perl install to be sure. I followed these instructions, but skipped adding SMTP/POP. Take a look at your httpd error log and you'll see problems. My httpd (apache) server would lock up intermittently.  Adding the statement below and rebooting fixed it:

 yum install perl-TimeDate

From: Marcelo Gondim at: 2010-03-31 22:33:48

Amavisd setup, we need to change this so the spamassassin to work properly by ispconfig 3: Change this: ### Uncomment this if you want to use amavis with sendmail milter interface. ### See README.milter for details. # #MILTER_SOCKET="local:/var/amavis/amavis-milter.sock" #MILTER_SOCKET="10024@127.0.0.1" ### These are other defaults. #AMAVIS_ACCOUNT="amavis" #CONFIG_FILE="/etc/amavisd.conf" #MILTER_FLAGS="" For: ### Uncomment this if you want to use amavis with sendmail milter interface. ### See README.milter for details. # #MILTER_SOCKET="local:/var/amavis/amavis-milter.sock" #MILTER_SOCKET="10024@127.0.0.1" ### These are other defaults. #AMAVIS_ACCOUNT="amavis" #CONFIG_FILE="/etc/amavisd.conf" CONFIG_FILE="/etc/amavisd/amavisd.conf" #MILTER_FLAGS="" The CONFIG_FILE is very important to work. Thanks for your howto, it helped me a lot with ISPConfig 3

From: iszabi at: 2010-03-15 14:40:11

Hi Falko Timme!

 Note to the 13th point:

under CentOs 5.4 screened :

"No package getmail available." when I wanted to install getmail:

 yum install getmail


From: Anonymous at: 2009-12-17 16:56:29

http://n0rp.chemlab.org/vlogger/vlogger-1.3.tar.gz check your input or your internet connection, works for me.

From: at: 2010-04-22 15:11:28

when I issue commands ./configure --prefix=/usr --sysconfdir=/etc --with-apr=/usr/bin/apr-1-config --with-apxs=/usr/sbin/apxs --with-apache-user=apache --with-setid-mode=owner --with-php=/usr/bin/php-cgi --with-logfile=/var/log/httpd/suphp_log --enable-SUPHP_USE_USERGROUP=yes make make install make[4]: Leaving directory `/tmp/suphp-0.7.1/src' make[3]: Nothing to be done for `install-data-am'. i don't see file suphp.conf file in /etc/httpd/conf.d/suphp.conf I have i386 system. I'm stuck at this step Please advise

From: SCM at: 2009-12-15 10:26:29

http://n0rp.chemlab.org/vlogger/vlogger-1.3.tar.gz is a dead link, can not find any other links. what a waste of 2 days worth of installing for ISPConfig :/

From: Anonymous at: 2010-02-02 23:29:20

This tutorial is seriously jacked up. I've spent over 8 hours, and half of this does not work. Find another route to take for ISPConfig!

From: JcOaCrO at: 2010-03-24 13:30:07

Great tutorial and all worked from first!!! For everyone having troubles just read carefully and check your typo :) Big THANKS to the auhor

From: Anonymous at: 2010-02-24 17:31:36

I've come across this tutorial a number of times because it looks like a great potential solution and finally took some time to walk through it on a test server.

Although the functionality looks great I'm rather concerned with the general lack of security and long term stability concern these instructions seem to have. True lots of people like to turn off SELINUX and GPG checks and you'll probably be fine, but more importantly the major reliance on disparate third party (and largely unaccountable) repositories and patches could make long term security and stability a serious issue.  To start, the instructions are already giving paths to out of date software packages, but what happens when a serious security update is released?  I could easily see running yum updates from official and third party repos, plus manual rpmbuilds could get things out of sync alone, but what happens when a patch or repo provider stops supplying updates?  Do you realize this before or after you've tried to apply updates?  And what services have you lost in the meantime without a clear path for resolution?

True a more experienced admin can pick and choose or modify aspects of the instructions to better suit their security and stability needs, but a lot of less experienced admins could be opening themselves up to the ticking time bomb of non-updatable system likely running production data for potentially paying customers.

As always with other people's "prefect build" instructions, be very cautious of what you are running and educate yourself on the finer details of how it all works.  Remember it's going to fall on you to fix things when they break, so make sure you have a good path to CYA. ;)

From: at: 2010-03-04 18:58:03

This line:

                mysqladmin -h server1.example.com -u root password yourrootsqlpassword

should probably look like this:

                mysqladmin -h server1.example.com -u root -p password yourrootsqlpassword

From: at: 2010-05-05 14:31:19

Please,

The link for download this "broken" http://mydns.bboy.net/download/mydns-mysql-1.1.0-1.i386.rpm.

Can where get the file mydns-mysql-1.1.0-1.i386.rpm
There is some other option?

From: ksc133 at: 2010-05-13 09:25:14

hi folks,

 is it possible to

Install Amavisd-new, SpamAssassin And ClamAV

on ISPconfig2 centos 5.4 x64?

 thanks a lot

From: wepabong at: 2009-11-21 06:32:38

amavis fails and show errors when i try to start, cheking the error, i founded i need install two additional packages:

so easy like this:

yum install perl-Mail-SPF.noarch  perl-Mail-SPF-Query.noarch

 great job :)

From: ZadY at: 2010-02-20 15:24:06

Great job!

From: volker at: 2010-04-06 17:01:09

hi,

 

thanks for this tut: Great work! what is the squirrelmails username and passwd? admin /admin too, like in the ispconfig app?

cheers volker

From: Bill48105 at: 2010-04-29 03:03:23

If mail sticks in deferred queue & amavisd won't stay running then be sure to run sa-update!

maillog shows something like:
status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)

I found this out by running:
/usr/sbin/amavisd foreground
Which told me:
Suicide () TROUBLE in pre_loop_hook: config: no rules were found!  Do you need to run 'sa-update'?

After running sa-update then restarting mail started getting delivered.

Took me forever to figure that out since the maillog made no mention of amavid or sa-update (spamassassin) so hope it helps someone avoid the frustration of a step this how-to missed.
Bill

From: Riverman at: 2012-05-13 20:54:11

Thanks for your info! This helped me...

But old messages has not been routed to mail yet...

 

From: latvian at: 2010-10-08 09:11:05

In page 37/69 there is the step of building the rpm for courier-imap. I am gettin gthe following problem while trying to run the rpmbuild:

 RPM build errors:

Bad exist status from /var/tmp/rpm.tmp.14636 (%prep)

 What is the soultion for this problem?

Thanks in advance

From: at: 2011-03-07 01:36:01

very great tutorial!

 Easy to follow and rather simple to update and configure for i386.

Forum replies have been fast and accurate!

 Thank you for your time and support