The Setup

Install some base packages

# yum install rpm-build gcc-java

Add jpackage repository to your yum repos

# cd /etc/yum.repos.d/
# wget https://jpackage.org/jpackage.repo
# vi /etc/yum.repos.d/jpackage.repo

set enabled = 1 on all repo files and save the .repo file. Next update yum.

# yum update

Download and install some SRPMs.

# cd /usr/local/src
# wget ftp://jpackage.hmdc.harvard.edu/mirrors/JPackage/1.7/generic/non-free/SRPMS/java-1.5.0-sun-1.5.0.11-1jpp.nosrc.rpm
# wget ftp://jpackage.hmdc.harvard.edu/mirrors/JPackage/1.6/generic/non-free/SRPMS/jta-1.0.1-0.b.4jpp.nosrc.rpm

Download some required files to /usr/src/redhat/SOURCES:

# cd /usr/src/redhat/SOURCES

Download jta-1_0_1B-classes.zip here after agreeing to the license.
Download jdk-1_5_0_11-linux-i586.bin, again after agreeing to a license.
Build and install the rpms.

# rpmbuild --rebuild /usr/local/src/java-1.5.0-sun-1.5.0.11-1jpp.nosrc.rpm
# rpm -ivh /usr/src/redhat/RPMS/i586/java-1.5.0-sun-1.5.0-11-1jpp.i586.rpm
# rpm -ivh /usr/src/redhat/RPMS/i586/java-1.5.0-sun-devel-1.5.0.11-1jpp.i586.rpm
# rpmbuild --rebuild --without javadoc /usr/local/src/jta-1.0.1-0.b.4jpp.nosrc.rpm
# rpm -ivh /usr/src/redhat/RPMS/noarch/jta-1.0.1-0.b.4jpp.noarch.rpm

Now install tomcat

# yum install tomcat5 tomcat5-webapps tomcat5-admin-webapps

note: if you get a dependency error at this point, like I did at first, try this solution for updating your jpackage-utils http://blog.sixsigns.com/2008/07/11/java-142-gcj-compati386-update-problem-on-centos/ which basically is to install the http://dev.centos.org/centos/5/testing/i386/RPMS/jpackage-utils-1.7.5-1jpp.1.el5.centos.noarch.rpm package and update yum

At this point you should be able to navigate to your ip on port 8080 and see the default tomcat page

With that said, I would be remiss if I didn’t also mention that fact that, while I have some issue with plesk and its somewhat cookie cutter approach to web administration, it still is a great web administration tool for the most part.

My goal is basically to get a bare server up and running and administer-able without using Plesk or CPanel. The more I play around with this setup the more I will update the server section of this site with new configurations and additions as I learn them.

Setting up a fresh CentOS server

1. Get a dedicated server from someone, I used aplus.net
2. Choose a basic installation, this means no plesk, cpanel etc… (keep in mind, eventually we will setup Webmin)
3. Start setting up your new box

The setup
shell into you server

# ssh root@111.111.11.111

Install LAMP (Linux Apache MySQL PHP) installed.
You will do this using yum. Yum is an rpm wrapper that will allow you to install various services and applications with a lot more ease.

# yum -y install httpd
# yum -y install php
# yum -y install mysql
# yum -y install mysql-server
# yum -y install php-mysql

note: the -y switch forces “yes” when prompted, so you don’t have to

Next configure the services you just installed to start automatically when the server restarts

# /sbin/chkconfig httpd on
# /sbin/chkconfig --add mysqld
# /sbin/chkconfig mysqld on
# /sbin/service httpd start
# /sbin/service mysqld start

At this point, you now have mysql installed, but you will want to set up the mysql database root password. Without a password, any user on the box can login to mysql as database root. The mysql root account is a separate password from the machine root account.

# mysqladmin -u root password 'new-password'

At this point, some of you may be able to navigate to your public ip address and see the default CentOS page, I was not able to see this. Basically at this point, what I had was LAMP installed on my shiny new server but no one would ever know because port 80 was blocked.

Enter iptables...
Iptables is your firewall, its baked into CentOS, and its extremely powerful. I don’t know the complete depth of iptables but for this tutorial you’ll need to just get a few ports opened up and that’s it.

# iptables -F
# iptables -A INPUT -p udp -m udp --dport domain -j ACCEPT
# iptables -A INPUT -p tcp --dport 22 -j ACCEPT
# iptables -A INPUT -p tcp --dport 10000 -j ACCEPT
# iptables -A INPUT -p tcp --dport 25 -j ACCEPT
# iptables -A INPUT -p tcp --dport 8080 -j ACCEPT
# iptables -A INPUT -p tcp --dport 80 -j ACCEPT
# iptables -A INPUT -p tcp -m tcp --dport domain -j ACCEPT
# iptables -A FORWARD -o eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_OUT:
# iptables -A FORWARD -i eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_IN:
# iptables -A OUTPUT -o eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_OUT:
# iptables -A INPUT -i eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_IN:

make sure you save your iptables configuration so you don’t have to re-edit it when you reboot your server

# /sbin/service iptables save

now just restart your firewall

# /etc/init.d/iptables restart

now you can check your configuration

# iptables -L -v

at this point, for good measure you might want to reboot your server

# reboot

once your server reboots you should now be able to browse to your public IP address and get the default CentOS page.

you can learn more about iptables here: http://wiki.centos.org/HowTos/Network/IPTables

 # cd /opt/cruisecontrol-bin-2.6
 
# ./cruisecontrol.sh

Top stop (aka Kill) CruiseControl use the UNIX command ‘ps’ to view the processes and corresponding process IDs as shown on this post on the source forge forums.

Find which PID (Process ID) you want to stop/kill type

 # ps -e

I dont know what the -e switch is for but from what I can tell it displays all the running processes in the system as opposed to just #ps which displays a limited list. If you want a more verbose list the type in

 #ps -e -f

(again I don’t know what the -f) switch is for, but it will return back to you even more information about the ongoing processes in your system. From here you can stop/kill the process you want based off the the displayed PID.

 # kill -9 'XXXX'

where ‘XXXX’ is the associated PID for the CruiseControl process you want to kill