changing hobbit port to 1985
list Olivier Beau
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
list David Gore
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
▸
user-fe6e0e6a0d05@xymon.invalid 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
list David Gore
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
user-fe6e0e6a0d05@xymon.invalid 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
list Henrik Størner
▸
On Thu, Feb 17, 2005 at 06:24:38PM +0100, user-fe6e0e6a0d05@xymon.invalid 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..
It's a bug. Fixed now. Use the --listen option on the hobbitd command to set a different portnumber if you need it now. Henrik
list Henrik Størner
▸
On Thu, Feb 17, 2005 at 05:42:44PM +0000, David Gore wrote:
It appears that if you change BBSERVERLOGS to something other than what you compiled in, Hobbit will fail to listen on port 1984.
Do you mean that it fails to start completely, or just that it doesn't log the "Setting up network listener on 0.0.0.0:1984" message ? If the latter, then note that this message is logged in the hobbitlaunch log-file (it's a bit messy, but hobbitd sets up the listener port before handling any options about where to log stuff). And the hobbitlaunch logfile is determined by a commandline option in starthobbit.sh
▸
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?
The duration counter does reset if Hobbit is restarted, at least with the default setup. You can change this by having hobbitd_alert save the state of the active alerts in a file when it shuts down, and restore the state when it starts up again. The "--checkpoint-file=FILENAME" option for hobbitd_alert will do that. The reason why this is not enabled by default is that you can get into a situation where an alert is active when you shut down Hobbit, but it's been resolved when Hobbit starts up again. At least until beta-6, hobbitd_alert would then keep on sending out alerts for a test that had gone green while Hobbit was off-line, so I turned this checkpoint option off - which means that after a restart you may get some alerts that would not appear had Hobbit not been restarted. But thinking about the changes in how alerts are managed, I believe it is safe to turn this back on. So if you like, you can try adding "--checkpoint-file=$BBTMP/alerts.chk" to the hobbitd_alert command in hobbitlaunch.cfg . Regards, Henrik