Re: [Opensync-users] syncml-client problem.

[W. <ha...@pv...>]

tir, 17,.10.2006 kl. 20.13 +0200, skrev Paco Orozco:

> Hiya,
> 
> I'm newbie in this list but I'd like to have some support related with
> syncml-client.
> 
> I'm trying to use syncml-client to connect kdepim with an eGroupware
> server. This server has a  syncml server implemented.
> 
> I've seen the great job form Michael Kolmodin doing in syncml-client
> connector but I'm gettimg some errors, so I'd apreciate some help.
> 
> I've installed SVN version via Ubuntu edgy packages and syncml-client
> via SVN+compile sources.
> 
> I've created a new group like this:
> $ msynctool --showgroup prova
> Groupname: prova
> Member 1: file-sync
>         Configuration :
> <config><path>/tmp/hola</path><recursive>FALSE</recursive></config>
> 
> Member 2: syncml-client
>         Configuration : <config>
>     <gconf-uri>/apps/syncml-client</gconf-uri>
>     <object-type>calendar</object-type>
>     <sync-source-name>cal</sync-source-name>
> </config>
> 
> I've try to run msynctool and I get this error:
> $msynctool --sync prova
> Synchronizing group "prova"
> Member 1 of type file-sync just connected
> 
> ** ERROR **: file
> /tmp/buildd/libopensync-0.19+svn20061015/./opensync/opensync_group.c:
> line 814 (osync_group_get_slow_sync): assertion failed:
> (osync_objtype)
> aborting...
> Member 2 of type syncml-client had an error while connecting: Broken Pipe
> Member 1 of type file-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
> Error while synchronizing: Unable to connect one of the members
> 
> I analyze tcpdump of my host and I see a connecto to my server.
> I set debug options, but I can't see the problem. I've attached logs.tgz
> 
> What it is the problem? Can you help me?


I don't know anything about this problem or its cause. But I think that
"broken pipe" errors are mostly due to plug-in crashes.
In this case it would probably be helpful for the ones that can help you
to get a backtrace from the crash.
Try this (and adjust as needed, this is mostly from memory):

     1. Make sure that you get a core file (some distros disble this by
        default) by running "ulimit -c unlimited" in the terminal before
        the sync command.
     2. After you get "broken pipe", you should probably have a core
        file in the current directory or your home directory.
     3. Load this core file with GDB: "gdb
        <path/to/opensync>/libexec/osplugin <core.file>
     4. Type "bt" to get a backtrace.


--
Håvard Wigtil || http://wigtil.net