Activity log for bug #752172

Date Who What changed Old value New value Message
2011-04-06 03:45:50 dusanv bug added bug
2011-04-07 13:16:01 James Page logwatch (Ubuntu): status New Confirmed
2011-04-07 13:16:04 James Page logwatch (Ubuntu): importance Undecided Low
2011-04-07 13:16:10 James Page bug added subscriber James Page
2012-10-02 14:33:35 Thomas Hood tags lucid natty precise quantal
2012-10-02 14:35:46 Thomas Hood summary Ubutu-specific afpd configuration missing Logwatch looks for afpd output in "messages", not in log files that afpd writes to
2013-05-16 16:37:06 Craig bug added subscriber Craig
2013-05-17 14:59:53 Robie Basak marked as duplicate 794727
2018-09-13 18:53:39 Karl Stenerud removed duplicate marker 794727
2018-09-13 18:53:48 Karl Stenerud logwatch (Ubuntu): assignee Karl Stenerud (kstenerud)
2018-09-14 14:44:16 Karl Stenerud description Binary package hint: logwatch This on Ubuntu 10.04.2 LTS, logwatch version 7.3.6.cvs20090906-1ubuntu2.1. The default logwatch configuration expects to find afpd log messages in the 'messages' log file (as per /usr/share/logwatch/default.conf/services/afpd.conf). afpd is logging to 'syslog', 'daemon' and 'auth' log files on Ubuntu so a Ubuntu-specific afpd configuration file should be present (/usr/share/logwatch/dist.conf/services/afpd.conf). That file should list the correct log files. Here's an example: Title = "afpd" LogFile = syslog LogFile = daemon LogFile = auth *OnlyService = afpd *RemoveHeaders [Impact] Since the changeover to rsyslogd, logwatch has been looking in the wrong places for the logfiles it's supposed to monitor. Logs that used to go to /var/log/daemon.log, /var/log/cron.log, and /var/log/messages, are now being logged to /var/log/syslog. This commit changes configurations in dist.conf/logfiles/ to point to /var/log/syslog. [Test Case] # lxc launch ubuntu-daily:cosmic tester # lxc exec tester bash # dhclient # apt update # apt dist-upgrade -y # apt install -y logwatch # echo "Sep 12 01:41:51 xxxxx named[838]: received control channel command 'refresh example.com' Sep 12 03:34:10 xxxxx smartd[30161]: Monitoring 4 ATA and 0 SCSI devices Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 463 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 1210 Offline uncorrectable sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1430 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1429 Offline uncorrectable sectors Sep 12 09:00:00 xxxxx afpd[2383]: login noauth" > /var/log/syslog # logwatch --detail medium --range all --service named # logwatch --detail medium --range all --service smartd # logwatch --detail medium --range all --service afpd * None of these commands will display anything. [Regression Potential] This has been broken since at least 2011. Logwatch currently doesn't report anything that isn't already pointing to syslog, so there should be no regression potential. [Original Description] Binary package hint: logwatch This on Ubuntu 10.04.2 LTS, logwatch version 7.3.6.cvs20090906-1ubuntu2.1. The default logwatch configuration expects to find afpd log messages in the 'messages' log file (as per /usr/share/logwatch/default.conf/services/afpd.conf). afpd is logging to 'syslog', 'daemon' and 'auth' log files on Ubuntu so a Ubuntu-specific afpd configuration file should be present (/usr/share/logwatch/dist.conf/services/afpd.conf). That file should list the correct log files. Here's an example: Title = "afpd" LogFile = syslog LogFile = daemon LogFile = auth *OnlyService = afpd *RemoveHeaders
2018-09-14 14:44:39 Karl Stenerud logwatch (Ubuntu): status Confirmed In Progress
2018-09-14 14:47:10 Karl Stenerud description [Impact] Since the changeover to rsyslogd, logwatch has been looking in the wrong places for the logfiles it's supposed to monitor. Logs that used to go to /var/log/daemon.log, /var/log/cron.log, and /var/log/messages, are now being logged to /var/log/syslog. This commit changes configurations in dist.conf/logfiles/ to point to /var/log/syslog. [Test Case] # lxc launch ubuntu-daily:cosmic tester # lxc exec tester bash # dhclient # apt update # apt dist-upgrade -y # apt install -y logwatch # echo "Sep 12 01:41:51 xxxxx named[838]: received control channel command 'refresh example.com' Sep 12 03:34:10 xxxxx smartd[30161]: Monitoring 4 ATA and 0 SCSI devices Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 463 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 1210 Offline uncorrectable sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1430 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1429 Offline uncorrectable sectors Sep 12 09:00:00 xxxxx afpd[2383]: login noauth" > /var/log/syslog # logwatch --detail medium --range all --service named # logwatch --detail medium --range all --service smartd # logwatch --detail medium --range all --service afpd * None of these commands will display anything. [Regression Potential] This has been broken since at least 2011. Logwatch currently doesn't report anything that isn't already pointing to syslog, so there should be no regression potential. [Original Description] Binary package hint: logwatch This on Ubuntu 10.04.2 LTS, logwatch version 7.3.6.cvs20090906-1ubuntu2.1. The default logwatch configuration expects to find afpd log messages in the 'messages' log file (as per /usr/share/logwatch/default.conf/services/afpd.conf). afpd is logging to 'syslog', 'daemon' and 'auth' log files on Ubuntu so a Ubuntu-specific afpd configuration file should be present (/usr/share/logwatch/dist.conf/services/afpd.conf). That file should list the correct log files. Here's an example: Title = "afpd" LogFile = syslog LogFile = daemon LogFile = auth *OnlyService = afpd *RemoveHeaders [Impact] Since the changeover to rsyslogd, logwatch has been looking in the wrong places for the logfiles it's supposed to monitor. Logs that used to go to /var/log/daemon.log, /var/log/cron.log, and /var/log/messages, are now being logged to /var/log/syslog. This commit changes configurations in dist.conf/logfiles/ to point to /var/log/syslog. [Test Case] # lxc launch ubuntu-daily:cosmic tester # lxc exec tester bash # dhclient # apt update # apt dist-upgrade -y # apt install -y logwatch # echo "Sep 12 01:41:51 xxxxx named[838]: received control channel command 'refresh example.com' Sep 12 03:34:10 xxxxx smartd[30161]: Monitoring 4 ATA and 0 SCSI devices Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 463 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdc, 1210 Offline uncorrectable sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1430 Currently unreadable (pending) sectors Sep 12 03:34:11 xxxxx smartd[30161]: Device: /dev/hdd, 1429 Offline uncorrectable sectors Sep 12 09:00:00 xxxxx afpd[2383]: login noauth" >> /var/log/syslog # logwatch --detail medium --range all --service named # logwatch --detail medium --range all --service smartd # logwatch --detail medium --range all --service afpd * None of these commands will display anything. [Regression Potential] This has been broken since at least 2011. Logwatch currently doesn't report anything that isn't already pointing to syslog, so there should be no regression potential. [Original Description] Binary package hint: logwatch This on Ubuntu 10.04.2 LTS, logwatch version 7.3.6.cvs20090906-1ubuntu2.1. The default logwatch configuration expects to find afpd log messages in the 'messages' log file (as per /usr/share/logwatch/default.conf/services/afpd.conf). afpd is logging to 'syslog', 'daemon' and 'auth' log files on Ubuntu so a Ubuntu-specific afpd configuration file should be present (/usr/share/logwatch/dist.conf/services/afpd.conf). That file should list the correct log files. Here's an example: Title = "afpd" LogFile = syslog LogFile = daemon LogFile = auth *OnlyService = afpd *RemoveHeaders
2018-12-10 11:19:06 Launchpad Janitor merge proposal linked https://code.launchpad.net/~kstenerud/ubuntu/+source/logwatch/+git/logwatch/+merge/354951
2020-08-03 19:18:51 Bryce Harrington logwatch (Ubuntu): assignee Karl Stenerud (kstenerud)
2020-08-03 19:18:57 Bryce Harrington logwatch (Ubuntu): status In Progress Triaged
2020-08-04 14:33:05 Lucas Kanashiro bug added subscriber Ubuntu Server
2022-06-03 19:13:48 Bryce Harrington marked as duplicate 794727