[mdlug] Fwd: [Nagios problem]

[David L Lambert]

A few weeks ago I decided to start playing with Nagios again.  I have 
two desktops which sit next to each other in the basement, each 
performing some "server" functions.  Both run Debian 7, and one of them 
runs a couple of qemu VMs ... one for Debian 7 as well, one for Windows 
XP.  The one running VMs is 32-bit, Intel CPU, 3.4GHz, dual-core, 2GB 
RAM;  the other is 768M RAM (actually "709432 kB", I think the on-board 
video borrows some memory), single-core AMD at 700 MHz.

I installed the Nagios controller stuff (packages "nagios3-cgi", 
"nagios3-core") on the Debian 7 VM.  Problem is, it generates a big 
batch of alerts, including ones like the below that are just about being 
unable to connect via SSH to one of the hosts it's monitoring, two or 
three times a day.  The VM doesn't seem to be underpowered on memory:

$ free
              total       used       free     shared    buffers     cached
Mem:        482236     471508      10728          0     104420     187992
-/+ buffers/cache:     179096     303140
Swap:       498004       3432     494572


Perhaps the virtual CPU just isn't fast enough for this load? Is Nagios 
really that heavy ... if so, can anyone recommend a lighter alternative? 
(The other services running are lightly-used MySQL, lightly-used Apache, 
and a Tor node.)

Or perhaps other processes on the VM's host (general desktop use, or the 
WInXP VM) are just starving it of CPU for long periods?  If so, how can 
I guarantee it at least a certain percentage of overall CPU time?

-------- Original Message --------
Subject: 	** PROBLEM Service Alert: Compaq Presario 5000 [***] in 
basement/Current Load is CRITICAL **
Date: 	Wed, 20 Aug 2014 06:29:36 -0400
From: 	nagios at lmert.com
To: 	root at localhost



***** Nagios *****

Notification Type: PROBLEM

Service: Current Load
Host: Compaq Presario 5000 [***] in basement
Address: 192.168.[XX.XX]
State: CRITICAL

Date/Time: Wed Aug 20 06:29:29 EDT 2014

Additional Info:

CRITICAL - Plugin timed out after 10 seconds