On 20/10/16 17:32, Andreas Metzler wrote: > I have just found this:
> Oct 20 03:22:19 XXXXXXXXX kernel: [1631169.824248] exim4[12010]: segfault at 0 ip 00007f634fee43e0 sp 00007ffc8abcf2b8 error 4 in libc-2.19.so[7f634fe73000+1a1000]
>
> with a corresponding mainlog of
> 2016-10-20 03:22:18 TLS error on connection from 7b.e9.36a9.ip4.static.sl-reverse.com (masscan) [169.54.233.123] (gnutls_handshake): The TLS connection was non-properly terminated.
>
> I guess this is too little information for finding the reason but I am
> willing to be surprised. ;-)
Without a coredump, yeah. And most people don't enable cores for setuid
programs. Ah, how dense is your connection rate - was that
the only likely related connection?
Thanks for spotting it and telling us though; please keep an
eye out for any more.
--
Cheers,
Jeremy
