We actually had looked into reasons why this error might occur a few weeks ago, and discovered that the slave was only making one attempt to update its slave info file. If another process (like the Monitor or Pulse) is accessing this file, this error occurs, so we’ve modified the slave to make multiple attempts at updating is info file before reporting this error. The “multiple write attempt” functionality is actually standard throughout the rest of Deadline, it was just this one particular case that slipped through the cracks.
While this still doesn’t guarantee that this error won’t occur again, its frequency will be greatly reduced. Also, getting these errors every now and then won’t cause any issues, because the slave will just update its info file during the next attempt.