Hi, You might try 1) increasing the logging verbosity of cron via uncommenting EXTRA_OPTS="-L 2" line in /etc/default/cron, and 2) taking a look at /var/spool/cron directory contents.
Best. On Mon, 21 Feb 2011 13:15:49 +1100, Robert S writes: > I'm getting these in my syslog: > > Feb 21 06:05:01 debian /USR/SBIN/CRON[17713]: (CRON) error (grandchild > #17716 failed with exit status 1) > Feb 21 07:05:01 debian /USR/SBIN/CRON[17855]: (CRON) error (grandchild > #17858 failed with exit status 1) > Feb 21 08:05:01 debian /USR/SBIN/CRON[18084]: (CRON) error (grandchild > #18087 failed with exit status 1) > Feb 21 09:05:01 debian /USR/SBIN/CRON[18501]: (CRON) error (grandchild > #18503 failed with exit status 1) > Feb 21 10:05:01 debian /USR/SBIN/CRON[20837]: (CRON) error (grandchild > #20839 failed with exit status 1) > > AFAICS I don't have any cron jobs running at 1 minute past the hour - > in /etc/crontab, /etc/cron.d/* or /etc/cron.hourly. I tried clearing > out all hourly scripts but I still get this message. > > What is happening here? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k4gtv3wb....@alamut.ozu.edu.tr