Your message dated Sun, 05 Jun 2011 09:02:09 +0000
with message-id <[email protected]>
and subject line Bug#608874: fixed in cron 3.0pl1-118
has caused the Debian Bug report #608874,
regarding [cron] New behavior of returning an error if grandchild exit status
not 0 is not properly advertised
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 [email protected]
immediately.)
--
608874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608874
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-116
Severity: minor
--- Please enter the report below this line. ---
After upgrade from cron 3.0pl1-114 to 3.0pl1-116 I had the following
problem:
My log reporting system began to send me a lot of error messages from cron.
Digging down it appears that the following cron command was the culprit:
Jan 3 04:41:01 private /USR/SBIN/CRON[12126]: (www-data) CMD (if [ -d
/usr/share/webcalendar ]; then cd /usr/share/webcalendar/tools;
./send_reminders.php 2>&1 |grep -v "PHP Notice" ; fi)
Jan 3 04:41:01 private /USR/SBIN/CRON[12125]: (CRON) error (grandchild
#12126 failed with exit status 1)
It never produced such an error before and apparently it's due to the
exit code of the last grep, usually =1 if nothing is output from
./send_reminders.php else than some PHP Notice.
I fixed it by a simple cat, just to avoid to have an exit status=1:
Jan 4 09:51:01 private /USR/SBIN/CRON[6150]: (www-data) CMD (if [ -d
/usr/share/webcalendar ]; then cd /usr/share/webcalendar/tools;
./send_reminders.php 2>&1 |grep -v "PHP Notice"|cat ; fi)
Before I was able to fix the problem I looked into the files
NEWS.Debian.gz and changelog.gz but couldn't find a description of this
new behavior.
I think it should be documented in one of those files.
Hopefully this bugreport by itself could help other people facing the
same problem and identifying what to do.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.34-1-amd64
Debian Release: squeeze/sid
990 testing www.debian-multimedia.org
990 testing security.debian.org
990 testing ftp.be.debian.org
990 testing deb.torproject.org
500 unstable ftp.be.debian.org
500 lucid linux.dropbox.com
1 experimental ftp.be.debian.org
--- Package information. ---
Depends (Version) | Installed
================================-+-==============
libc6 (>= 2.7) | 2.11.2-7
libpam0g (>= 0.99.7.1) | 1.1.1-6.1
libselinux1 (>= 1.32) | 2.0.96-1
debianutils (>= 1.7) | 3.4
adduser | 3.112+nmu2
lsb-base (>= 3.0-10) | 3.2-23.1
libpam-runtime (>= 1.0.1-11) | 1.1.1-6.1
Package Status (Version) | Installed
=============================-+-===========
nscd |
nis |
libpam-mount |
libpam-ldap |
libnss-ldap |
libnss-ldapd |
Recommends (Version) | Installed
===================================-+-===========
exim4 | 4.72-2
OR postfix |
OR mail-transport-agent |
lockfile-progs | 0.1.15
Suggests (Version) | Installed
============================-+-===========
anacron (>= 2.0-1) | 2.3-14
logrotate | 3.7.8-6
checksecurity |
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-118
We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive:
cron_3.0pl1-118.diff.gz
to main/c/cron/cron_3.0pl1-118.diff.gz
cron_3.0pl1-118.dsc
to main/c/cron/cron_3.0pl1-118.dsc
cron_3.0pl1-118_i386.deb
to main/c/cron/cron_3.0pl1-118_i386.deb
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Kastner <[email protected]> (supplier of updated cron 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 31 May 2011 14:50:34 +0200
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-118
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[email protected]>
Changed-By: Christian Kastner <[email protected]>
Description:
cron - process scheduling daemon
Closes: 608874
Changes:
cron (3.0pl1-118) unstable; urgency=low
.
* debian/control
- Limited Build-Depends for libaudit-dev to linux-any. I erroneously
assumed it applied to other OSes as well.
* debian/rules
- DEB_BUILD_OPTIONS for audit support is limited to Linux platforms
.
[ Javier Fernandez-Sanguino]
* debian/NEWS
- Document the new behaviour of cron regarding logging of non-zero
exit status cronjobs (Closes: #608874)
Checksums-Sha1:
66b2e8aa28bf6991769e8223131ad89509c50cdf 1231 cron_3.0pl1-118.dsc
f8cf1dd2012cef6812d9700164da0626b27f9d1d 89519 cron_3.0pl1-118.diff.gz
4d2bb1678bfd5206091b61f8dbb5298939e68567 96286 cron_3.0pl1-118_i386.deb
Checksums-Sha256:
a83595fd81ddbc0e619d963f89461b5d6992544dac0198a828cc16738b0b44fe 1231
cron_3.0pl1-118.dsc
33adc805175c6b6af9ed1aae71f2de6f01ed1d5f14c4858f2cf88bc1cbfd99f7 89519
cron_3.0pl1-118.diff.gz
14beb4263132fdce1284c0dd1162bd1026eb1f14847c85bb057b947ff46dbec1 96286
cron_3.0pl1-118_i386.deb
Files:
9e718bcd9c690d3bf5ba4d3f31c6b55e 1231 admin important cron_3.0pl1-118.dsc
d1af4a4a09fc0ed0b287e834912393f9 89519 admin important cron_3.0pl1-118.diff.gz
80b0079d37c8804be1454e3eaf747607 96286 admin important cron_3.0pl1-118_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFN60RAsandgtyBSwkRAnB3AKCDzo7npJdIzNt7E/RoauNJhg3VIQCfWcxJ
rjBlBErfJ/QQvyhuweo3wlw=
=+uTS
-----END PGP SIGNATURE-----
--- End Message ---
