BB Unix Network Monitor - Message

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

Re: {bb} Email notification mysterious problem



If I'm not mistaken, you want 180~10. ~180 is an initial delay of 180 minutes. I would think you'd want them in order, ~10 180, but I don't know the syntax for separating them here.

Take a look at the docs, but I think that's your problem.

Artur Shnayder wrote:

Philip,
Please see my $BBHOME/etc/bbwarnsetup.cfg and $BBHOME/etc/bbwarnrules.cfg files below:


------------- bbwarnsetup.cfg -----------------
bbwarn: TRUE
svcerrlist: disk:100 cpu:200 procs:300 msgs:400 conn:500 http:600 dns:800 ERR:999
trapcodes: disk:2 cpu:4 procs:6 msgs:8 conn:10 http:12 dns:14 dig:14 ftp:16 smtp:18 fping:20 imap:22 mq:24 mrtg:26 nntp:28 pop3:30 pop-3:30 ssh:32 swap:34 telnet:36 ERR:0
entoid: .1.3.6.1.4.1.7058
snmptrap_pgm: /usr/bin/snmptrap
snmptrap_type: UCD
ignforall:
pagehelpcode: 911
ttyline: /dev/cuaa0
prefix: T9
suffix:
pagedelay: 15
pagelevels: red purple
pagelevelsmail: yellow
pagerecovered: TRUE
pagetype: EVENT
pagemaster: root@localhost
pageaddhtmlpath: TRUE
cfgdelim: ;
briefrcpt:
-----------end--------------



------------bbwarnrules.cfg -------- *;;*;;*;*;<admin email>:10~180 notify-admin;;pagehelp;;*;*;<admin email> unmatched-*;;*;;*;*;<admin-email> ----------end----------------------

I would like BB wait for 10 min and then send emails every 3 hours. I used to play with bbwarnrules.cfg file with no success.


Thank you very much, Artur


----- Original Message ----- From: "Philip Clark" <bblist@cannae.uklinux.net>
To: <bb@bb4.com>
Sent: Wednesday, February 01, 2006 7:45 PM
Subject: Re: {bb} Email notification mysterious problem



On Wed, 2006-02-01 at 22:24, Artur Shnayder wrote:

I run bb1.9i on rhe3 and email notification doesn't work. All
configuration files seem to be all right and np_.. files are being created
under $BBHOME/tmp directory, but they have wrong timestamp.
"ls -l $BBHOME/tmp" command returns the following:


-rw-rw-r--    1 bb       bb             60 Feb  1 16:26 BB
-rw-rw-r--    1 bb       bb              0 Jan 30 12:41 BB.9233
-rw-rw-r--    1 bb       bb             19 Feb  1 16:06 BBPID
-rw-rw-r--    1 bb       bb             69 Feb  1  2006
np_alert@<email.com>_<hostname>.procs

Timestamp of the np_.. file is broken, however "ls -l --time atime"
produces:

-rw-rw-r--    1 bb       bb             60 Feb  1 16:16 BB
-rw-rw-r--    1 bb       bb              0 Feb  1 14:41 BB.9233
-rw-rw-r--    1 bb       bb             19 Feb  1 16:05 BBPID
-rw-rw-r--    1 bb       bb             69 Feb  1 15:45
np_alert@<email.com>_<hostname>.procs

Computer's time is synchronized via ntpd.

Any help will be appreciated,


The "np_*" files (like status logs) are created intentionally
with a timestamp in the future. Their purpose is to delay the
start of an alert in response to the rules that you have defined.
Once the timestamp is in the past, paging can start and the file
is be removed.

You should post the rules that you have defined and say what
behaviour you want to configure.

Cheers, Phil.



--
Faith is the quality that enables you to eat blackberry jam on a
picnic without looking to see whether the seeds move.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.


-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, or to subscribe to the bb-digest list send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or- subscribe bb-digest in the BODY of the message.

-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, or to subscribe to the bb-digest list send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or- subscribe bb-digest in the BODY of the message.


Home | Main Index | Thread Index