PDA

View Full Version : Fedora 7 crontabs/logwatch



Luniz2k1
7th September 2007, 03:02 PM
Ever since the crontabs 1.10-15.fc7 update, cron.daily has not been working properly. And yes, I have crontabs 1.10-16.fc7 installed, but things still are not the same. For instance the last few days I have received 60 logwatch emails (1 per min) each day between 4:15am and 5:15am. The /var/log/cron log file shows:


Sep 7 04:15:00 luniz anacron[10955]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 04:15:01 luniz crond[10961]: (root) CMD (run-parts /etc/cron.daily)
Sep 7 04:15:59 luniz anacron[11453]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 04:16:01 luniz crond[11485]: (root) CMD (run-parts /etc/cron.daily)
Sep 7 04:16:59 luniz anacron[12051]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 04:17:01 luniz crond[12083]: (root) CMD (run-parts /etc/cron.daily)
Sep 7 04:17:59 luniz anacron[12592]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 04:18:01 luniz crond[12624]: (root) CMD (run-parts /etc/cron.daily)
...
...
...
Sep 7 05:09:00 luniz anacron[8184]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 05:10:00 luniz anacron[8718]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 05:11:00 luniz anacron[9287]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 05:12:00 luniz anacron[9821]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 05:12:59 luniz anacron[10352]: Updated timestamp for job `cron.daily' to 2007-09-07
Sep 7 05:13:59 luniz anacron[10886]: Updated timestamp for job `cron.daily' to 2007-09-07

Prior to the update, the cron log file only showed 2 lines per day:


Aug 27 04:02:01 luniz crond[14145]: (root) CMD (run-parts /etc/cron.daily)
Aug 27 04:16:59 luniz anacron[14308]: Updated timestamp for job `cron.daily' to 2007-08-27
Aug 28 04:02:01 luniz crond[31438]: (root) CMD (run-parts /etc/cron.daily)
Aug 28 04:17:00 luniz anacron[31600]: Updated timestamp for job `cron.daily' to 2007-08-28
Aug 29 04:02:01 luniz crond[16220]: (root) CMD (run-parts /etc/cron.daily)
Aug 29 04:16:59 luniz anacron[16392]: Updated timestamp for job `cron.daily' to 2007-08-29
Aug 30 04:02:01 luniz crond[824]: (root) CMD (run-parts /etc/cron.daily)
Aug 30 04:16:59 luniz anacron[995]: Updated timestamp for job `cron.daily' to 2007-08-30
Aug 31 04:02:01 luniz crond[18010]: (root) CMD (run-parts /etc/cron.daily)
Aug 31 04:16:59 luniz anacron[18173]: Updated timestamp for job `cron.daily' to 2007-08-31

I was forced to remove a nightly backup script that I had running in cron.daily because for the last few days, there would be 50+ copies of this script running at the same time every morning starting at 4am.

This is what the current /usr/bin/run-parts looks like from crontabs 1.10-16.fc7:


#!/bin/bash
# run-parts - concept taken from Debian

# keep going when something fails
set +e

if [ $# -lt 1 ]; then
echo "Usage: run-parts <dir>"
exit 1
fi

if [ ! -d $1 ]; then
echo "Not a directory: $1"
exit 1
fi

# Ignore *~ and *, scripts
for i in $1/*[^~,] ; do
[ -d $i ] && continue
# Don't run *.{rpmsave,rpmorig,rpmnew,swp,cfsaved} scripts
[ "${i%.cfsaved}" != "${i}" ] && continue
[ "${i%.rpmsave}" != "${i}" ] && continue
[ "${i%.rpmorig}" != "${i}" ] && continue
[ "${i%.rpmnew}" != "${i}" ] && continue
[ "${i%.swp}" != "${i}" ] && continue
[ "${i%,v}" != "${i}" ] && continue

if [ -x $i ]; then
$i 2>&1 | awk -v "progname=$i" \
'progname {
print progname ":\n"
progname="";
}
{ print; }'
fi
done

exit 0

Any ideas as to why I am still having problems with the latest crontabs 1.10-16.fc7?

lmatter
12th September 2007, 01:22 AM
After a recent upgrade my logwatch emails stopped coming all together; last one was on September 2nd. I also have crontabs-1.10-15.fc7 installed.

Checking /var/log/cron (and cron.1) I see that until that day, it took minutes (like 10) between "Job `cron.daily' started" and "Job `cron.daily' terminated". Afterwards cron.daily is started and terminated in the same second.

Luniz2k1
12th September 2007, 04:42 AM
Problem seems to have gone away.

lmatter
12th September 2007, 04:32 PM
upgrading to crontabs-1.10-16.fc7 seems to have solved the problem.