Suggestions for more logging?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Suggestions for more logging?

Vicki Brown
I hunted up a better script for running SpamAssassin from postfix and tweaked it for more logging and better errors and I'm still seeing some odd behavior.

e.g. from the system log:

Nov 17 23:33:14 g3po spamchk[87681]: Spam filter piping to SpamAssassin: /usr/local/bin/spamc -x -E -s 10485760
Nov 17 23:33:14 g3po spamchk[87683]: SpamAssassin marked message as spam; diverting.
Nov 17 23:33:14 g3po spamchk[87686]: SpamAssassin marked message as spam; diverting.
Nov 17 23:33:15 g3po spamchk[87691]: SpamAssassin marked message as spam; diverting.
Nov 17 23:33:15 g3po spamchk[87694]: SpamAssassin marked message as spam; diverting.
Nov 17 23:33:28 g3po postfix/qmgr[87590]: warning: connect to transport spamchk: Connection refused
Nov 17 23:42:28 g3po postfix/qmgr[137]: warning: connect to transport spamchk: Connection refused
Nov 17 23:47:27 g3po postfix/qmgr[137]: warning: connect to transport spamchk: Connection refused
Nov 17 23:52:28 g3po postfix/qmgr[137]: warning: connect to transport spamchk: Connection refused
Nov 17 23:52:29 g3po spamchk[419]: Spam filter piping to SpamAssassin: /usr/local/bin/spamc -x -E -s 10485760
Nov 17 23:52:31 g3po spamchk[422]: SpamAssassin marked message as spam; diverting.


Any suggestions as to why the script would just refuse connections for a while and then come back?

What can I do to drill down into the cause of "connect to transport spamchk: Connection refused"

- Vicki
Reply | Threaded
Open this post in threaded view
|

RE: Suggestions for more logging?

L.P.H. van Belle
Try starting spamd with

--listen-ip 127.0.0.1 --listen-ip ::1

Greetz,

Louis

> -----Oorspronkelijk bericht-----
> Van: [hidden email] [mailto:[hidden email]] Namens Vicki
> Brown
> Verzonden: woensdag 18 november 2015 9:13
> Aan: Postfix users
> Onderwerp: Suggestions for more logging?
>
> I hunted up a better script for running SpamAssassin from postfix and
> tweaked it for more logging and better errors and I'm still seeing some
> odd behavior.
>
> e.g. from the system log:
>
> Nov 17 23:33:14 g3po spamchk[87681]: Spam filter piping to SpamAssassin:
> /usr/local/bin/spamc -x -E -s 10485760
> Nov 17 23:33:14 g3po spamchk[87683]: SpamAssassin marked message as spam;
> diverting.
> Nov 17 23:33:14 g3po spamchk[87686]: SpamAssassin marked message as spam;
> diverting.
> Nov 17 23:33:15 g3po spamchk[87691]: SpamAssassin marked message as spam;
> diverting.
> Nov 17 23:33:15 g3po spamchk[87694]: SpamAssassin marked message as spam;
> diverting.
> Nov 17 23:33:28 g3po postfix/qmgr[87590]: warning: connect to transport
> spamchk: Connection refused
> Nov 17 23:42:28 g3po postfix/qmgr[137]: warning: connect to transport
> spamchk: Connection refused
> Nov 17 23:47:27 g3po postfix/qmgr[137]: warning: connect to transport
> spamchk: Connection refused
> Nov 17 23:52:28 g3po postfix/qmgr[137]: warning: connect to transport
> spamchk: Connection refused
> Nov 17 23:52:29 g3po spamchk[419]: Spam filter piping to SpamAssassin:
> /usr/local/bin/spamc -x -E -s 10485760
> Nov 17 23:52:31 g3po spamchk[422]: SpamAssassin marked message as spam;
> diverting.
>
>
> Any suggestions as to why the script would just refuse connections for a
> while and then come back?
>
> What can I do to drill down into the cause of "connect to transport
> spamchk: Connection refused"
>
> - Vicki

Reply | Threaded
Open this post in threaded view
|

Re: Suggestions for more logging?

Wietse Venema
In reply to this post by Vicki Brown
Vicki Brown:
> Nov 17 23:33:28 g3po postfix/qmgr[87590]: warning: connect to transport spamchk: Connection refused

The pipe service "spamchk" is throttled because of fatal errors,
and therevore connection requests are dropped by the kernel. You
need to resolve the fatal pipe daemon errors. Grep the logfile
for "fatal".

        Wietse