Bug#396944: exim4 giving me problems again (#396944)

Marc Haber mh+debian-packages at zugschlus.de
Fri Jun 29 16:26:40 UTC 2007


[Please Cc: the BTS on all correspondence, in hard-to-debug cases it
is vital that the BTS has complete information.]

Please allow me to bounce your message and the ones following into the BTS.

On Fri, Jun 29, 2007 at 04:56:45AM -0600, Bruce Sass wrote:
> It happened again!

:-(

> The panic log has an entry at 23:13:21 for a failed start (23:08:50 in 
> mainlog);

Why did the start fail? Old daemon still running?

> pidwatch.log shows the pid disappearing between 22:50:01 and 
> 23:00:02; dpkg.log shows an upgrade of exim4 starting with the -config
> package at 22:54:22 (dpkg started logging at 22:48:07 and finished at 
> 23:10:04).
> 
> The only other log entries around that time are for the pidwatch cron 
> job itself (in auth and syslog), and scrollkeeper-update unregistering 
> (22:54:28+) then registering (23:08:41+) three exim4 .omf files in 
> scrollkeeper.log.
> 
> So, how much of which logs should I send to the BTS?

We only have proof now that the issue is somewhat related to updating
exim. I'll put some more debugging code in the maintainer scripts for
the next exim4 upload. Please make sure that you set EX4DEBUG to a
non-empty value before your upgrade to any version later than 4.67-5
and capture output please.

It might also be a good idea to run your pidwatch script in more
shorter frequency (such as every second) during the update, and to
find out whether your system uses some sort of prelinking etc.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190




More information about the Pkg-exim4-maintainers mailing list