On Do, 2011-01-06 at 03:19 +0000, John Dykstra wrote:
> I've started getting an error message I don't understand when trying to
> sync between two peers:
> 
>         j...@maple ~ $ syncevolution --sync refresh-from-server 
> redwood-server todo
>         [INFO] pat: inactive
>         [INFO] personal-projects: inactive
>         [INFO] work-calendar: inactive
>         [INFO] personal-blocked: inactive
>         [INFO] events: inactive
>         [INFO] memo: inactive
>         [INFO] work-blocked: inactive
>         [INFO] addressbook: inactive
>         [INFO] commute: inactive
>         [INFO] calendar: inactive
>         [INFO] work: inactive
>         [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via 
> libsoup: D-Bus server done
>         ^X[INFO] SyncContext: resend previous request #1
>         [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via 
> libsoup: D-Bus server done
>         ^[[1;5D^[[1;5D[INFO] SyncContext: resend previous request #1
>         [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via 
> libsoup: D-Bus server done
>         
> The SoupTransport error messages repeat until SE gives up.  The same
> thing happens no matter which source (or all) I try to sync.  The same
> thing also occurs if I try a --sync refresh-from-server.
> 
> This is an SE 1.1 client talking to an SE 1.1 server, which is using the
> Evolution backends.  The log on the server side shows _two_ _successful_
> sessions for each "SoupTransport Failure" message on the client side.
> 
> These two peers were syncing with each other yesterday.  The change I
> mad this morning was to add a source to the configuration on both sides.
> However, that source is not involved in the above attempt.
> 
> Can anyone suggest where to look to troubleshoot this problem?

     1. use the improved syncevo-http-server.py script from master on
        the server (can be combined with the existing 1.1.1 (!)
        installation - please update from 1.1 to 1.1.1):
        
http://meego.gitorious.com/meego-middleware/syncevolution/blobs/raw/master/test/syncevo-http-server.py
     2. run it with -d to get the full output
     3. check for anything suspicious, or send it to me (directly,
        probably too large for the list)


-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to