MailScanner & Zenoss

[UxBoD]

Steve,

The problem is that even though Zenoss can use regex and detect all instances of MailScanner running, but even with the parent process changing its description line it can sometimes see it as a failure.  Basically what it is doing is grabbing the process list from the SNMP tree.

May have to write a zenoss script to do it, which is a pain, as clamd, postfix etc are all okay.  Perhaps if MailScanner kept its parent process static with respect to the name ie. MailScanner and the child processes can report their own state.

I would imagine that this could also occur on other monitoring systems IMHO.

Regards,

--[ UxBoD ]--
// PGP Key: "curl -s https://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: C759 8F52 1D17 B3C5 5854  36BD 1FB1 B02F 5DB5 687B
// Keyserver: www.keyserver.net Key-ID: 0x5DB5687B
// Phone: +44 845 869 2749 SIP Phone: uxbod at sip.splatnix.net

----- Original Message -----
From: "Steve Freegard" <steve.freegard at fsl.com>
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Sent: Monday, September 24, 2007 3:23:03 PM (GMT) Europe/London
Subject: Re: MailScanner & Zenoss

UxBoD wrote:
> Hi,
> 
> Is anybody using Zenoss to monitor MailScanner ? The issue I am having is that due to MailScanner showing its current state on the process line ie. Checking with SpamAssassin, Waiting for Messages there is no one process line to check and ensure MailScanner is running.
> 
> Any ideas ?

How about:

[root at mail soaplite]# ps axf | grep `cat /var/run/MailScanner.pid` | 
grep -v grep
   889 ?        Ss     0:00 MailScanner: master waiting for children, 
sleeping

Cheers,
Steve.
-- 
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website! 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.