On Fri, 26 Apr 2002, Nguyen Thi Le Chau wrote:
> Why this kind of warning and can I safely ignore it ?
>
> polyclt.1019749427.log:718388: warning: skipping corrupted entry
> (log time: 1019754148.008810)
This means that the log contains an entry that does not make any sense
to the log reader. For example, internal entry type is unknown or
entry size is negative or way too big. Polygraph tries to skip such
entries by scanning for the next sequence of logged bytes that looks
like a valid entry. Sometimes Polygraph succeeds without visible
effects on log interpretations; sometimes not, depending on what area
of the log got corrupted.
There are three possible reasons for corruption: incomplete log file
(caused either by abrupt polyclt/polysrv process death or by errors
during file transfers, if any), corrupted log file (due to operating
system bugs when writing large files under heavy load), and yet
unknown internal Polygraph bugs.
If your test terminated prematurely, you should not be surprised by
the warning.
If the log file was copied from another machine, it is a good idea to
verify that the copy matches the original. Running md5 against both
files is the best way to do that.
If the log file was not copied or if it matches the original, there is
little you can do about the warning. You can only hope that no crucial
data was skipped.
Alex.
Received on Fri Apr 26 2002 - 11:20:20 MDT
This archive was generated by hypermail 2.2.0 : Thu Nov 20 2008 - 12:00:07 MST