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.
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')
Any ideas or further information needed?
Mathieu Trudel-Lapierre <mathieu...@gmail.com>
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
