Hallo Torsten,
> Cleaning up /home/atlasprd019
> find: ./.lcgjm/jobdescription.l16260: No such file or directory
> [...]
> find: ./.globus/job/grid-ce5.physik.uni-wuppertal.de/29072.1329620060: No such file or directory
> find: ./gram_job_mgr_10976.log: No such file or directory
> find: ./gram_job_mgr_25494.log: No such file or directory
> Cleaning up /home/atlasprd020
I think I have never seen the cron job produce such errors,
certainly not in those quantities!
It could happen if there is a big turnover in the account's
directory while the cron job is running, i.e. jobs for that
account would have to come in and finish at a high rate,
such that "find" will scan the directory at one time and
be unable to access some of the files a while later.
That scenario would require a large amount of job traffic
for the account and/or the file system being (very) slow
for some reason... Maybe an ongoing backup or so?
The cron job runs in the night...
|