Pkg exim4 users - Feb 2008 - Exim4 broken after apt-get

Dear all,

I am trying to urdestand what did break after I ran a usual apt-get
upgrade on my system.

I am running a Debian lenny on a AMD64 SMP box.

Here is output of uname -a:
Linux montblanc 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
GNU/Linux

And it is running a mail server with Exim4 and Cyrus IMAP.

Here is output of exim4 -bV:

Exim version 4.68 #1 built 01-Nov-2007 19:08:38
Copyright (c) University of Cambridge 2006
Berkeley DB: Berkeley DB 4.6.21: (September 27, 2007)
Support for: crypteq iconv() IPv6 PAM Perl GnuTLS move_frozen_messages
Content_Scanning Old_Demime
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
Segmentation fault


It is been running smooth for ages and today I found my paniclog was
getting filled. Then I noticed very strage behaviour. The only recent
change in my system was apt-get upgrade last day.


My paniclog has many messages like this one:
2008-02-08 10:33:52 [11323] 1JNPcE-0002wa-QM lmtp transport process
returned non-zero status 0x000b: terminated by signal 11

(lmtp is the transport top Cyrus IMAP)


Furthermore, in the mainlog one can see same error messages with the SPTM
transport:

2008-02-08 10:08:06 [10942] 1JNPDB-0002qP-Di == xyz at xxx.yyy R=dnslookup T
=remote_smtp defer (0): smtp transport process returned non-zero status
0x000b: terminated by signal 11

The messages are kept in the system as it is reported by mailq:

32m  1.5K 1JNPDB-0002qP-Di <xxx at yyy.zzz> *** frozen ***
        D xxx.yyy at www

But actually email is being sent and received.


Now, if I restart exim4 I get an uggly message:

montblanc:/etc/exim4# /etc/init.d/exim4 restart
Stopping MTA for restart:/usr/sbin/update-exim4.conf: line 419: 11753
Segmentation fault      "${EXIM}" -C
"${UPEX4C_outputfile}.tmp" -bV
>/dev/null
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not
installing
/var/lib/exim4/config.autogenerated.tmp to
/var/lib/exim4/config.autogenerated
montblanc:/etc/exim4#

You get the same message by running update-exim4.conf (By the way the
system is on split config).

Can someone give me any hints about what to check? Shall I rollback to
previous package? Anything has changed in the config schema? Any
dependency that might be broken?

Thanks,
Josep SERRANO.

> My paniclog has many messages like this one:
> 2008-02-08 10:33:52 [11323] 1JNPcE-0002wa-QM lmtp transport process
> returned non-zero status 0x000b: terminated by signal 11
Please check the kernel log (output from "dmesg", or syslog files)
from
that time for anything suspicious.

Hi Florian, thanks for your answer
> Please check the kernel log (output from "dmesg", or syslog
files) from
> that time for anything suspicious.
>
it is full of seg fault messages like the following one:

exim4[21368]: segfault at fffffffffffffffa rip 00002b429f5b8b6b rsp
00007fff0ddf2470 error 4

Josep SERRANO