BB Unix Network Monitor - Message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

{bb} Weird Procs results



Title: Weird Procs results

Hi,

I'm seeing a strange behavior from one of my servers and wanted to check if you folks had any ideas.

I am running BB Pro 3.10 on a Red hat server and Red Hat client.  I am using bb-proc.sh to check the status of running processes on the client machine.

What I'm seeing looks like a strange double effort.  When the monitored processes are running, the status page reports the following:

 green /usr/local/apache2/bin/httpd -k start MIN=1 (6 instances)   Status: UP
 
green /usr/local/[proprietary_app_1] MIN=4 (4 instances)             Status: UP
 
green /usr/local/[proprietary_app_2] MIN=4 (4 instances)       Status: UP
 
green /usr/local/mysql/bin/mysqld MIN=1 (4 instances)             Status: UP

But I still get paged.  When I look at the history, there are two entries every 5 minutes - just before the one above, this appears:

 red MIN=1 >=1 - not running, requires at least 1
 
red MIN=4 >=1 - not running, requires at least 1
 
red MIN=4 >=1 - not running, requires at least 1
 
red MIN=1 >=1 - not running, requires at least 1
 
red -k >=1 - not running, requires at least 1
 
green /usr/local/mysql/bin/mysqld >=1 - 4 instances running
 
green /usr/local/[proprietary_app_1] >=1 - 4 instances running
 
green /usr/local/[proprietary_app_2] >=1 - 4 instances running
 
green start >=1 - 9 instances running
 
green /usr/local/apache2/bin/httpd >=1 - 6 instances running

There is only 2-3 seconds of the "bad" status, then the correct one comes back.  This happens every time BB builds new pages (5 minutes).  The bb-proctab file on the client looks like this:

Host.any.com : : /usr/local/[proprietary_app_1] MIN=4
Host.any.com : : /usr/local/[proprietary_app_2] MIN=4
Host.any.com : : /usr/local/apache2/bin/httpd -k start MIN=1
Host.any.com : : /usr/local/mysql/bin/mysqld MIN=1

I have deleted the client-specific data from bbvar/logs, hist, and histlogs but still get the same results.  I have tried using the FQDN and "localhost" in bb-proctab, and get the same result.  Both the client and the BB server have been rebooted, just to make sure nothing got cached.

Where else might I find where the problem is?  I'm sure this info is just stored somewhere I haven't looked, but I haven't been able to track it down.

Thanks for your help,
Scott

-------------------------------
Scott McGillivray
Network Engineer
Encounter Collaborative
Office: (503) 295-6511
Cell: (503) 453-2953
scott@encounter.net

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Home | Main Index | Thread Index