Warning. Bad log file record found in file - corrupt logs?

[William]

Hi,

looking at the output from omshowlog, there seems to be always some bad log lines at the begining of the output, for example:

Code: Select all

# omshowlog -F 00:00 -l 1
Warning.  Bad log file record found in file 1 at 0x000c6df3,
          skipped 525 bytes to next record.
Warning.  Bad log file record found in file 1 at 0x000daf56,
          skipped 170 bytes to next record.
Warning.  Bad log file record found in file 1 at 0x000dbf3b,
          skipped 197 bytes to next record.
Warning.  Bad log file record found in file 1 at 0x000dcfd9,
          skipped 39 bytes to next record.
[OM 4884] omshowlog : No logged records match the specified criteria


is there a solution to this?

[mikethebike]

William,

I think the next time you have scalix down, you could remove the logfiles and start again.

Stop scalix
fuser ~logs/log.*

the actual files that omshowlog uses (and the event logs write to...omconflvl, omshowlvl) are log.0, log.1 and log.2....they roll over at a size specified by "omconflvl -s"

if there are no pids accessing the logfiles, either rename them, or delete them.

Start scalix and the logfiles will be recreated.

Mick

[William]

seems the files are not really in constant use so I did not need to do anything apart from rename the files and to a touch log.0 touch log.1 touch log.2 to reset the logs.