> Stefan,
>
> > I just updated to version 2.7.1 and experience this error with
> > $log_level=2:
> >
> > amavis[24809]: (24809-03) Sophie broken pipe (don't worry), retrying (1)
> > amavis[24809]: (24809-03) Amavis::IO::RW: Error flushing on close: Error
> > writing to socket: Broken pipe at /usr/sbin/amavisd line 6876,
[...]
> I checked the code, and it is alright, nothing to worry about.
> An extra check for a status of a flush before a close was added and
> an error during a flush() is now logged separately at log level 1,
> while previously this log entry was not there, just the final
> outcome of a close() was tested and reported.
To avoid the logging clutter at log level 1 or above, the following
trivial patch may be applied to 2.7.1, which just reduces a log level
for this innocent but sinister-looking message to 5.
The 2.8.0 will bring a more selective solution, differentiating
between this error on a regular close, from the same on a DESTROY.
Mark
--- amavisd~ 2012-04-29 02:31:15.000000000 +0200
+++ amavisd 2012-05-18 18:44:05.995242763 +0200
@@ -6771,3 +6771,3 @@
my $eval_stat = $@ ne '' ? $@ : "errno=$!"; chomp $eval_stat;
- do_log(1, "Amavis::IO::RW: Error flushing on close: %s", $eval_stat);
+ do_log(5, "Amavis::IO::RW: Error flushing on close: %s", $eval_stat);
};
