Your message dated Thu, 17 Jan 2008 15:01:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449345: exim4: daemon exits without notice when there is
no disk space
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: exim4
Version: 4.63-17
Severity: important
I am running an important exim4 server for dozens of users on Etch.
However, lately, when I notice that I do not get any mail anymore it seems
that the exim4 server has just exited/crashed, because it is no longer
running. When using QUEUERUNNER='separate', the queuerunner stays alive,
but after a while the stmp listener/daemon is dead.
After three days, I finally found something in the logs that might indicate
the source of the problems:
Nov 4 17:47:02 sphere exim[12843]: 2007-11-04 17:47:02 1IoicV-0003L9-DS failed
to write to main log: length=205 result=142 errno=9 (Bad file descriptor)
Nov 4 17:47:03 sphere exim[12843]: write failed on panic log: length=118
result=-1 errno=28 (No space left on device)
Nov 4 17:47:05 sphere exim[12844]: 2007-11-04 17:47:05 1Ioicr-0003LA-HM failed
to write to main log: length=183 result=-1 errno=28 (No space left on device)
Nov 4 17:47:05 sphere exim[12844]: write failed on panic log: length=122
result=-1 errno=28 (No space left on device)
[and so on...]
IMHO, the daemon should stay alive and try to log this or my change its
process name, appending [out of disk space] or something.
Regards,
Paul
-- Package-specific info:
Exim version 4.63 #1 built 20-Jan-2007 10:42:32
Copyright (c) University of Cambridge 2006
Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005)
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 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
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i486)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-4-486
Locale: LANG=C, LC_CTYPE=nl_NL.UTF8 (charmap=UTF-8)
Versions of packages exim4 depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii exim4-base 4.63-17 support files for all exim MTA (v4
ii exim4-daemon-heavy 4.63-17 exim MTA (v4) daemon with extended
exim4 recommends no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Mon, Nov 05, 2007 at 10:58:23AM +0100, Paul van Tilburg wrote:
> I am running an important exim4 server for dozens of users on Etch.
> However, lately, when I notice that I do not get any mail anymore it seems
> that the exim4 server has just exited/crashed, because it is no longer
> running. When using QUEUERUNNER='separate', the queuerunner stays alive,
> but after a while the stmp listener/daemon is dead.
>
> After three days, I finally found something in the logs that might indicate
> the source of the problems:
> Nov 4 17:47:02 sphere exim[12843]: 2007-11-04 17:47:02 1IoicV-0003L9-DS
> failed to write to main log: length=205 result=142 errno=9 (Bad file
> descriptor)
> Nov 4 17:47:03 sphere exim[12843]: write failed on panic log: length=118
> result=-1 errno=28 (No space left on device)
> Nov 4 17:47:05 sphere exim[12844]: 2007-11-04 17:47:05 1Ioicr-0003LA-HM
> failed to write to main log: length=183 result=-1 errno=28 (No space left on
> device)
> Nov 4 17:47:05 sphere exim[12844]: write failed on panic log: length=122
> result=-1 errno=28 (No space left on device)
> [and so on...]
>
> IMHO, the daemon should stay alive and try to log this
Trying to log this: Actually, exim _did_ log this, right? What's the
issue here?
> or my change its
> process name, appending [out of disk space] or something.
I have never seen a daemon doing something like this. If you send a
patch, I might report this upstream, but I don't think that a
patchless upstream bug report makes sense here. You are, of course,
free to report this upstream yourself.
In my opinion, the local admin should have mechanisms detecting a full
disk in place, and an MTA shouldn't have this bloat added.
I am closing this bug. Feel free to re-open if you want to.
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 621 72739835
--- End Message ---
