No longer syncing

[Martin Albisetti]

I copied a new file yesterday, and a new directory with very few files today, and none of them have sycned/
The tray icon appears instantly, but says that everything is up to date and stays there.
If it's of any value, tomboy syncing has been working without any problems.

[Martin Albisetti (beuno)]

.home.beuno..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.beuno..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: i386
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Rick McBride (rmcbride)]

seems like the syncdaemon is stuck on a piece of metadata in status STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ. I've seen similar behavior in the cases where my own sync would stop. flagging as possible metadata issue and assigning to Guillermo.

[Martin Albisetti (beuno)]

After rebooting, syncing seemed to kick in.
It's still syncing, but attaching the log before reboot, and when it's finished, the one after.

[Martin Albisetti (beuno)]

So it seems to have stopped syncing, although it hasn't finished uploading all the files.

Log attached.

[Guillermo Gonzalez (verterok)]

Facundo,
As you'r going to rework the AQ states, I'm assigned this bug to you.

Regards

[Facundo Batista (facundo)]

The problem seems to be here:

2009-11-05 13:37:37,640 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: START_WORKING_ON_METADATA_WITH_CONTQ; queues: metadata: 7; content: 2; hash: 0, fsm-cache: hit=37944 miss=6281) ----
2009-11-05 13:37:38,453 - ubuntuone.SyncDaemon.ActionQueue - WARNING - connection lost: Connection was closed cleanly.
2009-11-05 13:38:36,135 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 8; content: 2; hash: 0, fsm-cache: hit=37944 miss=6281) ----

This is the same problem that #487257, triggered differently. Marking as duplicate.