[checkmk-commits] gitbugs

Module: check_mk Branch: master Commit: b04fbb3ff02cb0daaee34e4700ee5ceddd3d98cd URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=b04fbb3ff02cb0… Author: Sebastian Herbord <sh(a)mathias-kettner.de> Date: Thu Feb 11 15:02:02 2016 +0100 gitbugs --- .bugs/2177 | 7 +++++-- .bugs/2400 | 7 +++++-- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/.bugs/2177 b/.bugs/2177 index e43860c..558356f 100644 --- a/.bugs/2177 +++ b/.bugs/2177 @@ -1,9 +1,12 @@ Title: new windows agent: eventlog monitoring should be able to process cleared logfiles Component: checks -State: open +Class: bug +State: closed Date: 2015-07-30 16:04:54 Targetversion: 1.2.8 -Class: bug If someone clears the event log with the event viewer, the windows agent is unable to start from event log record 0. It insists to continue at 51212, for example. + +2016-02-11 15:01:36: changed state open -> closed +This report is invalid? Clearing the event log does not reset the event id counter. If your newest record has it 42 and you clear the event console, the next record will still have the id 43. Seeking in the event log is based on that record id so clearing the event log has no effect except that check_mk may miss cleared events it hadn't read yet. diff --git a/.bugs/2400 b/.bugs/2400 index e0021d1..0682410 100644 --- a/.bugs/2400 +++ b/.bugs/2400 @@ -1,11 +1,14 @@ Title: Windows Agent may fail to read large event logs Component: checks -State: open +Class: bug +State: done Date: 2015-11-06 11:48:19 Targetversion: 1.2.8 -Class: bug Due to a bug in the ReadEventLog function (kb 177199) reading large event logs may fail. This could be worked around in the agent by using sequential read and a manual seek to the right offset but we'd have to check the performance implications. + +2016-02-11 14:57:03: changed state open -> done +EventLog code was overhauled and should fall back to sequential reading of event logs if necessary. Unfortunately wasn't possible to reproduce this problem internally.