[hobbit] Service Results not updating completely with status changes

Shea, Graeme A Shea.Graeme.A at edumail.vic.gov.au
Mon May 12 05:17:26 CEST 2008


Hi Matthew,
Everything is ok. I have been a little slack with the last time sheet
and will get to it. I'm on secondment to another project in DEECD that
requires separate billing. That has another week and a half to go and
I'll send that time sheet then.

Regards
Graeme

-----Original Message-----
From: Matthew.Roberts at nt.gov.au [mailto:Matthew.Roberts at nt.gov.au] 
Sent: Monday, 12 May 2008 12:11 PM
To: hobbit at hswn.dk
Subject: [hobbit] Service Results not updating completely with status
changes


Hello Again,

I have found another problem with monitoring Services using the BBWin
client
with the Hobbit server.

Say for example I am monitoring the DNS service and everything is ok.
The svcs
page for that host will display something similar to:

      Mon May 12 10:55:04 2008 - Services OK
            DNS is automatic started req automatic started

      Name                                StartupType  Status
      DisplayName
      DNS                                 automatic    started
DNS Server


However if the status of the monitored Service changes to stopped, then
an alert
is generated and the page turns red, however the result of the test
displayed on
the svcs page does not change it stays as:

      Mon May 12 10:57:04 2008 - Services NOT ok
            DNS is automatic started req automatic started

Even though the data sent by the BBWin client has changed to

      Name                                StartupType  Status
      DisplayName
      DNS                                 automatic    stopped       DNS
Server

When it should reflect this instead:

      Mon May 12 10:57:04 2008 - Services NOT ok
            DNS is automatic stopped req automatic started

So that we can quickly determine why Services are NOT ok.

I indentifed the reason this does not happen is because the string
variable
which contains this information is set on startup of the Hobbit and the
section
which generates the result does not get run again until the daemon is
restarted
due to the the statement on line 2077 and 2078 of
hobbitd/client_config.c

      result = (*walk)->rule->statustext;
                if (!result) {

By commenting the result = (*walk)->rule->statustext; line, I was able
to force
the result to update when BBDisplay runs at its regular intervals.
Before I
implement this change within our production environment, is there a
specific
reason why the result variable does not get updated at every BBDisplay
update?
Or was this line put in specifically to address some kind of performance
issue?

I am not a C programmer and relatively new to the workings of Hobbit so
any
comment would be greatly appreciated.

Regards,

Matthew Roberts
Senior Systems Administrator - Windows



To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk



Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.



More information about the Xymon mailing list