I updated 2 of 3 hobbits now to 4.0.2 and didn't get any errors. But I though one problem of 4.0.1 has been resolved. I got an alarm this night from the sensor procs of one host. After 5 minutes, the problem was solved. I also got a message about that. This morning I looked at the history and can't find the entry. After looking into the logfile from sensor, I found the entry, but bb-hist.sh don't show me this color-change. Here the part in the hist-file: ---snip--- Fri Jan 14 15:06:36 2005 green 1105711596 Tue Apr 5 16:02:32 2005 green 1112709752 16501 Tue Apr 5 20:37:33 2005 red 1112726253 301 Tue Apr 5 20:42:34 2005 green 1112726554 15646 Wed Apr 6 01:03:20 2005 purple 1112742200 24126 Wed Apr 6 07:45:26 2005 clear 1112766326 227 Wed Apr 6 07:49:13 2005 red 1112766553 295 Wed Apr 6 07:54:08 2005 green 1112766848 25803 Wed Apr 6 15:04:11 2005 red 1112792651 1201 Wed Apr 6 15:24:12 2005 green 1112793852 372952 Sun Apr 10 23:00:04 2005 red 1113166804 300 Sun Apr 10 23:05:04 2005 green 1113167104 14101 Mon Apr 11 03:00:05 2005 red 1113181205 300 Mon Apr 11 03:05:05 2005 green 1113181505 ---snap---
There are also entries in the histlogs, but bb-hist.sh shows me the following entry: ---snip--- Fri Jan 14 15:06:36 2005 green 86 days 19:12:47 ---snap--- The color also shows me a recent green.
I got the problem on 4.0.1 and 4.0.2.
Regards, Thomas
On Mon, Apr 11, 2005 at 11:23:56AM +0200, Thomas Ruecker wrote:
I updated 2 of 3 hobbits now to 4.0.2 and didn't get any errors. But I though one problem of 4.0.1 has been resolved. I got an alarm this night from the sensor procs of one host. After 5 minutes, the problem was solved. I also got a message about that. This morning I looked at the history and can't find the entry. After looking into the logfile from sensor, I found the entry, but bb-hist.sh don't show me this color-change. Here the part in the hist-file: ---snip--- Fri Jan 14 15:06:36 2005 green 1105711596 Tue Apr 5 16:02:32 2005 green 1112709752 16501 Tue Apr 5 20:37:33 2005 red 1112726253 301
The first log-entry is invalid - there's no duration field on it. If you change it to
Fri Jan 14 15:06:36 2005 green 1105711596 6998156
does that fix the history display ? (The 6998156 is simply the difference between th Jan 14 timestamp and the Apr 5 16:02 timestamp).
I vaguely recall this being discussed on the BB list a while back. I'll have a look through the archives, and also look at making the history log viewer more lenient towards this kind of error in the logfile - now you've provided a nice testcase.
Regards, Henrik
The first log-entry is invalid - there's no duration field on it. If you change it to
Fri Jan 14 15:06:36 2005 green 1105711596 6998156
does that fix the history display ? (The 6998156 is simply the difference between th Jan 14 timestamp and the Apr 5 16:02 timestamp). I will try it tomorrow, because I'm out of office today and give you some feedback.
I vaguely recall this being discussed on the BB list a while back. I'll have a look through the archives, and also look at making the history log viewer more lenient towards this kind of error in the logfile - now you've provided a nice testcase. I can give you more logfiles with this problem. I think all my logfiles have this problem. I upgrage from BB to Hobbit like the docs describe. Maybe you can write a script like the one for the RRDs to make a clean copy of all logfiles.
Thomas
The first log-entry is invalid - there's no duration field on it. If you change it to
Fri Jan 14 15:06:36 2005 green 1105711596 6998156
does that fix the history display ? (The 6998156 is simply the difference between th Jan 14 timestamp and the Apr 5 16:02 timestamp).
I will try it tomorrow, because I'm out of office today and give you some feedback. I deleted the line without the duration and now it works. But I don't have an idea, how to do this with a script on all logfiles. Anyone with an short-script, that deletes a line file where are only 3 columns and not 4?
Thomas
On Thu, 14 Apr 2005 10:09:25 +0200 Thomas Ruecker <truecker at technologie-management.net> wrote:
The first log-entry is invalid - there's no duration field on it. If you change it to
Fri Jan 14 15:06:36 2005 green 1105711596 6998156
does that fix the history display ? (The 6998156 is simply the difference between th Jan 14 timestamp and the Apr 5 16:02 timestamp).
I will try it tomorrow, because I'm out of office today and give you some feedback. I deleted the line without the duration and now it works. But I don't have an idea, how to do this with a script on all logfiles. Anyone with an short-script, that deletes a line file where are only 3 columns and not 4?
Thomas,
There're probably hundreds of ways to do it.
With egrep on command line or in a shell script it could be done by:egrep "200[0-5][[:space:]]+[a-z]+[[:space:]]+[0-9]+[[:space:]]+[0-9]+[[:space:]]?+$" log_file >new_logfile
You can be less stricter, matching only "<number><space?s><number>", or use sed, awk...
Hope it help's.-wm
participants (4)
-
henrik＠hswn.dk
-
mls＠fl-base.de
-
truecker＠technologie-management.net
-
wmlist_ext＠terra.com.br