false positive in logwatch report

[latimerio]

 I always get the following false positives reported from dmesg.

  ERST: Error Record Serializa ...: 2 Time(s)
  EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro ...: 2 Time(s)

Both messages are obviously not errors.

It seems that logwatch is just looking for words like "error" and there is no exclusion filter for false positives.

[latimerio (fomember)]

To my understanding it is normal behaviour that during boot the root filesystem is first mounted ro and after it has passed some checks it gets remounted.
Logwatch seems to just to check the fstab line in the log file, see the error option and report it as a false positive.
It is a false positive because the line says "in case of an error, remount as ro" but the file system in fact gets remounted as rw after it was initially mounted as ro.
So the line from fstab appears in the dmesg log and logwatch unfortunately just seems to trigger on the word error.
The same thing happens with the entry "ERST: Error Record Serializa" which gets me a logwatch error after every boot.
I hope that future versions of logwatch will have an option to filter those false positives which are a real nag to me.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robie Basak (racb)]

I merged 7.4.1-2ubuntu1 yesterday. Based on Debian's changelog, it looks like this bug is fixed now in the latest development release. If not, please reopen.