How 2 #CentOS

Installing #Cherokee on #CentOS 5.5

How2CentOS — Mon, 06 Sep 2010 09:25:29 +0000

Cherokee is a very fast, flexible and easy to configure Web Server. It supports the widespread technologies nowadays: FastCGI, SCGI, PHP, CGI, TLS and SSL encrypted connections, virtual hosts, authentication, on the fly encoding, load balancing, Apache compatible log files, and much more. This tutorial shows how you can install Cherokee on a CentOS 5.5 server

Preliminary Note

In this updated tutorial we will use a base 32 bit CentOS 5.5 server install with the hostname centos01.how2centos.com with the IP address 10.0.0.3. These settings might differ for you, so you have to replace them where appropriate.

Let’s begin

# yum install yum-priorities
# rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# yum update

First we install MySQL and MySQL server:

# yum install mysql mysql-server

Followed by RRDTool

# yum install rrdtool

Then finally we’ll install the Cherokee and add it to startup:

# yum install cherokee
# chkconfig cherokee on
# service cherokee start

Now direct your browser to http://10.0.0.3

You should see the Cherokee placeholder page.

Cherokee can be configured through a web-based control panel which we can start as follows:

cherokee-admin -b

(By default cherokee-admin binds only to 127.0.0.1 (localhost), with the -b parameter you can specify the network address to listen to. If no IP is provided, it will bind to all interfaces.)

Output should be similar to this one:

# cherokee-admin -b

Login:
User: admin
One-time Password: gtVzmvy6Rqy9idKy

Web Interface:
URL: http://localhost:9090/

Cherokee Web Server 1.0.6 (Aug 6 2010): Listening on port ALL:9090, TLS
disabled, IPv6 enabled, using epoll, 4096 fds system limit, max. 2041
connections, caching I/O, single thread

The admin web interface can be found on http://10.0.0.3:9090/ (make sure to enter your one-time password)

To stop cherokee-admin, type CTRL+C on the shell.

Links

Cherokee: http://www.cherokee-project.com/
MySQL: http://www.mysql.com/
CentOS: http://centos.org/

#CentOS: Change that hostname

How2CentOS — Thu, 02 Sep 2010 09:16:35 +0000

In this CentOS 5.5 tutorial we will be showing you how to change the hostname. The assumption is that you are running as root and have a basic understanding of the software required but if you follow this tutorial you should be able to complete the task successfully.

To find the machine’s fully qualifier domain name (FQDN) see for yourself how the machine identifies itself:

# uname -n
centos01.how2centos.com
# dnsdomainname
how2centos.com

There are a couple of ways to change the hostname. Edit the /etc/sysconfig/network and change the hostname

# vi /etc/sysconfig/network

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=centos01.how2centos.com

or run System Config

# system-config-network

Select Edit DNS configuration

ââââââââ¤ Select Action âââââââ
â                             â
â  Edit a device params       â
â  Edit DNS configuration     â
â                             â
â                             â
â                             â
â  âââââââââââââ  ââââââââ    â
â  â Save&Quit â  â Quit â    â
â  âââââââââââââ  ââââââââ    â
â                             â
â                             â
âââââââââââââââââââââââââââââââ

âââââââ¤ DNS configuration âââââââ
â                                â
â                                â
â  Hostname      centos01.how2ce â
â  Primary DSN   10.0.0.10______ â
â  Secondary DNS _______________ â
â  Tertiary DNS  _______________ â
â  Search        how2centos.com_ â
â                                â
â     ââââââ  ââââââââââ         â
â     â Ok â  â Cancel â         â
â     ââââââ  ââââââââââ         â
â                                â
â                                â
ââââââââââââââââââââââââââââââââââ

Edit the hostname and select OK and then Save&Quit

TIP: If you would like to strip off the domain name portion, which is stored elsewhere anyway.

# sed -i.bak 's/\.[a-z].*//g' /etc/sysconfig/network

# cat /etc/sysconfig/network

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=centos01

# uname -n
centos01
# dnsdomainname
how2centos.com

Dont forget to change the hostname in your hosts file

# vi /etc/hosts

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       centos01.how2centos.com centos01 localhost.localdomain localhost
::1             localhost6.localdomain6 localhost6

However we’re not finished. The machine wont normally see the updated hostname until about it reboots, but we can force it to update.

# source /etc/sysconfig/network
# hostname $HOSTNAME

Installing #Puppet Master with #Foreman frontend on #CentOS 5.5

How2CentOS — Fri, 27 Aug 2010 13:24:39 +0000

In this CentOS 5.5 tutorial we will be installing Foreman on a CentOS 5.5 i386 server including Puppet Master and Puppet client. The assumption is that you have a basic to medium understanding of the software required but if you follow this tutorial you should be able to complete the task successfully.

A bit on the software that we’ll be using:

Foreman
Foreman is aimed to be a Single Address For All Machines Life Cycle Management.

Foreman integrates with Puppet (and acts as web front end to it).

Foreman takes care of bare bone provisioning until the point puppet is running, allowing Puppet to do what it does best.

Foreman shows you Systems Inventory (based on Facter) and provides real time information about hosts status based on Puppet reports.

Foreman creates everything you need when adding a new machine to your network. It’s goal being automatically managing everything you would normally manage manually – that would eventually include DNS, DHCP, TFTP, PuppetCA, CMDB and everything else you might consider useful.

With Foreman You Can Always Rebuild Your Machines From Scratch!

Foreman is designed to work in a large enterprise, where multiple domains, subnets and puppetmasters are required.

http://theforeman.org/

Preliminary Note:
I am using a CentOS 5.5 i386 base installation in this tutorial with root access.

* foreman.how2centos.com (IP 10.0.0.100): CentOS 5.5 i386 base installation

Lets begin by adding additional CentOS 5.5. repositories and installing the framework required by Foreman.

# yum install yum-priorities
# rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

# cat > /etc/yum.repos.d/foreman.repo << EOF
[foreman]
name=Foreman Repo
baseurl=http://theforeman.org/repo
gpgcheck=0
enabled=1
EOF

Lets begin installing the framework starting with Puppet Master, client and MySQL

# yum install puppet-server puppet
# yum install mysql mysql-server mysql-devel ruby-mysql rubygem-activerecord

Let do a basic Puppet Master and client configuration.

# vi /etc/puppet/puppet.conf

[main]
    # The Puppet log directory.
    # The default value is '$vardir/log'.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is '$vardir/run'.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is '$confdir/ssl'.
    ssldir = $vardir/ssl

[puppetd]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion.  Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is '$confdir/classes.txt'.
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration.  An
    # extension indicating the cache format is added automatically.
    # The default value is '$confdir/localconfig'.
    localconfig = $vardir/localconfig

	# Enable reporting for Foreman
	report = true

[puppetmasterd]
    storeconfigs = true
    dbadapter = mysql
    dbuser = puppet
    dbpassword = puppet
    dbserver = localhost
    dbsocket = /var/lib/mysql/mysql.sock
    rrddir=/var/lib/puppet/rrd
    rrdinterval=$runinterval
    rrdgraph=true
    reports=log, foreman

# vi /etc/sysconfig/puppet

# The puppetmaster server
PUPPET_SERVER=foreman.how2centos.com

# If you wish to specify the port to connect to do so here
#PUPPET_PORT=8140

# Where to log to. Specify syslog to send log messages to the system log.
PUPPET_LOG=/var/log/puppet/puppet.log

# You may specify other parameters to the puppet client here
#PUPPET_EXTRA_OPTS=--waitforcert=500

# mkdir /etc/puppet/manifests/classes/
# vi /etc/puppet/manifests/site.pp

import "classes/*"

node default {
    include sudo
 }

# vi /etc/puppet/manifests/classes/sudo.pp

class sudo {
    file { "/etc/sudoers":
        owner => "root",
        group => "root",
        mode  => 440,
    }
}

Start MySQL and add it to startup

# service mysqld start
# chkconfig mysqld on

Add the Puppet Database

# mysql
mysql> create database puppet;
mysql> grant all privileges on puppet.* to puppet@localhost identified by ‘puppet’;
mysql> exit
Bye

Install Foreman and configure the Database and enable reporting.

# yum install foreman

Foreman uses a database, by default, SQLite is used, if you want to use other database (e.g. MySQL) please modify the configuration file under config/database.yml.

# mv /etc/foreman/database.yml /etc/foreman/database.yml.old
# vi /etc/foreman/database.yml

production:
  adapter: mysql
  database: puppet
  username: puppet
  password: puppet
  host: localhost
  socket: "/var/lib/mysql/mysql.sock"

To enable reporting in Foreman you’ll be required to copy foreman-report.rb to your report directory, edit the $foreman_url=, and then add it to your master puppet.conf under the main section add:

# cp /usr/share/foreman/extras/puppet/foreman/files/foreman-report.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb
# vi /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb

# copy this file to your report dir - e.g. /usr/lib/ruby/1.8/puppet/reports/
# add this report in your puppetmaster reports - e.g, in your puppet.conf add:
# reports=log, foreman # (or any other reports you want)

# URL of your Foreman installation
$foreman_url="http://foreman.how2centos.com:3000"

require 'puppet'
require 'net/http'
require 'uri'

Puppet::Reports.register_report(:foreman) do
    Puppet.settings.use(:reporting)
    desc "Sends reports directly to Foreman"

    def process
      begin
        uri = URI.parse($foreman_url)
        http = Net::HTTP.new(uri.host, uri.port)
        if uri.scheme == 'https' then
          http.use_ssl = true
          http.verify_mode = OpenSSL::SSL::VERIFY_NONE
        end
        req = Net::HTTP::Post.new("/reports/create?format=yml")
        req.set_form_data({'report' => to_yaml})
        response = http.request(req)
      rescue Exception => e
        raise Puppet::Error, "Could not send report to Foreman at #{$foreman_url}/reports/create?format=yml: #{e}"
      end
    end
end

Finally to initialize the database schema type:

# cd /usr/share/foreman/
# RAILS_ENV=production rake db:migrate

Let start, and add to startup, the various componants and browse to your newly installed Puppet Master and client with Foreman frontend.

# service puppetmaster start
# service puppet start
# service foreman start
# chkconfig puppetmaster on
# chkconfig puppet on
# chkconfig foreman on

Point your bowser to http://foreman.how2centos.com:3000

#Dell and #CentOS the Perfect Combination

How2CentOS — Tue, 10 Aug 2010 19:01:51 +0000

A quick post to share this mostly unknown gem that Dell manages it’s own Open Manage Linux Repository.

To get your CentOS server installed with Server Administrator set up the Dell Open Manage Repository like so:

# wget -q -O – http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

Then install the Server Administrator

# yum install srvadmin-all

Finally browse to your newly installed Open Manage Server Administrator and monitor your Dell hardware.

https://your.Centos.Server:1311/

Log on screen – Use your root username and password

Main Screen after log on

TIP: After installing the Dell Server Administrator get your service tag number from your CentOS Linux server by running

# dmidecode -s system-serial-number
ABCDEF1

No related posts.

Installing #Smokeping on #CentOS 5.5

How2CentOS — Fri, 06 Aug 2010 13:46:33 +0000

In this CentOS 5.5 tutorial we will be installing Smokeping and SmokeTrace on a CentOS 5.5 i386 server. The assumption is that you have a basic to medium understanding of Apache but if you follow this tutorial you should be able to complete the task successfully.

A bit on the software that we’ll be using:

Smokeping
SmokePing keeps track of your network latency:

* Best of breed latency visualisation.
* Interactive graph explorer.
* Wide range of latency measurment plugins.
* Master/Slave System for distributed measurement.
* Highly configurable alerting system.
* Live Latency Charts with the most ‘interesting’ graphs.
* Free and OpenSource Software written in Perl written by Tobi Oetiker, the creator of MRTG and RRDtool

http://oss.oetiker.ch/smokeping/

Preliminary Note:
I am using a CentOS 5.5 i386 base installation in this tutorial.

* www.how2centos.com (IP 10.0.0.100): CentOS 5.5 i386 base installation

Lets begin by installing the framework required by Smokeping.

# yum update
# rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
# yum install httpd
# yum install rrdtool
# yum install fping
# yum install echoping
# yum install curl
# yum install perl perl-Net-Telnet perl-Net-DNS perl-LDAP perl-libwww-perl perl-RadiusPerl perl-IO-Socket-SSL perl-Socket6 perl-CGI-SpeedyCGI

# wget http://oss.oetiker.ch/smokeping/pub/smokeping-2.4.1.tar.gz
# tar zxvf smokeping-2.4.1.tar.gz
# mv smokeping-2.4.1 /opt/smokeping
# cd /opt/smokeping

# cd bin/
# cp smokeping.dist smokeping
# cd ../htdocs/
# cp smokeping.cgi.dist smokeping.cgi
# cp tr.cgi.dist tr.cgi
# cd ../etc/
# cp config.dist config
# cp basepage.html.dist basepage.html
# cp smokemail.dist smokemail
# cp tmail.dist tmail
# cp smokeping_secrets.dist smokeping_secrets
# chmod 600 /opt/smokeping/etc/smokeping_secrets

# vi /opt/smokeping/bin/smokeping

Replace this:

#!/usr/sepp/bin/perl-5.8.4 -w
# -*-perl-*-

use lib qw(/usr/pack/rrdtool-1.2.23-mo/lib/perl);
use lib qw(lib);

use Smokeping 2.004000;

Smokeping::main("etc/config.dist");

With This:

#!/usr/bin/perl -w
# -*-perl-*-

use lib qw(/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/RRDs/);
use lib qw(/opt/smokeping/lib);

use Smokeping 2.004000;

Smokeping::main("/opt/smokeping/etc/config");

or you can Patch the file:

# cd /opt/smokeping/bin
# vi /opt/smokeping/bin/smokeping.patch

*** /opt/smokeping/bin/smokeping.dist   2008-06-10 15:08:07.000000000 +0200
--- /opt/smokeping/bin/smokeping        2010-08-04 16:43:08.000000000 +0200
***************
*** 1,12 ****
! #!/usr/sepp/bin/perl-5.8.4 -w
  # -*-perl-*-

! use lib qw(/usr/pack/rrdtool-1.2.23-mo/lib/perl);
! use lib qw(lib);

  use Smokeping 2.004000;
!
! Smokeping::main("etc/config.dist");

  =head1 NAME

--- 1,12 ----
! #!/usr/bin/perl -w
  # -*-perl-*-

! use lib qw(/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/RRDs/);
! use lib qw(/opt/smokeping/lib);

  use Smokeping 2.004000;
!
! Smokeping::main("/opt/smokeping/etc/config");

  =head1 NAME

# patch -p1 -i smokeping.patch /opt/smokeping/bin/smokeping
patching file /opt/smokeping/bin/smokeping

# vi /opt/smokeping/htdocs/smokeping.cgi

Replace this:

#!/usr/sepp/bin/speedy -w
# -*-perl-*-

use lib qw(/usr/pack/rrdtool-1.0.33-to/lib/perl);
use lib qw(/home/oetiker/data/projects/AADJ-smokeping/dist/lib);
use CGI::Carp qw(fatalsToBrowser);

use Smokeping 2.004000;

Smokeping::cgi("/home/oetiker/data/projects/AADJ-smokeping/dist/etc/config");

With this:

#!/usr/bin/speedy -w
# -*-perl-*-

use lib qw(/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/RRDs);
use lib qw(/opt/smokeping/lib);
use CGI::Carp qw(fatalsToBrowser);

use Smokeping 2.004000;

Smokeping::cgi("/opt/smokeping/etc/config");

or you can Patch the file:

# cd /opt/smokeping/htdocs/
# vi /opt/smokeping/htdocs/smokeping_cgi.patch

***************
*** 1,13 ****
! #!/usr/sepp/bin/speedy -w
  # -*-perl-*-

! use lib qw(/usr/pack/rrdtool-1.0.33-to/lib/perl);
! use lib qw(/home/oetiker/data/projects/AADJ-smokeping/dist/lib);
  use CGI::Carp qw(fatalsToBrowser);

  use Smokeping 2.004000;

! Smokeping::cgi("/home/oetiker/data/projects/AADJ-smokeping/dist/etc/config");

  =head1 NAME

--- 1,13 ----
! #!/usr/bin/speedy -w
  # -*-perl-*-

! use lib qw(/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/RRDs);
! use lib qw(/opt/smokeping/lib);
  use CGI::Carp qw(fatalsToBrowser);

  use Smokeping 2.004000;

! Smokeping::cgi("/opt/smokeping/etc/config");

  =head1 NAME

# patch -p1 -i smokeping_cgi.patch /opt/smokeping/htdocs/smokeping.cgi
patching file /opt/smokeping/htdocs/smokeping.cgi

# cd /opt/smokeping/htdocs
# vi /opt/smokeping/htdocs/tr.cgi

Change this:

#!/usr/sepp/bin/speedy-5.8.8 -w
use strict;
use lib qw(/home/oposs/smokeping/software/lib);
use lib qw(perl);

To this:

#!/usr/bin/speedy -w
use strict;
use lib qw(/opt/smokeping/lib);
use lib qw(perl);

or you can Patch the file:

# vi /opt/smokeping/htdocs/tr_cgi.patch

*** /opt/smokeping/htdocs/tr.cgi.dist   2008-06-14 00:02:34.000000000 +0200
--- /opt/smokeping/htdocs/tr.cgi        2010-08-06 15:01:31.000000000 +0200
***************
*** 1,6 ****
! #!/usr/sepp/bin/speedy-5.8.8 -w
  use strict;
! use lib qw(/home/oposs/smokeping/software/lib);
  use lib qw(perl);

  use CGI;
--- 1,6 ----
! #!/usr/bin/speedy -w
  use strict;
! use lib qw(/opt/smokeping/lib);
  use lib qw(perl);

  use CGI;

# patch -p1 -i tr_cgi.patch /opt/smokeping/htdocs/tr.cgi
patching file /opt/smokeping/htdocs/tr.cgi

# mkdir -p /var/www/html/smokeping/img /var/www/html/smokeping/script/ /opt/smokeping/data /opt/smokeping/var
# chown -R apache:apache /var/www/html/smokeping/img

# ln -s /opt/smokeping/htdocs/cropper /var/www/html/smokeping/cropper
# ln -s /opt/smokeping/htdocs/resource /var/www/html/smokeping/resource
# ln -s /opt/smokeping/htdocs/script/Tr.js /var/www/html/smokeping/script/Tr.js
# ln -s /opt/smokeping/htdocs/smokeping.cgi /var/www/html/smokeping/smokeping.cgi
# ln -s /opt/smokeping/htdocs/tr.cgi /var/www/html/smokeping/tr.cgi

# chmod 4775 /bin/traceroute

vi /etc/httpd/conf/httpd.conf

change > #AddHandler cgi-script .cgi
to > AddHandler cgi-script .cgi

Under

change > Options Indexes FollowSymLinks
to > Options Indexes FollowSymLinks ExecCGI

# vi /opt/smokeping/etc/basepage.html

Change this:

To this:

or you can Patch the file:

# cd /opt/smokeping/etc/
# vi /opt/smokeping/etc/basepage.patch

56,59c56,59
< 
< 
< 
< 
---
> 
> 
> 
>

# patch -p1 -i basepage.patch /opt/smokeping/etc/basepage.html
patching file /opt/smokeping/etc/basepage.html

# vi /opt/smokeping/htdocs/tr.html

Change this:


	
	  
		SmokeTrace

To this:


	
	  
		SmokeTrace

# ln -s /opt/smokeping/htdocs/tr.html /var/www/html/smokeping/tr.html

Lets create a basic Config file for Smokeping to get started:

# vi /opt/smokeping/etc/config

*** General ***

owner    = Peter Random
contact  = some@address.nowhere
mailhost = my.mail.host
sendmail = /usr/sbin/sendmail
# NOTE: do not put the Image Cache below cgi-bin
# since all files under cgi-bin will be executed ... this is not
# good for images.
imgcache = /var/www/html/smokeping/img
imgurl   = http://www.how2centos.com/smokeping/img
datadir  = /opt/smokeping/data
piddir  = /opt/smokeping/var
cgiurl   = http://www.how2centos.com/smokeping/smokeping.cgi
smokemail = /opt/smokeping/etc/smokemail
tmail = /opt/smokeping/etc/tmail

# specify this to get syslog logging
syslogfacility = local0

# each probe is now run in its own process
# disable this to revert to the old behaviour
# concurrentprobes = no

*** Alerts ***
to = alertee@address.somewhere
from = smokealert@company.xy

+someloss
type = loss
# in percent
pattern = >0%,*12*,>0%,*12*,>0%
comment = loss 3 times  in a row

*** Database ***

step     = 300
pings    = 20

# consfn mrhb steps total

AVERAGE  0.5   1  1008
AVERAGE  0.5  12  4320
    MIN  0.5  12  4320
    MAX  0.5  12  4320
AVERAGE  0.5 144   720
    MAX  0.5 144   720
    MIN  0.5 144   720

*** Presentation ***

template = /opt/smokeping/etc/basepage.html

+ charts

menu = Charts
title = The most interesting destinations

++ stddev
sorter = StdDev(entries=>4)
title = Top Standard Deviation
menu = Std Deviation
format = Standard Deviation %f

++ max
sorter = Max(entries=>5)
title = Top Max Roundtrip Time
menu = by Max
format = Max Roundtrip Time %f seconds

++ loss
sorter = Loss(entries=>5)
title = Top Packet Loss
menu = Loss
format = Packets Lost %f

++ median
sorter = Median(entries=>5)
title = Top Median Roundtrip Time
menu = by Median
format = Median RTT %f seconds

+ overview

width = 600
height = 50
range = 10h

+ detail

width = 600
height = 200
unison_tolerance = 2

"Last 3 Hours"    3h
"Last 30 Hours"   30h
"Last 10 Days"    10d
"Last 400 Days"   400d

#+ hierarchies
#++ owner
#title = Host Owner
#++ location
#title = Location

*** Probes ***

+ FPing

binary = /usr/sbin/fping

*** Targets ***

menuextra = (TR)

probe = FPing

menu = Top
title = Network Latency Grapher
remark = Welcome to the SmokePing website of xxx Company. \
         Here you will learn all about the latency of our network.

+ hosts
menu= Targets

++ How2CentOS

menu = How2CentOS.com
title = How2CentOS.com
alerts = someloss
host = www.how2centos.com

++ CentOS

menu = CentOS.org
title = CentOS.org
alerts = someloss
host = www.centos.org

Lets create a service startup script for Smokeping

# vi /etc/init.d/smokeping

#!/bin/bash
#
# chkconfig: 2345 80 05
# Description: Smokeping init.d script
# Hacked by : How2CentOS - http://www.how2centos.com

# Get function from functions library
. /etc/init.d/functions

# Start the service Smokeping
start() {
        echo -n "Starting Smokeping: "
        /opt/smokeping/bin/smokeping >/dev/null 2>&1
        ### Create the lock file ###
        touch /var/lock/subsys/smokeping
        success $"Smokeping startup"
        echo
}

# Restart the service Smokeping
stop() {
        echo -n "Stopping Smokeping: "
        kill -9 `ps ax | grep "/opt/smokeping/bin/smokeping" | grep -v grep | awk '{ print $1 }'` >/dev/null 2>&1
        ### Now, delete the lock file ###
        rm -f /var/lock/subsys/smokeping
        success $"Smokeping shutdown"
        echo
}

### main logic ###
case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  status)
        status Smokeping
        ;;
  restart|reload|condrestart)
        stop
        start
        ;;
  *)
        echo $"Usage: $0 {start|stop|restart|reload|status}"
        exit 1
esac

exit 0

# chmod 755 /etc/init.d/smokeping

Finally lets add Apache and Smokeping to startup and get them started:

# chkconfig smokeping on
# chkconfig httpd on
# service smokeping start
Starting Smokeping: [ OK ]
# service httpd start
Starting httpd: [ OK ]

Now browse to your new installed Smokeping and Smoketrace installation

http://www.how2centos.com/smokeping/smokeping.cgi

#Gentoo lost and #Debian losing to #CentOS

How2CentOS — Sun, 01 Aug 2010 19:09:30 +0000

If Linux distributions were stocks and you an investor you wish you’d have invested in CentOS. Time to sell what’s left and get yourself some steady and stable CentOS stocks, well at least according to Google Insights.

Installing #Redmine & #Subversion on CentOS 5.5

How2CentOS — Sun, 25 Jul 2010 11:24:55 +0000

In this CentOS 5.5 tutorial we will be installing Redmine and Subversion with LDAP authentication on a CentOS 5.5 i386 server. The assumption is that you have a basic to medium understanding of Apache and MySQL but if you follow this tutorial you should be able to complete the task successfully. A bit on the software that we’ll be using:

Redmine
Redmine is a flexible project management web application. Written using Ruby on Rails framework, it is cross-platform and cross-database. An online demo can be found here:
http://demo.redmine.org/

Subversion
Subversion is a free/open-source version control system. That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data, or examine the history of how your data changed.
http://subversion.apache.org/

Preliminary Note:
I am using a CentOS 5.5 i386 base installation in this tutorial.

* svn.how2centos.com (IP 10.0.0.100): CentOS 5.5 i386 base installation
* ldap.how2centos.com (IP 10.0.0.100): CentOS 5.5 i386 base installation
* redmine.how2centos.com (IP 10.0.0.100): CentOS 5.5 i386 base installation

Lets begin by installing the framework required by the Redmine, Subversion and LDAP platform.

# yum install yum-priorities
# rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
# yum update
# yum groupinstall “MySQL Database”
# yum install httpd
# yum install gcc-c++
# yum install ImageMagick ImageMagick-devel
# yum install subversion mod_dav_svn
# yum install perl-HTML-Parser perl-SVN-Notify
# yum install ruby rubygems rubygem-rails rubygem-sqlite3-ruby ruby-devel ruby-mysql

Next a couple of Ruby Gems

# gem install rack -v 1.0.1
# gem install cgi_multipart_eof_fix
# gem install coderay
# gem install thin

Now lets add the software to startup and start MySQL and Apache.

# thin install
# chkconfig thin on
# chkconfig mysqld on
# chkconfig httpd on
# service mysqld start
# service httpd start

Configure Thin

# thin config -C /etc/thin/(config-name).yml -c (rails-app-root-path) --servers (number-of-threads) -e (environment)

(application-name) = redmine
(rails-app-root-path) = /opt/redmine
(number-of-threads) = 3
(environment) = production

# thin config -C /etc/thin/redmine.yml -c /opt/redmine --servers 3 -e production

Download, install and configure the Redmine framework.

# cd /opt/
# wget http://rubyforge.org/frs/download.php/70486/redmine-0.9.4.tar.gz
# tar zxvf redmine-0.9.4.tar.gz
# mv redmine-0.9.4 redmine
# chmod -R a+rx /opt/redmine/public/
# cd /opt/redmine
# chmod -R 755 files log tmp

# cd /opt/redmine/config/
# cp database.yml.example database.yml
# vi /opt/redmine/config/database.yml

production:
  adapter: mysql
  database: redmine
  host: redmine
  username: redmine
  password: redmine
  encoding: utf8

# mysql

mysql> create database redmine default character set utf8;
mysql> grant all on redmine.* to redmine@localhost identified by ‘redmine’;
mysql> flush privileges;
mysql> quit

# cd /opt/redmine
# RAILS_ENV=production rake config/initializers/session_store.rb
# RAILS_ENV=production rake db:migrate

Configure Apache and add a Redmine config file

# vi /etc/httpd/conf/httpd.conf

Uncomment
NameVirtualHost *:80

# vi /etc/httpd/conf.d/redmine.conf


        DocumentRoot /opt/redmine
        ServerName redmine.how2centos.com
        
                 BalancerMember http://127.0.0.1:3000
                 BalancerMember http://127.0.0.1:3001
                 BalancerMember http://127.0.0.1:3002
        
        ProxyPass / balancer://redminecluster/
        ProxyPassReverse / balancer://redminecluster/
        ErrorLog /var/log/httpd/redmine_error.log
        CustomLog /var/log/httpd/redmine_access.log combined

Setup Redmine to email

# cp /opt/redmine/config/email.yml.example /opt/redmine/config/email.yml
# vi /opt/redmine/config/email.yml

production:
  delivery_method: :smtp
  smtp_settings:
    address: smtp.how2centos.com
    port: 25
    domain: how2centos.com
#    authentication: :login
#    user_name: "redmine@example.net"
#    password: "redmine"

development:
  delivery_method: :smtp
  smtp_settings:
    address: 127.0.0.1
    port: 25
    domain: how2centos.com
#    authentication: :login
#    user_name: "redmine@example.net"
#    password: "redmine"

Start thin and Redmine

# service thin start

Create a Subversion repository and start the SVN deamon

# svnadmin create /opt/svn/repo
# svnserve -d

Add a Subversion Apache configuration file

# vi /etc/httpd/conf.d/svn.conf

LoadModule dav_svn_module     modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so

LDAPSharedCacheFile /root/LDAPSharedCacheFile
LDAPSharedCacheSize 200000
LDAPCacheEntries 1024
LDAPCacheTTL 600
LDAPOpCacheEntries 1024
LDAPOpCacheTTL 600



        DocumentRoot /opt/svn
        ServerName svn.how2centos.com

        ErrorLog /var/log/httpd/svn_error.log
        LogLevel warn
        CustomLog /var/log/httpd/svn_access.log combined
        ServerSignature On

        
                AuthBasicProvider ldap
                AuthType Basic
                AuthzLDAPAuthoritative off
                AuthName "How2CentOS SVN server"
                AuthLDAPURL "ldap://ldap.how2centos.com/CN=Users,DC=how2centos,DC=com?sAMAccountName"
                AuthLDAPBindDN "CN=ldap,CN=Users,DC=how2centos,DC=com"
                AuthLDAPBindPassword LDAPpassword

                require valid-user

        

        
                DAV svn
                SVNParentPath           /opt/svn
                SVNListParentPath       On
                SVNReposName            "How2CentOS SVN Repo"
        

        
                SetHandler ldap-status

# chown -R apache:apache /opt/svn/*
# chmod -R 770 /opt/svn/*

Restart Apache for changes to take effect

# Service httpd restart

Browse to newly setup Redmine and Subversion setup

http://redmine.how2centos.com

http://svn.how2centos.com

CentOS: The most popular Linux distribution for web servers

How2CentOS — Sat, 10 Jul 2010 10:02:30 +0000

It’s a great day for CentOS and its community because, according to Web Technology Surveys, in July 2010, “For the first time, CentOS is now leading the Linux distribution statistics on web servers with almost 30% of all Linux servers.”

Create #Fedora 13 local #Yum Repository

How2CentOS — Thu, 24 Jun 2010 05:11:59 +0000

Fedora 13 (Goddard) is out and it’s time to add it to our arsenal of local yum repositories. We all know the importance of creating a local YUM repository on your LAN. Not only do you decrease the time it takes to download and install updates, you also decrease bandwidth usage.

Fedora 13 (Goddard) release notes

This How To will show you a simple yet effective way to create your local Fedora 13 YUM repository and client.

TIP: Distribute your Fedora YUM configuration via your Puppet Master

Preliminary Note:

I am using two Fedora 13 installations in this tutorial with server1.example.co.za configured with Apache httpd

* server1.example.co.za (IP 10.0.0.100): Fedora 13 YUM Repository and httpd server
* server2.example.co.za (IP 10.0.0.102): Fedora 13 YUM client

Configure Fedora YUM repo and httpd server as follows:

Create the following Directories:

# mkdir -p /var/www/html/fedora/13/os/i386
# mkdir -p /var/www/html/fedora/13/os/x86_64

Create a bash script that will rsync your local YUM Repository server with your local YUM mirror (Make sure the mirror supports rsync).

Fedora Mirror list – http://mirrors.fedoraproject.org/publiclist

# vi fedora-repo-update.sh

#!/bin/sh
# This script will create a local Fedora 13 mirror via Rsync
# Note: This script will download Fedora 13
#

rsync="rsync -avrt --bwlimit=256"

mirror=mirrors.kernel.org::mirrors/fedora

verlist="13"
archlist="i386 x86_64"
baselist="os"
local=/var/www/html/fedora/

for ver in $verlist
do
 for arch in $archlist
 do
  for base in $baselist
  do
    remote=$mirror/releases/$ver/Fedora/$arch/$base/
    $rsync $remote $local/$ver/$base/$arch/
  done
 done
done

# chmod 755 fedora-repo-update.sh

Add the bash script to your crontab to update your local repository every night (01H00 in this case)

# crontab -e

#       minute (0-59),
#       |       hour (0-23),
#       |       |       day of the month (1-31),
#       |       |       |       month of the year (1-12),
#       |       |       |       |       day of the week (0-6 with 0=Sunday).
#       |       |       |       |       |       commands
# -----------[ cron jobs  ]------------ #

# Update Local YUM repo update from fedora.mirror.facebook.net
	 0 	  1 	  * 	  * 	  * 	   /path/to/fedora-repo-update.sh

Configure Fedora YUM client servers as follows:

Rename all existing yum repositories from *.repo to *.old

# vi /etc/yum.repos.d/localFedora.repo

[base]
name=Fedora $releasever – $basearch
failovermethod=priority
baseurl=http://server1.example.co.za/fedora/$releasever/$basearch/os/
enabled=1
gpgcheck=0

Test your setup by running a yum update on your client machine.

# yum update

Loading “fastestmirror” plugin
Loading mirror speeds from cached hostfile
* update: server1.example.co.za
* base: server1.example.co.za

Enabling #multimedia support on #CentOS 5.5

How2CentOS — Tue, 01 Jun 2010 10:42:34 +0000

The CentOS base repository has no way to install the codecs and utilities we need to be able to play an MP3 or watch a DIVX movie. In this guide I will show you how to get all the multimedia support you want, as well as being able to use flash to view flash enabled websites.

Firstly we need to install the RPMForge repository, so that we can get access to all the codecs and applications we need. The repository comes in two flavors, namely 64-bit and 32-bit. Make sure you select the correct repository to install. When in doubt, select 32-bit.

For 32-bit installations (i.e. CentOS 5.x 32-bit installed), enter the following into your console/terminal:

# wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.i386.rpm
# su -c ‘rpm -Uvh rpmforge-release-0.5.1-1.el5.rf.i386.rpm’