[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Negotiator restarted daily - error to fsync or flush
- Date: Thu, 28 Jan 2010 07:43:34 -0500
- From: Matthew Farrellee <matt@xxxxxxxxxx>
- Subject: Re: [Condor-users] Negotiator restarted daily - error to fsync or flush
$ grep 116 /usr/include/asm-generic/errno.h
#define ESTALE 116 /* Stale NFS file handle */
Since your spool is on NFS, and is probably being written to by multiple machines (Schedd + Negotiator), I'd suggest putting the Accountantnew.log in a different directory from the job_queue.log.
NEGOTIATOR.SPOOL = /workingcopy/negotiatorspool
If you are using HAD and the Replicator, the you can just point NEGOTIATOR.SPOOL to local disk and let HAD sync the Accountantnew.log between your HA Negotiators.
On 01/28/2010 06:25 AM, Johnson koil Raj wrote:
> Hi All,
> In our pool Negotiator is configured for HA. I am seeing this error
> daily or frequently Negotiator dies restarts.
> The spool directory is in nfs.
> I am not using condor_replication. so this file is needed.
> If I did't use Replication am I losing some thing.
> 1/27 04:02:18 ERROR "fsync of /workingcopy/spool/Accountantnew.log
> failed, errno = 116" at line 206 in file classad_log.cpp
> 1/28 04:07:10 ERROR "flush to /workingcopy/spool/Accountantnew.log
> failed, errno = 116" at line 202 in file classad_log.cpp
> Can any one tell why this kind of error occurs. Do I missed any
> Please do not print this email unless it is absolutely necessary.
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
> 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: