Your message dated Wed, 14 Aug 2019 07:49:28 +0000 with message-id <e1hxo2c-000dx4...@fasolo.debian.org> and subject line Bug#399930: fixed in exim4 4.92.1-2 has caused the Debian Bug report #399930, regarding exim4: logrotation race condition with exim writing to logs 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 399930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: exim4 Version: 4.50-8sarge2 Severity: normal Yesterday exim died with the following error in the panic log: 2006-11-22 06:25:23 +1100 Cannot open main log file "/var/log/exim4/mainlog": Permission denied: euid=102 egid=102 This was a fairly busy server so by the time I managed to get to it 20k messages got backed up. Having thought about it though the only way I could see the above happening would be due to a race condition in logrotate between logrotates create option fulfilling its duties and exim trying to deliver/accept an email. I think it would've gone a little like this: logrotate rotates the logs logrotate creates a new log file due to the create option exim attempts to log to the new logfile exim fails to log as logfile is owned root.adm (no write permissions) exim panics and bails logrotate chowns logfile to Debian-exim.adm logrotate chmods logfile 640 It was a slim chance but I cannot think of what else might have happened. The obvious fix, as far as I can see, was to replace the create option with nocreate. It's not necessary as exim will automatically attempt to create the logfile if it's missing and since the log dir is owned by Debian-exim and exim has write permissions it'll succeed. The dir is also group sticky so the new file will automatically get group-owned to adm. About the only thing that'll be lacking, I think, is the group read permission but that's better then no mail server IMO. If I'm wrong then I'm lost as to an explanation for what happened. This was with a custom build of 4.62-1, btw though I have checked and the logrotation is thesame for the standard sarge build. -- Package-specific info: Exim version 4.50 #1 built 11-Apr-2006 12:29:22 Copyright (c) University of Cambridge 2004 Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Support for: iconv() IPv6 GnuTLS Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16.29 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages exim4 depends on: ii exim4-base 4.50-8sarge2 support files for all exim MTA (v4 ii exim4-daemon-light 4.50-8sarge2 lightweight exim MTA (v4) daemon -- no debconf information
--- End Message ---
--- Begin Message ---Source: exim4 Source-Version: 4.92.1-2 We believe that the bug you reported is fixed in the latest version of exim4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 399...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler <ametz...@debian.org> (supplier of updated exim4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 14 Aug 2019 09:25:28 +0200 Source: exim4 Architecture: source Version: 4.92.1-2 Distribution: unstable Urgency: medium Maintainer: Exim4 Maintainers <pkg-exim4-maintain...@lists.alioth.debian.org> Changed-By: Andreas Metzler <ametz...@debian.org> Closes: 399930 Changes: exim4 (4.92.1-2) unstable; urgency=medium . * Pulled from exim-4.92+fixes branch: + 75_30-Fix-crash-after-TLS-channel-shutdown.patch + 75_31-Auth-handle-socket-read-errors-in-Dovecot-authentica.patch * Add Breaks: sa-exim (<< 4.2.1-17) to -heavy, see #930648. * Change *.logrotate to nocreate to work around #400198. Closes: #399930 Checksums-Sha1: aab2884b41a2026579a66d5d3cf615fdf96d31dd 2849 exim4_4.92.1-2.dsc 596c75c0273a0382ff0ee00db102e02255db0b6d 477656 exim4_4.92.1-2.debian.tar.xz Checksums-Sha256: b9d33ad2f82e01d755ba09de2962c3204b88fce54aa0c2d31762bda52d6c9396 2849 exim4_4.92.1-2.dsc c2e7ebdc7acc527fe1b87e8606ddc2e8826699b2bca24b78e5fc8407124e9728 477656 exim4_4.92.1-2.debian.tar.xz Files: 292fae55da6e8ddea4aa133acd821930 2849 mail standard exim4_4.92.1-2.dsc a7ac9db8144d0c0da67e4eaa54dcdd84 477656 mail standard exim4_4.92.1-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl1TuO8ACgkQpU8BhUOC FIR6Ig//aLIpEx8nz1lv0PvxlFFWUMurgjTRpfmffnfyQWI/12b4LAkCpGOBT2sL ELE5P63Ih/Z49W3WY2cedgZSdWEZmFdHg9y1wF7hNqWtpEr8j3EIE2YMkVZxCfZf xpgV2cPagdsU4gdTB9taPO/YLZZixIDptVJZXZURL+y0S6dT3lPjEEL9qigIrfin bysf4+ehHL3SbNoPvCep8XsRfOwNxz7aDUhyhu9xohgtMc3hwPvf8x63ndEL5BlS t+hhMjUjhufYDJwgRbG47719q5TT2uA8Moe7JPT7qExS+nllAa2BsN702ZPvcAiL 62OEJ1DaFY1I4K46/Ayd6OmwO1+OigWVNxsILv/GpzYvxLOiqEnBgmR4rrx1AX6/ BkckTSL9Hw4oy1Q22oXNBwt8VLzKLqYJz4D1HqogWXRhRY6OqVaMIVgJZaqZ6VLQ nS5cU3az/FT5LYTOcoeLUL3puLxpt17cENAry75TBIkRiEf5NwNgoyVBcYsj2eWk fzqE/SHbSmiF2Zsp7kgsE3YzQJ1qkFaz7esPz/RCE3eNHTxCBJvXORBiYTJzuAb0 uOeYtnpwOrXLAK/YtKlmdlZRVU5AWhgDOQs0uQ5p1Hscog15099daYV4BH/Lg6bD abpSXcy0btjFStvDYTt6ClclDMZkHH+E1QSyEcvhj5+060jSTYY= =g8eY -----END PGP SIGNATURE-----
--- End Message ---
