The thing it that in the middle of syncronization it gets stucked in the standoff state without notifying of this.
Before getting stucked, it looses the connection.
2010-02-10 16:29:17,751 - ubuntuone.SyncDaemon.ActionQueue - WARNING - connection lost: Connection was closed cleanly.
2010-02-10 16:29:20,599 - ubuntuone.SyncDaemon.ActionQueue - INFO - Protocol version OK
2010-02-10 16:29:51,505 - ubuntuone.SyncDaemon.ActionQueue - WARNING - connection lost: Connection was closed cleanly.
2010-02-10 16:30:05,870 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: START_STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ----
2010-02-10 16:32:05,870 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: START_STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ----
The thing it that in the middle of syncronization it gets stucked in the standoff state without notifying of this. SyncDaemon. ActionQueue - WARNING - connection lost: Connection was closed cleanly. SyncDaemon. ActionQueue - INFO - Protocol version OK SyncDaemon. ActionQueue - WARNING - connection lost: Connection was closed cleanly. SyncDaemon. Main - NOTE - ---- MARK (state: START_STANDOFF_ WAITING_ WITH_NETWORK_ WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ---- SyncDaemon. Main - NOTE - ---- MARK (state: START_STANDOFF_ WAITING_ WITH_NETWORK_ WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ----
Before getting stucked, it looses the connection.
2010-02-10 16:29:17,751 - ubuntuone.
2010-02-10 16:29:20,599 - ubuntuone.
2010-02-10 16:29:51,505 - ubuntuone.
2010-02-10 16:30:05,870 - ubuntuone.
2010-02-10 16:32:05,870 - ubuntuone.