Stuck in UNKNOWN_ERROR state after receiving SYS_SERVER_RESCAN_DONE event when in START_CONNECTING_WITH_CONTQ state

[Pieter Leclerc]

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_CONNECTING_WITH_CONTQ to try and reconnect.

But, while it was in START_CONNECTING_WITH_CONTQ, it got at SYS_SERVER_RESCAN_DONE from the SCANNING_WITH_BOTHQ, and that's where it went wrong...

Since that SYS_SERVER_RESCAN_DONE was unexpected at that point, it went 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.SyncDaemon.State - ERROR - START_CONNECTING_WITH_CONTQ --[SYS_SERVER_RESCAN_DONE]--> ERROR!!!
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/state.py", line 52, in handle_default
    next_state = self.state.next(event)
  File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/states.py", line 73, in next
    % (self.name, event))
BadTransition: State START_CONNECTING_WITH_CONTQ can't handle the SYS_SERVER_RESCAN_DONE event

2009-07-15 12:47:45,340 - ubuntuone.SyncDaemon.State - DEBUG - START_CONNECTING_WITH_CONTQ --[SYS_SERVER_RESCAN_DONE]--> UNKNOWN_ERROR

[John Lenton (chipaca)]

On Wed, Jul 15, 2009 at 12:41:43PM -0000, Tom wrote:
> 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_CONNECTING_WITH_CONTQ to try and reconnect.
>
> But, while it was in START_CONNECTING_WITH_CONTQ, it got at
> SYS_SERVER_RESCAN_DONE from the SCANNING_WITH_BOTHQ, and that's where it
> went wrong...
>
> Since that SYS_SERVER_RESCAN_DONE was unexpected at that point, it went
> 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.SyncDaemon.State - ERROR - START_CONNECTING_WITH_CONTQ --[SYS_SERVER_RESCAN_DONE]--> ERROR!!!
> Traceback (most recent call last):
> File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/state.py", line 52, in handle_default
> next_state = self.state.next(event)
> File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/states.py", line 73, in next
> % (self.name, event))
> BadTransition: State START_CONNECTING_WITH_CONTQ can't handle the SYS_SERVER_RESCAN_DONE event
>
> 2009-07-15 12:47:45,340 - ubuntuone.SyncDaemon.State - DEBUG -
> START_CONNECTING_WITH_CONTQ --[SYS_SERVER_RESCAN_DONE]--> UNKNOWN_ERROR
>
> ** 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

[Pieter Leclerc (pieterleclerc-deactivatedaccount)]

My pleasure !
I just noticed this bug is very similar (but not equal) to Bug #396720.

[Ken VanDine (ken-vandine)]

I am seeing this bug as well with 0.90.4+r94-0ubuntu1~ppa1~karmic

Restarting doesn't seem to help