All posts by bsdman

Currently working as an IT Manager. Worked for an OIT company as a Network Engineer in 2011. Worked for a Medical IT company as the Network Administrator 2009-2011. Worked as the Senior Systems Administrator at a computer reseller from 2005-2009. Worked as a Computer Consultant for several small companies from 2007-2009. Worked as a Computer Technician at a computer reseller from 2002-2004.

Install Nagios on Ubuntu 9.x, Client on Windows

This is how I got nagios to install on my Ubuntu 9.10 x86 server (LAMP):
***EDIT*** I’ve upgraded the 9.10 x86 server to 10.04LTS x86 and Nagios is still running like a champ. FYI.

This assumes you’ve already got LAMP up and running on the box and have at least a little common sense when it comes to linux commands. I still use putty to connect via SSH to my box. I also cheated and made it so I don’t do sudo (sudo passwd root, then su into root). If you don’t want to do that, just add ‘sudo’ in front of all the commands.

Update your box:
apt-get update
apt-get upgrade
apt-get dist-upgrade

Install the GCC compiler development libraries:
apt-get install build-essential

Install GD development libraries:
apt-get install libgd2-xpm-dev

Create a new user “nagios”:
useradd -m -s /bin/bash nagios

Make a password for the new user:
passwd nagios

Create a new group “nagcmd”
groupadd nagcmd
usermod -a -G nagcmd nagios
usermod -a -G nagcmd www-data

Download the nagios files – I use /home/username as my download point:
wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.0.tar.gz
wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.14.tar.gz

Extract and compile the files:
tar xzf nagios-3.2.0.tar.gz
cd nagios-3.2.0
./configure --with-command-group=nagcmd
make all
make install
make install-init
make install-config
make install-commandmode
make install-webconf

Create a nagiosadmin account for the web interface:
htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

Restart Apache
apache2ctl restart

That should be it for the installation phase of the main application. You can verify that everything works by viewing the site: http://localhost/nagios (or http://ipofserver/nagios) and logging in using nagiosadmin/thepasswordyoupicked. But now we should probably put the plugins in place before actually going through any other setup.

Unpack the plugins:
tar xzf nagios-plugins-1.4.14.tar.gz
cd nagios-plugins-1.4.14

Configure and install the plugins:
./configure --with-nagios-user=nagios --with-nagios-group=nagios
make
make install

Verify that the sample nagios configuration files are fine:
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

If there are no errors you can start nagios:
/etc/init.d/nagios start

http://localhost/nagios
Click on the Tactical Overview navbar link to see all that’s monitored right now. This may take a few moments to load as to not “kill” the machine with requests.

http://www.monitoringexchange.org/

INSTALL CLIENT ON WINDOWS MACHINE(S):
I’ve installed on WindowsXP 32, Windows Server 2003 32/64, and Windows 7 64bit without any issues.

Setting up for Windows Machine monitoring is a little more in depth:

Download the NSClient++:
http://nsclient.org/nscp/downloads
Extract to the C:\ directory
Open a CMD prompt and navigate to C:\NSClient++-0.3.7-Win32

Install the Service and System Tray:
The system tray gave me some issues on a Windows 7 x64 box. FYI.
nsclient++ /install
nsclient++ SysTray -install

Configure the NSClientpp Service:
Open up services (services.msc) and find NSCLientpp (Nagios)
Right-Click and select properties
Click on the Log On tab and make sure the Local System account can interact with the desktop

Edit the INI file:
Navigate to C:\NSClient++*\
Edit NSC.INI

Uncomment the following:

FileLogger.dll
CheckSystem.dll
CheckDisk.dll
NSClientListener.dll
NRPEListener.dll
SysTray.dll
CheckEventLog.dll
CheckHelpers.dll

Uncomment the hosts allowed file – either add the IP address of the Nagios server or just leave it blank and it will accept from all IPs.

Save the file, Start the service – I’ve had it work without interact with desktop, but it was recommended by Nagios to enable that feature.

Back on the Nagios server, edit the /usr/local/nagios/etc/objects/windows.cfg file to the liking of your windows machine.
You may have to add the host name/ip to your /etc/hosts file to rid yourself of errors

Verify your setup can run:
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Then restart nagios:
/etc/init.d/nagios restart

Now you should be done. Login to your http://serverip/nagios site with your nagiosadmin/passwordyouchoseearlier account information.

As a side note, I also edited /usr/local/nagios/etc/nagios.cfg for the admin_email= to send email to my account. I already have postfix installed from another project, so it *should* send me alert emails. AND I found that you have to edit /usr/local/nagios/etc/objects/contacts.cfg as well. After editing make sure you restart the nagios service.

***EDIT***

I was receiving the emails just fine, but they were coming from the “wrong domain”. Ubuntu/debian puts the domain name by default in the /etc/mailname file. Edit that file and then reload postfix.
nano /etc/mailname
postfix reload

If the file does not exist (you’re creating a new file with nano), type in your domain name (ie thelibrarie.com), and then save the file. Then edit the postfix configuration and uncomment myorgin.
nano /etc/mailname
nano /etc/postfix/main.c

myorigin = /etc/mailname

And then try it again. You can test it out by sending yourself some mail:
mail -s test username@domain.tld
body
Control + D
Control + D

I also realized that I put how to install the client on Windows machines, so I should probably mention that in the subject, eh?

***EDIT***
OK, I had to add another user to be able to view the status of the systems.
Add the User:
SSH to your nagios system
htpasswd /usr/local/nagios/etc/htpasswd.users USERNAMEHERE
apache2ctl restart

Add the permissions:
nano /usr/local/nagios/etc/cgi.cfg
Search under GLOBAL HOST/SERVICE VIEW ACCESS
Change:
authorized_for_all_services=nagiosadmin
authorized_for_all_hosts=nagiosadmin
to:
authorized_for_all_services=*
authorized_for_all_hosts=*

Or you can comma-delimit the users. Either way, I win.

Restart nagios.
/etc/init.d/nagios restart

***EDIT 2***
Need more plugins? http://nagios.manubulon.com/

***EDIT 3***
There will be a new post regarding editing Nagios to add images to the map/new users/parents of configurations etc.

PHPSysInfo and LM-Sensors

I wanted to get phpsysinfo working with the hardware sensors suite known as lm-sensors, but I really didn’t feel like working through all the problems myself. But, despite my attempts to be lazy, I actually had to work a little bit at this.

First of all, this is running on an Ubuntu Server 9.10 x86 – 2.6.31-14-generic-pae to be exact – using an old Dell Precision 360 box to be even more exact. I installed phpsysinfo version 2.5.4 and edited the config.php file to enable lm-sensors hardware monitoring.

Unfortunately I get this error when I navigate to http://myserverip/phpsysinfo:

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Return value: 0

Wonderful. So I have to install lm-sensors. Now another site told me to do the following:
sudo apt-get install lm-sensors i2c-tools read-edid sensord hddtemp sensors-applet
After the lengthy download (153MB I believe), hddtemp needed some input. The defaults are fine – I selected to start the hddtemp service every reboot and run it on the default port 7634 as this is an internal only server. If it’s an externally facing server you may want to exercise some caution when opening ports.

You can verify that this is working by navigating to http://yourserverip:7634
In my case I see:

|/dev/sg0|ST380011A|38|C||/dev/sda|ST380011A|38|C|

Which I can see the Seagate HD that’s 80GB IDE with two mount points running at 38C (100.4F).

Now to setup for other sensors. Go back to your terminal session and type:
sudo sensors-detect
Hit YES for everything. When the script finishes you should probably reboot:
reboot

Reload your http://yourserverip/phpsysinfo page – you should now see a bunch of other stuff added at the bottom:
lm-sensors

Remove Annoying Logon Background Image

I had to RDP to a server several times before this actually started to bother me:
Dell has their own image set as the default background during the login prompt. RDP over the internet enough and the slow loading of the background starts to eat away at you.

It’s a simple registry hack to fix it:

Start – Run
regedit
HKEY_USERS\.DEFAULT\Control Panel\Desktop
Find a key named Wallpaper
Change the key’s data to (None) instead of C:\windows\dellcrap\dellcrapimage.bmp
Close out of the registry editor
Wait a few minutes and it should be gone when you try to login.

This worked on Windows XP and Windows Server 2003.

What Version Of Linux Am I Running?

I wanted to upgrade my Ubuntu installation to the latest version, but wanted to make sure that it wasn’t already updated (shared servers are fun).

uname -a shows a decent amount of information, but I wanted to know what version of ubuntu I was currently on. With Ubuntu 9.10 released today, I ran some quick updates:
apt-get update
apt-get upgrade
apt-get dist-upgrade

uname -a
Showed this:

Linux ubuntuserver 2.6.28-16-server #55-Ubuntu SMP Tue Oct 20 20:50:00 UTC 2009 i686 GNU/Linux

lsb_release -a
Showed this:

Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

So I’m still on 9.04.

Then I realized I have to update some more…

apt-get install update-manager-core
do-release-upgrade
I then got this error:

This session appears to be running under ssh. It is not recommended
to perform a upgrade over ssh currently because in case of failure it
is harder to recover.

So I decided to run it local. At a whopping 50KB/sec this will take a while:

11 packages are going to be removed. 110 new packages are going to be installed. 444 packages are going to be upgraded.

You have to download a total of 332M. This download will take about 1 hour 10 minutes with your connection.

Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be cancelled.

I think I’ll eat lunch while it’s doing its thing.

Change Login Screen Windows 7 Vista

I wanted to change the login screen for Windows 7 and Vista. I know I had a program on Vista that allowed me to change it without a problem, but I can’t seem to find it after I wiped out the drive :).

So anyway, here’s another free way to change it without going into the registry yourself:
http://it.thelibrarie.com/utilities/W7C%20LogonUI%20Changer.exe

Open it up, click on the middle, select your picture, and away you go. It resizes and everything. Yay.

Or for the jerks out there that want to remotely have fun with coworkers:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background

Check to see if a DWord value named OEMBackground exists and has a value of 1. If not, right click the white-space and create a DWORD Value for this.

Put an UNDER 256KB file in this directory:
%windir%\system32\oobe\info\backgrounds
Name the file backgroundDefault.jpg

Foobar2000 MSN Show Song Playing

I like software that just works. If it works well and uses minimal resources all the better. That’s why I like foobar 2000. I’m using it to play all of my songs and it’s using a slim 20MB. And yes, it works under Windows 7 64bit.

But one feature that was missing was the ability to show my fellow MSN (or Windows Live Messenger) users what I was currently listening to. Not that anyone cares, but it bothered me that both iTunes and Media Player could provide this information but foobar couldn’t.

There’s a plugin just for this reason – it works well under 0.9.6.9 so far.

Download this: http://it.thelibrarie.com/utilities/foo_msnalt.dll
Put the file in your foobar 2000 components folder (in my case it’s C:\Program Files (x86)\foobar2000\components)
Restart Foobar2000

You should now notice that MSN will display the song (assuming you set it to do so) in your status. Rock on.

Install Windows 7 or Vista via USB

I believe I already posted a how-to regarding installing Windows XP from a USB key flash drive thumb drive. Now we’re onto the next OS – Windows 7. This should work with Vista as well as they use the same boot loader. This will NOT work with XP.

You must have a USB Flash Drive of 4GB or more
You must have the Windows 7 or Vista installation files handy – OEM, Retail, or VL works ON CD OR ISO not just in a random folder
This process will ERASE your Flash drive, so make sure you don’t have anything on there you need to keep

Open the command prompt (Windows Key + R)
If you have any problems with the commands, try typing “cmd” into the Start Menu search box and then press Control + Shift + Enter to activate the admin privileged command prompt

Type diskpart
This will start the disk partition utility

list disk
This will show all of the disk’s currently in the disk management utility. In most cases Disk 1 will be your USB drive. MAKE SURE that this is the case BEFORE trying any of the following commands.
select disk 1
This selects the disk that you found from the previous command
clean
This clears out the partition tables
create partition primary
This creates a primary partition – primary is needed as a boot device
select partition 1
This selects the primary partition
active
This makes the primary partition active so it can be booted
format fs=ntfs
This formats the device with the filesystem NTFS. It took almost 30 minutes on a 16GB device
assign
This assigns all changes to the device
exit
Exits the utility

Keep the Command Window open though. We’ll be needing it again.

Now insert the CD or mount the ISO image. We need the 7 or Vista files to be mounted as a drive letter. Take note of the drive letter, in my case it’s G:
Also take note of the drive letter for your Flash Drive – in my case it’s F:

G: hit enter
cd boot hit enter
bootsect.exe /nt60 f: hit enter

Now copy all of the files from your DVD/ISO to the USB Flash Drive.

Once you’re done, reboot your machine and select the USB HD as your boot device.

That’s it!