Alex,
I found some odd behaviour..
I'm using HM 4.87, W2K3, fully patched
for some unknown reason, some of the test have a double logging :
28/11/2004 00:00:19 Ok 11748432,59
28/11/2004 11:54:24 Ok 11834833,48
29/11/2004 11:54:25 Ok 11921233,94
30/11/2004 11:54:26 Bad 81297,60
01/12/2004 00:00:46 Bad 81297,60
01/12/2004 11:54:26 Ok 167697,99
02/12/2004 11:54:27 Ok 254098,99
30/11/2004 03:31:29 Ok 1922 ms
30/11/2004 11:31:31 Ok 1453 ms
30/11/2004 19:31:31 Ok 672 ms
01/12/2004 00:00:49 Ok 672 ms
01/12/2004 03:31:34 Ok 1922 ms
01/12/2004 11:31:36 Ok 1688 ms
It always happens at 00:00:something...
I saw a previous (old) post that had the some issue :
http://www.ks-soft.net/cgi-bin/phpBB/vi ... .php?t=404
I see 2 options
- The extra (unnecessary) log is done when the HM service is restarted (due to upgrade). BUT I never upgraded at 00:00
- There is a bug in the systems that performes an extra log for some reason (change of month ?)
Please advise
Pieter
-
Test executed at midnight without reason
-
plambrecht
- Posts: 151
- Joined: Wed May 19, 2004 8:11 am
- Location: Belgium
- Contact:
There is 3rd option. I assume you have configured HM to change log file on regular basis, e.g. monthly. Right?
When HostMonitor creates new log it records information about all test items (without performing all these test, just saves information about current status). This is very useful for log analyzing because some (most of?) tests do not change status often.
Regards
Alex
When HostMonitor creates new log it records information about all test items (without performing all these test, just saves information about current status). This is very useful for log analyzing because some (most of?) tests do not change status often.
Regards
Alex
-
plambrecht
- Posts: 151
- Joined: Wed May 19, 2004 8:11 am
- Location: Belgium
- Contact:
I looked into it, and it is indeed everytime the logfile changes to a new one, that there is an extra entry.
I'm ok with the fact that the you re-log in a new file, but it also logs a new entry in my advanced ODBC logging...
that is something I don't like....
It gives fals results in my reporting system..
for ex, I check the uptime of servers, and when the uptime is less then the previous one, i log an entry that the the machine rebooted..
With the current system, I have the BAD entry twice in my sql database, and the report shows 2 reboots...
a little checkbox that would control this behaviour, would be nice
Pieter
I'm ok with the fact that the you re-log in a new file, but it also logs a new entry in my advanced ODBC logging...
that is something I don't like....
It gives fals results in my reporting system..
for ex, I check the uptime of servers, and when the uptime is less then the previous one, i log an entry that the the machine rebooted..
With the current system, I have the BAD entry twice in my sql database, and the report shows 2 reboots...
a little checkbox that would control this behaviour, would be nice
Pieter
Ok, there is update at www.ks-soft.net/download/hm494.zip
When HM creates new log it records info about all tests into regular log but does not record this info into ODBC log.
This is "unofficial" update, means there are some undocumented modifications. It was tested and seems to be working fine but it was not tested much. So, better if you keep your eyes on it for a while.
Regards
Alex
When HM creates new log it records info about all tests into regular log but does not record this info into ODBC log.
This is "unofficial" update, means there are some undocumented modifications. It was tested and seems to be working fine but it was not tested much. So, better if you keep your eyes on it for a while.
Regards
Alex