[Unison-hackers] Problem with error setting a watch

Marcos Athanasoulis marcos at athanasoulis.net
Wed Jan 28 22:26:43 EST 2015


Hi,

I am having an issue.  I replicated it with the following basic setup:

Server 1:

/ssd/unitest (directory being synced and watched)

Server 2

/home/unitest (remote directory synced and watched

If I create a new directory (in this example test1) on
server2://home/unitest/test1

The directory is properly synced back to server 1, but an error is
generated when trying to put a watch on the directory:

[2015-01-28 19:16:14,548 pyinotify ERROR] add_watch: cannot watch
/ssd/unitest/.unison.test1.70cf75d5f3a77222c5327ba3780dce0e.unison.tmp
WD=-1 Errno=No such file or directory (ENOENT)

And the directory test1 does exist, but it almost seems like it is
attempting to watch the temporary file unison creates and then renames to
the actual file name.  But when I turn on debug I can see (I think) that at
the point it is setting the watch the file has already been renamed to
test1 from the unison.tmp file, which it seems to be trying to set the
watch on (though it does not exist at that point).

This seems like it would be a common use case and I don't see anyone
posting similar issues.  Any ideas?

Thanks so much.  (And sidenote, extremely impressed and pleased with Unison
it has solved a big problem for me!)

I am on CentOS 6 (up to date) and Unison 2.48.3.

Here is the whole update session with the failure:

Looking for changes
  Waiting for changes from server
Reconciling changes
         <---- dir        test1
local        : absent
web02.the... : dir                modified on 2015-01-28 at 19:16:13  size
0         rwxr-xr-x user=0 group=0
Propagating updates
UNISON 2.48.3 started propagating changes at 19:16:14.54 on 28 Jan 2015
[BGN] Copying test1 from //web02.thehcn.net//home/unitest to /ssd/unitest
[END] Copying test1
UNISON 2.48.3 finished propagating changes at 19:16:14.54 on 28 Jan 2015
Saving synchronizer state
[2015-01-28 19:16:14,548 pyinotify ERROR] add_watch: cannot watch
/ssd/unitest/.unison.test1.70cf75d5f3a77222c5327ba3780dce0e.unison.tmp
WD=-1 Errno=No such file or directory (ENOENT)
Synchronization complete at 19:16:14  (1 item transferred, 0 skipped, 0
failed)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.seas.upenn.edu/pipermail/unison-hackers/attachments/20150128/63113f54/attachment.html>


More information about the Unison-hackers mailing list