[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[hobbit] Potential bugs, BBSERVERLOGS, alert counter
- To: hobbit (at) hswn.dk
- Subject: [hobbit] Potential bugs, BBSERVERLOGS, alert counter
- From: David Gore <David.Gore (at) mci.com>
- Date: Thu, 17 Feb 2005 17:42:44 +0000
- References: <1108661078.4214d356ceda3@www.qalpit.com>
- User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Sorry, about that previous email with the wrong subject line, "Re:
[hobbit] changing hobbit port to 1985".
Potential bugs:
It appears that if you change BBSERVERLOGS to something other than what
you compiled in, Hobbit will fail to listen on port 1984.
But more importantly, is Hobbit suppose to restart the counter for
alerts after you restart it? In other words, when I am looking at the
log file I can clearly see that the counter is reset by watching the
minduration lines in page.log. Perhaps, I have something serious
misconfigured?
2005-02-17 17:20:31 hobbitd_alert: Got message 3331
@@page#3331|1108660831.790898|some.ip.address|nornxs02|IdeasLogQ|some.ip.address|1108662631|red|red|1108654832|NOR/NETeXPERT|628789
2005-02-17 17:20:31 Got page message from nornxs02:IdeasLogQ
2005-02-17 17:20:31 Alert status changed from 0 to 1
2005-02-17 17:20:31 criteriamatch nornxs02:IdeasLogQ (NULL):(NULL):(NULL)
2005-02-17 17:20:31 Checking explicit color setting 10000000040 against
5 gives 1
2005-02-17 17:20:31 Found a first matching rule
2005-02-17 17:20:31 criteriamatch nornxs02:IdeasLogQ (NULL):(NULL):(NULL)
2005-02-17 17:20:31 failed minduration 0<900
The red alarmed at 15:40:32.
~ David Gore
olivier (at) qalpit.com wrote:
hobbit doesnt seem to start another port than 1984
i've do 3 things:
-changed bbd in bb-services
-changed port in hobbitserver.cfg
-and even re-compiled hobbit with PORT 1985 in the makefile
but still doesnt work..
did i forget something ?
--
Olivier Beau
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk