[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] NFS errors with log file

Kent--what about the case where a complicated DAG is being parsed by
more than one schedd, which could in extremes even be on
different machines? Is there any thought being given to this possibility
when extending DAGMAN?

Steve Timm

The reason for all of this is that file locking generally doesn't work
reliably on NFS, which can cause corruption of the log files.  For
stand-alone jobs, having a log file on NFS generates a warning, but for a
DAGMan node job, it generates a fatal error (because the log files are
crucial to the proper execution of the DAG).  (You can change this
behavior with the configuration macros mentioned below.)

You should look at the information for the LOG_ON_NFS_IS_ERROR and
DAGMAN_LOG_ON_NFS_IS_ERROR configuration macros in the configuration
section of the manual
(http://www.cs.wisc.edu/condor/manual/v7.0/3_3Configuration.html) for

Kent Wenger
Condor Team
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.