$ sudo service squid3 {start|stop|restart}

To specify what to run, an upstart must have exec or script stanza. When the goal is to start two or more (multiple) instances of squid3, exec is meant to replace existing process image of /usr/sbin/squid3 executable, therefore will not start two instances.

Multiple squid3 instances started via upstart exec

As workaround we can have symbolic link to squid3 executable instead and add new upstart job configuration with exec call to the link. I need two instances running in the same machine due to the implementation design where the fist instance is HTTP proxy cache while the second one is accelerator/interceptor (reverse proxy) that serves default landing page telling user to use proxy (and how to do that). Hence, for the second instance I add:

lrwxrwxrwx 1 root root 6 May  3 09:25 /usr/sbin/squid3ins2 -> squid3
-rw-r--r-- 1 root root 1156 May  6 13:30 /etc/init/squid3ins2.conf

and for the first instance I add:

-rw-r--r-- 1 root root 298 May  3 10:13 /etc/init/squid3.override

squid3ins2 is our link and /etc/init/squid3ins2.conf contains exec call to it to run second squid3. For the first instance I choose to write an override (/etc/init/squid3.override) so that the original job configuration file is left intact. For the complete content of all files check my github v1.1 of the Squid integration. There, in details you’ll also find how both instances PID, log, etc. are differentiated by each instance config via the following directives:

http_port
cache_dir
pid_filename
cache_access_log
cache_log

..you’ll always have love-hate relationship with the tools you work with.. blindly turning yourself into devoted-fanatic is another thing..

Enough bragging (let’s spare that). First we need to have /dev/tap0, /dev/tap1, etc., available using TunTap kernel extension.

I modify the small script from this post to have it available on background instead of keeping a shell open all the time:

I saved it as /usr/local/bin/setup-tap1.py

1
2
3
4
5
6
7
8
9
10
11
12
13
14

#!/usr/bin/python
 
import os
while 1:
	try:
		file_path = '/dev/tap1'
		dev_file = os.open(file_path, os.O_RDWR)
		interface = 'tap1'
		while 1:
			pass
	except:
		print "tap interface is closing"
		exit()
		break

Let the shell takes care of putting it to background (daemon):

[root]$ /usr/local/bin/setup-tap1.py &

and there you have one working tap interface:

VirtualBox tap interface in Mac OSX Lion 10.7

[Moving-in would probably be easier if I started life with FreeBSD. More posts to come]

I decided to install in RedHat 5.2. Maybe it is easier in Ubuntu (Nagios 3 already listed in the repository, but I haven’t tried it). As pointed out by the quickstart (it is meant for Fedora by the way), requirements are:

1. php, httpd
2. gcc, glibc, glibc-common
3. gd, gd-devel

After getting those, the configure-make-install procedure runs well, except that I don’t check the warnings. It turns out that only some of Nagios core components are installed. It can be seen from the content of /usr/local/nagios/libexec directory. There is no check_snmp etc. Error also appears in statusmap page of Nagios.

Compile More Nagios Core Components

I run through ./configure once more, check out all warnings, and begin to evaluate requirements (found this text inside nagios-plugins-1.4.14 tarball)

MySQL

For check_mysql functionality, mysql (MySQL client for linux) must be installed. ./configure also test this client, by default config, to the local MySQL socket, hence mysql-server must also exist.

Radius Client

Client from freeradius package doesn’t meet Nagios requirements. It must be the ones from original radiusclient, I found RPMs for radiusclient-0.3.2-0.2.el5.rf.i386.rpm and radiusclient-devel-0.3.2-0.2.el5.rf.i386.rpm.

GD

It is quite tricky to get statusmap.c to be compiled for the .cgi of Nagios status map. Compilation needs gd library from http://www.libgd.org/. gd requires zlib, libjpeg, and libpng. On first attempt, I installed from RPMs. This appeared to be not working as I could still see warnings about gd2 during ./configure.

So, I choose to compile from the source gd-2.0.33.tar.bz2. This tarball was found in the older section of current gd2 web. I chose this version because the RPM used was gd-2.0.33-9.4.el5_1.1.rpm. I removed this RPM first which made me to remove also libmwf and ImageMagick.

After straightforward  configure-make-install the library will be installed under /usr/local/lib i.e libgd.so.2.0.0. Header files will also be available in /usr/local/include i.e gd.h. These are different from the situation when I installed from RPM where libgd.so.2.0.0 is under /usr/lib/ and no gd.h found under /usr/include.

So, I make devclean and rerun

./configure --with-gd-lib=/usr/local/lib --with-gd-inc=/usr/local/include --with-command-group=nagcmd

I configure the /usr/local/nagios/etc/cgi.conf but status map page is still empty. Next workaround is to install back  gd-2.0.33-9.4.el5_1.1.rpm. (which also bring back libmwf and ImageMagick) and point the gd library to the ones created from RPM. I make devclean and rerun:

./configure --with-gd-lib=/usr/lib --with-gd-inc=/usr/local/include --with-command-group=nagcmd

At this point I regret not to have Ubuntu implementation in the first place. Just a small regret.

Other library needed for check_smtp, check_http, etc. don’t seem to trouble me much, I need openssl, openldap, etc. and simply get them from RPMs.

$ sudo make install

After that I test tagsistant to organize /data/tags/

$ tagsistant /data/tags

The tagging works as expected but not too handy since no browser GUI is embedded. It is just like browsing through multiple OR and AND folders.

The installation process will also install tagman (a tag manager GUI) if libgtk2.0-dev and libglib2.0-dev are installed.