Date: Fri, 12 Mar 2004 22:10:29 +0200 From: Ion-Mihai Tetcu <itetcu@apropo.ro> To: ports@FreeBSD.ORG Cc: eik@FreeBSD.org Subject: daily/330.fetchaudit Message-ID: <20040312221029.2a7ea717@it.buh.cameradicommercio.ro>
next in thread | raw e-mail | index | archive | help
Hi,
I've noticed the absence of "daily run output". The last is
Date: Wed, 10 Mar 2004 21:44:01 +0200 (EET)
and now it is:
# date
Fri Mar 12 21:49:17 EET 2004
ps axwl:
0 4265 471 0 -8 0 1380 716 piperd S ?? 0:00.00 cron: running job (cron)
0 4267 4265 0 8 0 1672 720 wait Ss ?? 0:00.01 /bin/sh -c periodic daily
0 4269 4267 0 8 0 1688 748 wait S ?? 0:00.02 /bin/sh - /usr/sbin/periodic daily
0 4278 4269 0 8 0 1712 748 wait S ?? 0:00.09 /bin/sh - /usr/sbin/periodic daily
0 4279 4269 0 8 0 1688 748 wait S ?? 0:00.00 /bin/sh - /usr/sbin/periodic daily
0 4280 4279 0 -8 0 1340 524 piperd S ?? 0:00.01 mail -s it.buh.cameradicommercio.ro daily run output root
0 4933 4278 0 8 0 1700 772 wait S ?? 0:00.02 /bin/sh /usr/local/etc/periodic/daily/330.fetchaudit
0 98521 4933 0 4 0 2616 968 select S ?? 0:02.73 fetch -1am ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-dist-distfiles/eik//auditfile.tbz
This is not a temporary problem (look at the hours), a snip of the daily
mails:
# grep 'Date:' /home/itetcu/MailMH/Work/buh/it/daily/* | sed -E '/.*,/s///'
5 Mar 2004 10:43:47 +0200 (EET)
6 Mar 2004 07:17:40 +0200 (EET)
7 Mar 2004 06:35:26 +0200 (EET)
8 Mar 2004 09:15:03 +0200 (EET)
9 Mar 2004 18:57:33 +0200 (EET)
Since the # uptime
10:04PM up 1 day, 10:57
I guess it fetch was stuck and the cron job got killed at the last reboot.
Maybe we should enforce a timeout and / or restart the fetch for the
audit file after some time (let's say an hour) ?
Point finger to fetch, which has the really nasty habit to stuck like this.
No, the rest of the periodic jobs work OK, and no, I don't consume all
the bandwidth.
--
IOnut
Unregistered ;) FreeBSD user
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040312221029.2a7ea717>