unmatched entries for rsyslogd

Bug #1583706 reported by Jared Fernandez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
logwatch (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Under the "rsyslogd" heading, the following rsyslog lines appear as unmatched:

**** Unmatched entries ****
   rsyslogd's groupid changed to 103 : 1 Times
   rsyslogd's userid changed to 101 : 1 Times
   [origin software="rsyslogd" swVersion="8.16.0" x-pid="1859" x-info="http://www.rsyslog.com"] exiting on signal 15. : 1 Times
   message repeated 10 times: [ [origin software="rsyslogd" swVersion="8.16.0" x-pid="1859" x-info="http://www.rsyslog.com"] rsyslogd was HUPed] : 1 Times

-----------------------------------------------------------------
Description: Ubuntu 16.04 LTS
Release: 16.04

logwatch:
  Installed: 7.4.2-1ubuntu1
  Candidate: 7.4.2-1ubuntu1
  Version table:
 *** 7.4.2-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

rsyslog:
  Installed: 8.16.0-1ubuntu3
  Candidate: 8.16.0-1ubuntu3
  Version table:
 *** 8.16.0-1ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

Robie Basak (racb)
tags: added: bitesize
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you already for taking the time to report this bug and helping to make Ubuntu better.

It is really great that you identified and split up all these issues, but given that up to now neither Debian nor Ubuntu add tremendous functional delta to the upstream logwatch content I think the right way to address is to file them upstream (https://sourceforge.net/p/logwatch/bugs/).

Despite on sourceforge they seem to be still active there - Debian as well as Ubuntu can eventually pick it up on the next merge then.

If you are so kind and file them upstream it would be great if you drop us a note here or even link the upstream bug via "also affects project" above in Launchpad.

Revision history for this message
Nish Aravamudan (nacc) wrote :

Fixed upstream: https://sourceforge.net/p/logwatch/git/ci/32adbfdd7f5718d050a5392ed82271b4740c4122/

We could probably take another git snapshot to pick it up, but I think we're better off asking Debian to and then backporting the change.

Revision history for this message
Bryce Harrington (bryce) wrote :

Commits 32adbfdd and 3abbb24d address this issue, and both are included in upstream's 7.5.0 release, which is packaged for and released in Ubuntu disco (19.04). We can consider this fixed now.

Changed in logwatch (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.