Friday, June 3, 2011

PNP4Nagios with CentOS

PNP4Nagios with CentOS:

PNP is an addon to Nagios which analyzes performance data provided by plugins and stores them automatically into RRD-databases

Prerequisites

RRDtool is the OpenSource industry standard, high performance data logging and graphing system for time series data. Use it to write your custom monitoring shell scripts or create whole applications using its Perl, Python, Ruby, TCL or PHP bindings.
Our CentOS server needed a few devel libraries installed for RRDtool:

yum -y install cairo-devel glib2-devel pango-devel

Download the latest source for RRDtool

mkdir ~/downloads && cd ~/downloads wgethttp://oss.oetiker.ch/rrdtool/pub/rrdtool-1.4.3.tar.gztar zxf rrdtool-1.4.3.tar.gz cd rrdtool-1.4.3

Configure it with a few adjustments for our setup:

./configure --prefix=/usr/local/rrdtool

If everything is ok, then build and install it

make make install

Zlib support for PHP - --with-zlib

Installation
Download the latest version of PNP4Nagios:

cd /extra/src wgethttp://sourceforge.net/projects/pnp4nagios/files/PNP-0.6/pnp4nagios-0.6.3.tar.gz/download tarzxf pnp4nagios-0.6.3.tar.gz cd pnp4nagios-0.6.3

Configure it:

./configure \ --with-rrdtool=/usr/local/rrdtool/bin/rrdtool \ --with-httpd-conf=/usr/local/apache2/conf/extra \ --with-perl_lib_path=/usr/local/rrdtool/lib/perl/5.8.8/i386-linux-thread-multi

Then build and install:

make all make install

Copy the sample config files:

make install-config

Add pnp4nagios to your Apache configuration:

Install the Apache config file into /etc/httpd/conf.d/pnp4nagios.conf:

make install-webconf

Then edit /etc/httpd/conf/httpd.conf and add a line to load the PNP4Nagios conf file:

Include conf.d/pnp4nagios.conf

or can add the contents of httpd.conf to your Nagios VirtualHost directive:

Alias /pnp4nagios "/usr/local/pnp4nagios/share" AllowOverride None Order allow,deny Allow from all # # Use the same value as defined in nagios.conf # AuthName "Nagios Access" AuthType Basic AuthUserFile /usr/local/nagios/etc/htpasswd.users Require valid-user # Turn on URL rewriting RewriteEngine On Options FollowSymLinks # Installation directory RewriteBase /pnp4nagios/ # Protect application and system files from being viewed RewriteRule ^(application|modules|system) - [F,L] # Allow any files or directories that exist to be displayed directly RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d # Rewrite all other URLs to index.php/URL RewriteRule .* index.php/$0 [PT,L]

- It might show error related to php-5.2, if it shows such issue add CentOS-Test repository and add following configuration as:

vi /etc/yum.repos.d/CentOS-Test-repo

[CentOS-testing]

name=CentOS-5 Testing

baseurl=http://dev.centos.org/centos/5/testing/$basearch/

enabled=1

gpgcheck=1

gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing

update php:

yum update php

Restart httpd service:

service httpd restart

Access the PNP4Nagios Environment Tests by going to http://localhost/pnp4nagios. If it passes all the tests, remove the install.php file:

`mv /usr/local/pnp4nagios/share/install.php /usr/local/pnp4nagios/share/old.install.php`

NPCD Daemon

Copy the sample NPCD config file:

`cp /usr/local/pnp4nagios/etc/npcd.cfg-sample /usr/local/pnp4nagios/etc/npcd.cfg`

Data Collection :
Nagios needs to be configured to trigger the data collector by editing `/usr/local/nagios/etc/nagios.cfg` and editing/uncommenting some lines:

`process_performance_data=1 service_perfdata_command=process-service-perfdata host_perfdata_command=process-host-perfdata`

Edit `/usr/local/nagios/etc/objects/commands.cfg` and remove the existing process-service-perfdata and process-host-perfdatacommands. Then add the new PNP4Nagios commands for service and host performance data logging:

`define command { command_name process-service-perfdata command_line /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl } define command { command_name process-host-perfdata command_line /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl -d HOSTPERFDATA }`

Nagios Web Front-End Integration :
In order to easily view the graphs from your Nagios server, we can take advantage of Nagios' external URL features in extended info configs. There are two ways of doing it - regular links or Javascript pop-ups:

Regular Links
Edit `/usr/local/nagios/etc/objects/templates.cfg` and add:
`# PNP4Nagios host/service definitions define host { name host-pnp action_url /pnp4nagios/graph?host=$HOSTNAME$&srv=_HOST_ register 0 } define service { name srv-pnp action_url /pnp4nagios/graph?host=$HOSTNAME$&srv=$SERVICEDESC$ register 0 }`

OR

Javascript pop-ups :
Copy status-header.ssi to your Nagios web files:
`cp /downloads/pnp4nagios-0.6.3/contrib/ssi/status-header.ssi \ /usr/local/nagios/share/ssi/`
Edit `/usr/local/nagios/etc/objects/templates.cfg` and add:
`define host { name host-pnp action_url /pnp4nagios/graph?host=$HOSTNAME$&srv=_HOST_' class='tips' rel='/pnp4nagios/popup?host=$HOSTNAME$&srv=_HOST_ register 0 } define service { name srv-pnp action_url /pnp4nagios/graph?host=$HOSTNAME$&srv=$SERVICEDESC$' class='tips' rel='/pnp4nagios/popup?host=$HOSTNAME$&srv=$SERVICEDESC$ register 0 }`

To use them, add them to your host/service definitions with something similiar to:

`define host{ use linux-server,host-pnp ; Name of host templates to use ; This host definition will inherit all variables that are defined ; in (or inherited by) the linux-server host template definition. host_name localhost alias localhost address 127.0.0.1 } define service{ use local-service,srv-pnp ; Name of service template to use host_name localhost service_description PING check_command check_ping!100.0,20%!500.0,60% }`

Wednesday, June 1, 2011

SWAP Memory (Creating Swap file)

What is swap?

Swap space is an area on disk that temporarily holds a process memory image. When physical memory demand is sufficiently low, process memory images are brought back into physical memory from the swap area on disk. Having sufficient swap space enables the system to keep some physical memory free at all times.

There are three types of swap: device swap, file system swap and pseudo swap. Device swap is a separate partition allocated when the disk is configured. File system swap allows you to use the existing file system to allocate swap space. Pseudo swap is allocated from system memory on some systems.

How can I create swap on these machines?

Though we cannot create device swap, we can still create create file system swap. Steps are given below to create swap file:log-in as root and check your existing mounted partitions to create swap file using disk usage utility :

[root@shah-lp ~]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 9.9G 7.8G 1.6G 84% /

none 7.6G 0 7.6G 0% /dev/shm

/dev/sdb1 414G 32G 362G 8% /share

As we can see above /dev/sdb1 is mounted at /share and it got enough space to create swap file.

Assume my machine got 4GB physical RAM & 2GB of SWAP. Now we are looking to increase it to 8GB, 6GB more. follow below steps:

[root@shah-lp ~]# dd if=/dev/zero of=/share/swapfile bs=1G count=5

5+0 records in

5+0 records out

5368709120 bytes (5.4 GB) copied, 64.3235 seconds, 83.5 MB/s

[root@shah-lp ~]# mkswap /share/swapfile

[root@shah-lp ~]# swapon /share/swapfile

[root@shah-lp ~]# echo " /share/swapfile swap swap defaults 0 0" >> /etc/fstab

[root@shah-lp ~]# mount -a

To confirm run :

[root@shah-lp ~]# free -m

total used free shared buffers cached

Mem: 15367 11428 3938 0 53 10378

-/+ buffers/cache: 996 14370

Swap: 23551 0 23551

[root@shah-lp ~]# swapon -s

total used free shared buffers cached

Mem: 15367 11428 3938 0 53 10378

-/+ buffers/cache: 996 14370

Swap: 23551 0 23551

Introduction to Linux for beginners

History

UNIX

In order to understand the popularity of Linux, we need to travel back in time, about 30 years ago, imagine computers as big as houses, even stadiums. While the sizes of those computers posed substantial problems, there was one thing that made this even worse: every computer had a different operating system. Software was always customized to serve a specific purpose, and software for one given system didn’t run on another system. Being able to work with one system didn’t automatically mean that you could work with another. It was difficult, both for the users and the system administrators. Computers were extremely expensive then, and sacrifices had to be made even after the original purchases just get the users to understand how they worked. The total cost of IT was enormous. Technologically the world was not quite that advanced, so they had to live with the size for another decade. In 1969, a team of developers in the Bell Labs laboratories started working on a solution for the software problem, to address these compatibility issues.

Bell Labs

UNIX was originally developed for internal use at AT&T Bell Labs by researchers Ken Thompson and Dennis Ritchie. AT&T licensed the source code, widely allowing many companies to modify and produce UNIX-like operating systems. Because AT&T held the UNIX name, other companies had to create their own names to brand the modifications ad additions they had made: AIX from IBM, HP/UX from Hewlett-Packard, SunOS (later Solaris) from Sun, and Mac from Apple.

They developed a new operating system, which was Simple and elegant.

Features

Written in the C programming language instead of in assembly code.
Able to recycle code.
the Bell Labs developers named their project “UNIX”

The code recycling features were very important. Until then, all commercially available computer system were written in code specifically developed for one system. UNIX on the other hand needed only a small piece of that special code, which is now commonly named the kernel. This kernel is the only piece of code that needs to be adapted for every specific system and forms the base of the UNIX system. The operating system and all other functions were built around this kernel and written in a higher programming language ‘C’.

This language was especially developed for creating the UNIX system. Using this new technique, it was much easier to develop an operating system that could run on many different types of hardware.

The software vendors were quick to adapt, since they could sell ten times more software almost effortlessly. Weird new software came in existence: imagine for instances computers from different vendors communicating in the same network, or users working on different systems without the need for extra education to use another computer. UNIX did a great deal to help users become compatible with different systems. Throughout the next couple of decades the development of UNIX continued. More things became possible to do and more hardware and software vendors added support for UNIX to their products. UNIX was initially found only in very large environments with mainframes and minicomputers (note that a PC a “micro” computer). You had to work at a university, for the government or for large financial corporations on order to get your hands on UNIX system. But smaller computers were being developed, and by end of the 80s, many people had home computers. By that time, there were several versions of UNIX available for the PC architecture, but none of them were truly free.

GNU Project/FSF

GNU project started in 1984 by Richard Mathew Stallman. Project goals were to create “free” UNIX clone, by 1990, nearly all required user space applications created and FSF stands for Free Software Foundation is non-profit organization that manages GNU project.

Philosophy

The term free software may have a different meaning than you expect. The term doesn’t refer to the cost of the software, but the fact that end user has the freedom to modify and change the program.

“Free software” refers to the users’ freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:

The freedom to run the program, for any purpose.
The freedom to study how the program works, and adapt it to your needs
The freedom to redistribute codes (software) so you can help your neighbor.
The freedom to improve program, and release your improvements to public, so that the whole community benefits.

Linus and Linux

Linus Torvalds, a young man studying computer science at the University of Helsinki, thought it would be a good idea to have some sort of freely available academic version of UNIX, and promptly stared to code.

He started to ask questions, looking for answers and solutions that would help him get UNIX on his PC.

From the start, it was Linus’ goal to have free system that was completely compliant with the original UNIX.

That is why he asked for POSIX standards, POSIX still being the standard for UNIX.

In those days plug-and-play wasn’t invented yet, but so many people were interested in having a UNIX system of their own, that was only a small obstacle. New drivers became available for all kind of new hardware, at a continuously rising speed. Almost as soon as new piece of hardware became available, someone bought it and submitted it to the Linux test, as the systems was gradually being called, releasing more free code for an ever wider range of hardware. These coders didn’t stop at their PC’s, every piece of hardware they could find was useful for Linux. Back then, those people were called “nerds” or “freaks”, but it didn’t matter to them, as long as the supported hardware list grew longer and longer. Thanks to these people, Linux is now not only ideal to run on new PC’s but it also the system of choice for old and exotic hardware that would be useless if Linux didn’t exist.

Introduction to Linux

Two years after Linus’ post, there were 12000 Linux users. The project, popular with hobbyists, grew steadily, all the while staying within the bounds of the POSIX standard. All the features of the UNIX were added over the next couple of years, resulting in the mature operating system Linux has become today. Linux is a full UNIX clone, fit for use on workstations s well as on middle-range and high-end servers. Today, all the important players on the hard and software market each have their team of Linux developers, at your local dealer’s you can even buy pre-installed Linux systems with official support.

Why Linux is better?

Cost -- Linux is free, and that includes all the apps. Microsoft is greedy. Vista Home Premium and Ultimate cost hundreds of dollars, even when upgrading from Windows XP. Moving up to Office 2007 involves handing over another bundle of dollars.
Resources -- Even the most lavishly equipped Linux distros demand no more resources than Windows XP. Vista is greedy: a single-user PC operating system that needs 2GB of RAM to run at acceptable speed, and 15GB of hard disk space, is grossly obese.
Performance -- Linux worked faster on my Dell Inspiron Core Duo than XP, at least the way XP worked out of the box. After cleaning out the bloatware and trading McAfee's Abrams Tank for the lightweight NOD32, XP and Linux (with Guarddog and Clam-AV) perform at similar speed.
No bloat ware -- Linux is free from adware, trialware, shovelware, and bloat ware. Running Linux is like watching the public TV network.
Security -- Last year, 48,000 new virus signatures were documented for Windows, compared to 40 for Linux. Still, most bistros come with firewalls and anti virus (AV) software. Programs like Guard dog and Clam-AV are free, of course.
Dual booting -- The best Linux distros make dual booting a simple affair, along with the required disk partitioning (so you don't need to buy partitioning software). Windows on my Dell laptop is still intact after installing and uninstalling a dozen distros.
Installation -- Anyone who's done it once knows that installing Windows from scratch takes hours or even days by the time you get all your apps up and running. With Linux, it can take as little as half an hour to install the operating system, utilities, and a full set of applications. No registration or activation is required, no paperwork, and no excruciating pack drill.
Reinstalling the OS -- You can't just download an updated version of Windows. You have to use the CD that came with your PC and download all the patches Microsoft has issued since the CD was made. With Linux, you simply download the latest version of your distro (no questions asked) and, assuming your data files live in a separate disk partition, there's no need to reinstall them. You only need to re-install the extra programs you added to the ones that came with the distro.
Keeping track of software -- Like most Windows users, I have a shelf full of software CDs and keep a little book with serial numbers under my bed in case I have to reinstall the lot. With Linux, there are no serial numbers or passwords to lose or worry about. Not a single one.
Updating software -- Linux updates all the software on your system whenever updates are available online, including all applications programs. Microsoft does that for Windows software but you have to update each program you've added from other sources. That's about 60 on each of my PCs. More icing on the Linux cake is that it doesn't ask you to reboot after updates. XP nags you every ten minutes until you curse and reboot your machine. If you choose "custom install" to select only the updates you want, XP hounds you like a mangy neighborhood dog until you give in.
More security -- These days, operating systems are less vulnerable than the applications that run on them. Therefore a vital aspect of PC security is keeping your apps up-to-date with the latest security patches. That's hard manual labor in Windows, but with Linux it's automatic.
No need to defrag disks -- Linux uses different file systems that don't need defragging. NTFS was going to be replaced in Vista, but Microsoft's new file system didn't make the final cut. Instead, Vista does scheduled disk defragging by default, but the defrag utility is a sad affair.
A wealth of built-in utilities -- The utilities supplied with Windows are pretty ordinary on the whole, that's why so many small software firms have made a nice living writing better ones. Linux programs are comparable with the best Windows freeware, from CD burners to photo managers, memory monitors and disk utilities. PDF conversion is built-in, both into OpenOffice Writer and into the DTP application Scribus. All you do is click a button on the task bar.