On 28 February 2017 at 00:16, Daryl Richards via Exim-users <
exim-users@???> wrote:
> Hello,
>
> I don't know if this is related to any of the other crash issues reported
> lately, so I'll start a new message in case it isn't.
>
> Two different servers, both on FreeBSD 10.3, both with latest exim port
> (exim-4.88_2) are often having the exim process crash during mail delivery.
> In my system log, I see many of:
>
> .....
> pid 61062 (exim), uid 26: exited on signal 11
> pid 61733 (exim), uid 26: exited on signal 11
> pid 63665 (exim), uid 26: exited on signal 11
> pid 75168 (exim), uid 26: exited on signal 11
> pid 79529 (exim), uid 26: exited on signal 11
> pid 81047 (exim), uid 26: exited on signal 11
> pid 83091 (exim), uid 26: exited on signal 11
> pid 83868 (exim), uid 26: exited on signal 11
> pid 90324 (exim), uid 26: exited on signal 11
> pid 92003 (exim), uid 26: exited on signal 11
> ....
>
> In the exim mainlog, I see thousands of lines (each time it crashes,
> sometimes 10s of thousands of lines) like:
>
> .....
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> 2017-02-27 00:05:44 [25045] 1ciDLb-0006Vx-92 SSL_write: (from
> smtp24.elabs11.com [74.116.234.24]:44780) syscall: Broken pipe
> .....
>
> I've tried re-compiling all ports, no help. I've tried changing various
> SSL parameters, no help.
>
> Is this likely related to some of the other crashes that people have been
> working through lately? If so, I'd be willing to test the newer RCs if
> someone could help point me in a direction to have it compile under the
> ports framework so I know my options are the same...
>
> If it's something new, if I can submit more information to track this
> down, let me know.
>
> Thanks
Find a way to exclude this host from everything to do with SSL, I think.
The output of your exim -bP and exim -bV should help those who want to see
what you have.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."
