Rodrigo,
> I've just upgraded to amavisd-new 2.3.1 and spamassassin 3.0.3, and
> I'm getting these error messages:
>
> May 19 03:18:07 omni amavis[11980]: (11965-01) TROUBLE in
^^^^^ ^^^^^
> process_request: Error writing a SMTP response to the socket: Bad file
> descriptor
> at (eval 41) line 788, <GEN6> line 270.
> May 19 03:18:07 omni amavis[11980]: (11965-01) Requesting process
^^^^^ ^^^^^
> rundown after fatal error
>
> The only way to avoid them is to set $sa_local_tests_only to 1.
Trouble. Looks like a runaway forked process created by SA.
The PID inserted by syslog should match the am_id of the task,
but it doesn't in your case.
> I have dcc and pyzor disabled at
> ~amavis/.spamassassin/local.cf. Running amavis with sa-debug does not
> give an evident error.
My guess is that dccproc or pyzor can not be started for some reason,
and SA fails to notice that exec failed.
Mark
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
