Hello,
Have a bit of a problem with Exim 4.12 + exiscan-4.12-25.
I started using Exim about 3 weeks ago, liked it a lot, and till yesterday
everything worked ok. But yesterday and today Exim started to die
occasionally on signal 11. Like this:
Mar 30 11:12:16 cloud /kernel: pid 21664 (exim-4.12-1), uid 26: exited on signal 11
Mar 30 11:49:16 cloud /kernel: pid 22225 (exim-4.12-1), uid 26: exited on signal 11
Mar 30 13:02:08 cloud /kernel: pid 23459 (exim-4.12-1), uid 26: exited on signal 11
Mar 30 20:52:47 cloud /kernel: pid 912 (exim-4.12-1), uid 26: exited on signal 11
Mar 30 21:38:58 cloud /kernel: pid 1632 (exim-4.12-1), uid 26: exited on signal 11
Mar 30 23:30:04 cloud /kernel: pid 3409 (exim-4.12-1), uid 26: exited on signal 11
The latest of these events I managed to document in the "-d+all" mode by
running listening daemon like this:
2710 p1 S 0:01.37 /usr/local/sbin/exim -d+all -bd -q10m (exim-4.12-1)
The relevant part of the debug log seems to suggest there is something
wrong with ident code:
...
23:28:35 2710 Listening...
23:30:04 2710 ---0 Get 614688 0 daemon.c 164
23:30:04 2710 ---0 Get 614688 16 string.c 344
23:30:04 2710 Connection request from 210.22.102.30 port 51358
23:30:04 3409 ---0 Get 614704 24 string.c 344
23:30:04 3409 host in rfc1413_hosts? yes (matched "*")
23:30:04 3409 doing ident callback
23:30:05 2710 1 SMTP accept process running
23:30:05 2710 ---0 Rst 614688 ** daemon.c 613 24600
23:30:05 2710 child 3409 ended: status=0xb
23:30:05 2710 0 SMTP accept processes now running
23:30:05 2710 Listening...
...
Is it a known problem? Did anybody happen to observe similar behaviour?
--
Olwi
