Description of problem: The httpd *error_log files don't use the same date format as the *access_log files, so it doesn't find anything. Removing "*ApplyhttpDate" from conf/logfiles/http-error.conf fixes it.
Actually, we probably want a custom date filter for this format: [Sun Nov 25 03:44:01 2012] Although it at least find items from the right date.
Indeed, removing "*ApplyhttpDate" from conf/logfiles/http-error.conf fixes this misbehavior. I just ran into some serious problems while testing this. The 'fix' works only with httpd 2.2. In 2.4, http-error doesn't work at all due to a different log format. The second problem is that the output log format can be heavily configured (mod_log_config), which kind of negates the whole purpose of the http-error script. It would probably make sense to fix this / support the default log and disregard anything else. If you want this to be really configurable, an RFE for a configurable regexp will be a way to go.
Pushed: http://lists.fedoraproject.org/pipermail/scm-commits/2012-December/909867.html
logwatch-7.4.0-19.20120619svn110.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/logwatch-7.4.0-19.20120619svn110.fc18
logwatch-7.4.0-19.20120619svn110.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/logwatch-7.4.0-19.20120619svn110.fc17
Package logwatch-7.4.0-19.20120619svn110.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing logwatch-7.4.0-19.20120619svn110.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19730/logwatch-7.4.0-19.20120619svn110.fc17 then log in and leave karma (feedback).
logwatch-7.4.0-19.20120619svn110.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
logwatch-7.4.0-19.20120619svn110.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.