On 06/04/2011 08:59 PM, Mathieu Trudel-Lapierre wrote:
> Hi,
>
> Here I'm reporting an issue I got from the Debian bugs for congruity.
> For reference, that's http://bugs.debian.org/584896.
>
> Apparently congruity tries to do the "Reconnect to Remote" task right
> after "Verify Upgrade". This yields a failure, because it seems like
> the 785 restarts after "Verify Upgrade" as isn't yet ready to answer
> to new connections. It's been suggested by the reporter to just wait a
> bit in congruity before reconnecting.
Unless something is broken, congruity attempts to connect 60 times, with
a 1 second delay between each try. The remote shouldn't take that long
to reboot...
Does the user see the problem immediately, or after this ~60s delay?
> This is the error message:
>
> Unknown error
> (libconcord function reset_remote error -19)
>
> Traceback (most recent call last):
> File "/usr/bin/congruity", line 702, in _WorkerFunction
> self._WorkerFunctionBody()
> File "/usr/bin/congruity", line 862, in _WorkerFunctionBody
> libconcord.reset_remote()
> File "/usr/lib/python2.6/dist-packages/libconcord.py", line 97, in __call__
> raise LibConcordException(self.func_name, result)
> LibConcordException: libconcord function 'reset_remote' failed with
> error code -19 ('Unknown error')
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
