Re: [Condor-users] Strange condor_preen message

[Steven Timm <timm@xxxxxxxx>]

Follow up on this..
a) all of these directories came from jobs
submitted by a single user.
b) He submitted those jobs via condor_run rather than condor submit
c) the first four digits of the directory name correspond to the
first four digits of the linux pid of the condor_starter.

Unfortunately there are none of these jobs running anymore.

Steve


On Mon, 17 Jul 2006, Steven Timm wrote:

> Strange condor_preen message:
>
> I have seen the following request coming from about 20 of the nodes
> on my cluster thus far.  They are rather strange because
> I thought that the spool directories ought to be the same name as the
> process id of the condor_starter that is running the job.
>
> Obviously the directory names below are not corresponding
> to any real linux process because the names are too long.
> Any idea what might be causing it?
>
> Steve Timm
>
> ---------- Forwarded message ----------
> Date: Mon, 17 Jul 2006 12:03:08 -0500
> From: condor <condor@xxxxxxxxxxxxxxx>
> To: farm-team@xxxxxxxx
> Subject: [Condor] condor_preen results
>
> This is an automated email from the Condor system
> on machine "fnpc14.fnal.gov".  Do not reply.
>
>
> The condor_preen process has found the following
> stale condor files on <fnpc14>:
>
>   /local/stage1/condor/execute/dir_25667656 - Removed
>   /local/stage1/condor/execute/dir_27313663 - Removed
>   /local/stage1/condor/execute/dir_30839682 - Removed
>
>
> What is condor_preen?
>
> The condor_preen tool examines the directories belonging to Condor, and
> removes extraneous files and directories which may be left over from Condor
> processes which terminated abnormally either due to internal errors or a
> system crash.  The directories checked are the LOG, EXECUTE, and SPOOL
> directories as defined in the Condor configuration files.  The condor_preen
> tool is intended to be run as user root (or user condor) periodically as a
> backup method to ensure reasonable file system cleanliness in the face of
> errors. This is done automatically by default by the condor_master daemon.
> It may also be explicitly invoked on an as needed basis.
>
> See the condor manual section on condor_preen for more details.
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Questions about this message or Condor in general?
> Email address of the local Condor administrator: farm-team@xxxxxxxx
> The Official Condor Homepage is http://www.cs.wisc.edu/condor
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR

--
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team