GNOME Bugzilla – Bug 535279
FAILURE OF SYNCHRONIZATION: RECURRENT AND REPRODUCIBLE
Last modified: 2009-04-23 02:14:01 UTC
Please describe the problem: Choosing 'Synchronize Notes' from the 'Tools' menu usually generates the following error message: Server is locked One of your other computers is currently synchronizing. Please wait 2 minutes and try again. Steps to reproduce: 1. JUST TRY TO SYNCHRONIZE NOTES IN UBUNTU HARDY HERON 2. 3. Actual results: Server is locked One of your other computers is currently synchronizing. Please wait 2 minutes and try again. Expected results: NOTHING HAPPENS. THIS MESSAGE CONTINUES UNTIL I DELETE THE 'LOCK' FILE TOMBOY'S BACKUP DIRECTORY/LOCATION Does this happen every time? YES Other information: Usually have to delete the lock file to restore synchronize. But it reforms and persist ... tedious after the upteenth time! CONTENTS OF THE 'LOCK' FILE IN THE DIRECTORY ARE PASTED BELOW<?xml version="1.0" encoding="utf-8"?> <lock> <transaction-id>d2c30f99-0780-4642-a941-fdcbe330e923</transaction-id> <client-id /> <renew-count>16</renew-count> <lock-expiration-duration>00:02:00</lock-expiration-duration> <revision>59</revision> </lock>
What version of Tomboy is this? This may have been fixed in 0.10.2.
(In reply to comment #1) > What version of Tomboy is this? This may have been fixed in 0.10.2. > Version 0.10.1 - this is the version that's packaged with Ubuntu 8.04. (Hardy Heron). OS if fully updated. Will get the latest version of Tomboy from it's home site, update and see whether the problem goes away. Thanks for the tip. By the way, this has become an indispensable application. Like the microwave, don't know how I managed before Tomboy!
I'm using Tomboy 0.10.2 (also in Ubuntu 8.10) and I see this behavior too. I actually have to delete the lock file twice --- the first error I get is: 8/3/2008 8:42:48 PM [DEBUG]: SyncThread using SyncServiceAddin: SSH (sshfs FUSE) 8/3/2008 8:42:49 PM [DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 22 nturner@nturner-desktop:tomboy-sync /home/nturner/.tomboy/sync-sshfs 8/3/2008 8:42:50 PM [DEBUG]: Error calling /usr/bin/sshfs 8/3/2008 8:42:50 PM [DEBUG]: Exception while creating SyncServer: An error ocurred while connecting to the specified server: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option at Tomboy.Sync.FuseSyncServiceAddin.MountFuse (Boolean useStoredValues) [0x00000] at Tomboy.Sync.FuseSyncServiceAddin.CreateSyncServer () [0x00000] at Tomboy.Sync.SyncManager.SynchronizationThread () [0x00000] <the fuse filesystem is not mounted at this point> <I do a "rm ~/.tomboy/sync-sshfs/lock" and retry the sync> 8/3/2008 8:43:20 PM [DEBUG]: SyncThread using SyncServiceAddin: SSH (sshfs FUSE) 8/3/2008 8:43:20 PM [DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 22 nturner@nturner-desktop:tomboy-sync /home/nturner/.tomboy/sync-sshfs 8/3/2008 8:43:22 PM [DEBUG]: Sync: Discovered a sync lock file, wait at least 00:02:00 before trying again. 8/3/2008 8:43:22 PM [DEBUG]: PerformSynchronization: Server locked, try again later <I've tried waiting, but it does not appear to help...> <the fuse filesystem IS mounted at this point, so the file I'm rm'ing is on the remote system> <I do a "rm ~/.tomboy/sync-sshfs/lock" a 2nd time and try the sync a 3rd time> 8/3/2008 8:45:46 PM [DEBUG]: SyncThread using SyncServiceAddin: SSH (sshfs FUSE) 8/3/2008 8:45:47 PM [DEBUG]: 8 8/3/2008 8:45:47 PM [DEBUG]: Sync: GetNoteUpdatesSince rev 4 8/3/2008 8:45:47 PM [DEBUG]: GetNoteUpdatesSince xpath returned 0 nodes 8/3/2008 8:45:47 PM [DEBUG]: GetNoteUpdatesSince (4) returning: 0 8/3/2008 8:45:47 PM [DEBUG]: Sync: 0 updates since rev 4 8/3/2008 8:45:47 PM [DEBUG]: GetAllNoteUUIDs has 220 notes 8/3/2008 8:45:47 PM [DEBUG]: Sync: Uploading 0 note updates 8/3/2008 8:45:47 PM [DEBUG]: GetAllNoteUUIDs has 220 notes 8/3/2008 8:45:48 PM [DEBUG]: Sync: New revision: 4 <it works. yay.> Let me know if I can provide more info to help debug this.
Probably a dupe of bug #522424 , but I don't have time to investigate right now.
Got click happy, didn't mean to close this bug.
Not a dupe of bug #522424. Working on it (related to how lock files are being handled).
Issues: 1. Lock files are being updated every two minutes for no good reason (some timer issue) when no sync is occurring. Probably the main cause of the error reported here. I think this may the result of an unexpected exception during sync preventing the lock update timer from being canceled. 2. Lock files are being created in (for example) ~/.tomboy/sync-sshfs, even if the server isn't mounted. Then mount attempts fail because the directory is non-empty. This may be a last vestige of bug #522424, or it may be something else. If it's related to issue 1, it could be that the server is being unmounted after five minutes, but the lock update timer is recreating the lock file anyway.
I'm right about the causes of the issues in comment #7. Working on fixes now. Also fixing the stuff that's causing those exceptions in the first place. :-)
Fixed in r2145, but it could really use more testing. I hope a lot of people try out 0.12.0 so that any remaining fixes will be available quickly in 0.12.1.
*** Bug 554295 has been marked as a duplicate of this bug. ***