On Wed, 6 Aug 2014, Rich Shepard wrote:
> Considering that logwatch.pl has run faithfully each day for years I
> suspect that there's something in the upgrade to version 7.4.0 that is at
> the root of the problem.
Found and fixed the problem. When I upgraded postfix-2.11.0 to -2.11.1 I
negle
Rich Shepard wrote:
# The 'Service' option expects either the name of a filter
# (in/usr/share/logwatch/scripts/services/*) or 'All'.
# The default service(s) to report on. This should be left as All for
# most people.
Service = All
# You can also disable certain services (when specifying all)
Se
On Wed, 6 Aug 2014, Eric Wilhelm wrote:
> If you're getting no error output and not the expected results, you might
> look for unchecked exit code on system() or backtick/qx{}. Those bits
> might also be in your strace output. `grep sendmail`?
Eric,
Nice thought. Here's what I find:
$ grep s
# from Rich Shepard on Wednesday 06 August 2014:
> However, ... running 'logwatch.pl --output stdout' does display the
>report on the console, so the problem seems to be back to an issue
>with sendmail rather than logwatch.pl. Yet, a few days ago the
>problem was the opposite: changing logwatch.c
Rich Shepard wrote:
> On Wed, 6 Aug 2014, Dale Snell wrote:
>
>> ENOTTY is an error; one could translate it as "Error: No Terminal". At a
>> guess, logwatch tried to open a device or file as a target to recieve its
>> standard output, and failed. Why, I do not know. It's going to take some
>> more
On Wed, 6 Aug 2014, Michael Rasmussen wrote:
> What are the parameters you normally call logwatch.pl with?
It runs from /etc/cron.daily/0logwatch which is a soft link to
/usr/share/logwatch/scripts/logwatch.pl. The configuration is in
/usr/share/logwatch/default.conf/logwatch.conf:
##
On Wed, Aug 06, 2014 at 11:44:19AM -0700, Rich Shepard wrote:
> On Wed, 6 Aug 2014, Rich Shepard wrote:
>
> > With the debug option nothing indicative of a problem shows up.
>
>However, ... running 'logwatch.pl --output stdout' does display the report
> on the console,
What are the parame
On Wed, 6 Aug 2014, Dale Snell wrote:
> ENOTTY is an error; one could translate it as "Error: No Terminal". At a
> guess, logwatch tried to open a device or file as a target to recieve its
> standard output, and failed. Why, I do not know. It's going to take some
> more troubleshooting, I'm afraid
On Wed, 6 Aug 2014 11:35:27 -0700 (PDT)
Rich Shepard wrote:
> On Wed, 6 Aug 2014, Dale Snell wrote:
>
> > Try running the strace output file through grep, looking for the
> > string "ERR" or "ENO". It's a long shot, but it can't hurt to
> > try.
>
> Dale,
>
>No errors, but some ENOTTY; do
On Wed, 6 Aug 2014, Rich Shepard wrote:
> With the debug option nothing indicative of a problem shows up.
However, ... running 'logwatch.pl --output stdout' does display the report
on the console, so the problem seems to be back to an issue with sendmail
rather than logwatch.pl. Yet, a few d
On Wed, 6 Aug 2014, Dale Snell wrote:
> Try running the strace output file through grep, looking for the
> string "ERR" or "ENO". It's a long shot, but it can't hurt to
> try.
Dale,
No errors, but some ENOTTY; don't know if those are new or were always
there.
> What options did you specify
On Wed, 6 Aug 2014 07:39:16 -0700 (PDT)
Rich Shepard wrote:
>After changing logwatch.pl to send its reports by mail the script
> worked for a few days. Today it failed completely. That is, running
> from the command line produces no output in the virtual terminal so
> apparently there's nothi
On Wed, 6 Aug 2014, Michael Rasmussen wrote:
Michael,
> use strict;
Yes.
> use warnings;
No.
> If not add them and forward the output after you run it again.
No output to console or mail.
> And forward a copy to me off list.
logwatch-strace.log sent separately and gzipped.
Tha
are:
use strict;
use warnings;
at the top?
If not add them and forward the output after you run it again.
And forward a copy to me off list.
On Wed, Aug 06, 2014 at 07:39:16AM -0700, Rich Shepard wrote:
>After changing logwatch.pl to send its reports by mail the script worked
> for a few da
After changing logwatch.pl to send its reports by mail the script worked
for a few days. Today it failed completely. That is, running from the
command line produces no output in the virtual terminal so apparently
there's nothing to report via mail either.
Running logwatch.pl via strace produ
15 matches
Mail list logo
