Stuck in UNKNOWN_ERROR state after receiving SYS_SERVER_RESCAN_DONE event when in START_CONNECTING_WITH_CONTQ state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Client |
Fix Released
|
High
|
John Lenton |
Bug Description
After first installing ubuntuone-client, I had quite a lot (~ 1.5 GB) to upload. While the client was "Working", it got disconnected for 10 seconds (I didn't see this happen, but concluded it from checking syncdaemon.log).
Then, when it had reconnected and authenticated, it went to the SCANNING_WITH_BOTHQ state, but got disconnected again, so it when to START_CONNECTIN
But, while it was in START_CONNECTIN
Since that SYS_SERVER_
I don't think this is a duplicate of Bug #376143, since getting stuck in UNKNOWN_ERROR is the end result, not the cause of the problem.
Here's the relevant log snippet, see the attachment for the full log:
2009-07-15 12:47:45,296 - ubuntuone.
Traceback (most recent call last):
File "/usr/lib/
next_state = self.state.
File "/usr/lib/
% (self.name, event))
BadTransition: State START_CONNECTIN
2009-07-15 12:47:45,340 - ubuntuone.
Changed in ubuntuone-client: | |
importance: | Medium → High |
importance: | High → Medium |
milestone: | none → w15 |
importance: | Medium → High |
Changed in ubuntuone-client: | |
milestone: | w15 → w17-karmic-alpha4 |
Changed in ubuntuone-client: | |
status: | Confirmed → Fix Released |
On Wed, Jul 15, 2009 at 12:41:43PM -0000, Tom wrote: G_WITH_ CONTQ to try and reconnect. G_WITH_ CONTQ, it got at RESCAN_ DONE from the SCANNING_ WITH_BOTHQ, and that's where it RESCAN_ DONE was unexpected at that point, it went SyncDaemon. State - ERROR - START_CONNECTIN G_WITH_ CONTQ --[SYS_ SERVER_ RESCAN_ DONE]-- > ERROR!!! python2. 6/dist- packages/ ubuntuone/ syncdaemon/ state.py" , line 52, in handle_default next(event) python2. 6/dist- packages/ ubuntuone/ syncdaemon/ states. py", line 73, in next G_WITH_ CONTQ can't handle the SYS_SERVER_ RESCAN_ DONE event SyncDaemon. State - DEBUG - G_WITH_ CONTQ --[SYS_ SERVER_ RESCAN_ DONE]-- > UNKNOWN_ERROR
> Public bug reported:
>
> After first installing ubuntuone-client, I had quite a lot (~ 1.5 GB) to
> upload. While the client was "Working", it got disconnected for 10
> seconds (I didn't see this happen, but concluded it from checking
> syncdaemon.log).
>
> Then, when it had reconnected and authenticated, it went to the
> SCANNING_WITH_BOTHQ state, but got disconnected again, so it when to
> START_CONNECTIN
>
> But, while it was in START_CONNECTIN
> SYS_SERVER_
> went wrong...
>
> Since that SYS_SERVER_
> to UNKNOWN_ERROR, and got stuck there - I suspect that's due to Bug
> #376143.
>
> I don't think this is a duplicate of Bug #376143, since getting stuck in
> UNKNOWN_ERROR is the end result, not the cause of the problem.
>
> Here's the relevant log snippet, see the attachment for the full log:
>
> 2009-07-15 12:47:45,296 - ubuntuone.
> Traceback (most recent call last):
> File "/usr/lib/
> next_state = self.state.
> File "/usr/lib/
> % (self.name, event))
> BadTransition: State START_CONNECTIN
>
> 2009-07-15 12:47:45,340 - ubuntuone.
> START_CONNECTIN
>
> ** Affects: ubuntuone-client
> Importance: Undecided
> Status: New
>
thanks for your great report! While I get round to fixing the issue
(shortly!), restarting the syncdaemon should have everything just work
again.
assignee chipaca
status confirmed
importance medium