I recently updated 3 servers to logwatch-7.3-r1 when it was marked stable, at which point I stopped receiving logwatches, and started receiving e-mails with the subject "Cron <root@hostname> test -x /usr/sbin/run-crons && /usr/sbin/run-crons", and the text "No mail for root". I tracked this down to logwatch simply calling the /bin/mail program with no arguments, i.e. not giving it a destination address etc. I tested on one box rolling back to logwatch-7.1 and the problem disappeared. I've included an output from manually running /usr/sbin/logwatch --debug=high below, I couldn't figure out from that what was going wrong... Reproducible: Always Steps to Reproduce: 1. Update (with emerge -u) to logwatch-7.3-r1 from logwtach-7.1 2. Run /usr/sbin/logwatch Actual Results: Received the message "No mail for root" on STDERR Expected Results: An e-mail to be sent to the address specified in /etc/logwatch/conf/logwatch.conf containing a report on the days log
Created attachment 106600 [details] STDOUT from running logwatch --debug=high E-mail address removed to protect the innocent
Created attachment 106602 [details] STDERR from running logwatch --debug=high
Exact same problem here on two machines, same version of logwatch.
The solution here was to replace the line: mailer = /bin/mail in /etc/logwatch/conf/logwatch.conf with the following: mailer = /usr/sbin/sendmail -t
(In reply to comment #4) > The solution here was to replace the line: > > mailer = /bin/mail > > in /etc/logwatch/conf/logwatch.conf with the following: > > mailer = /usr/sbin/sendmail -t > This has fixed it for me as well, I guess it might be worth someone putting something in the ebuild to mention this as part of the emerge process so that other people can find out?
this is now 3 years ago ... i guess we don't need to put a message in it anymore ...
