Re: [Fwd: Re: status of network data provider]



On Sat, Feb 16, 2008 at 1:08 AM, Zsolt Barat <zsolt softmonsters com> wrote:
> John Stowers schrieb:
>
>
> >>  >
>  >>  hi, thanks for your reply,
>  >>  im using conduit vers. 0.3.6 and tomboy 0.8.2 but is tried also conduit
>  >>  from latest svn.
>  >>  avahi 0.6.22-r1, python2.5.1-r5 . all on gentoo.
>  >>  thats the way i tried to sync:
>  >>  i put tomboy dataprovider in connection to the network dataprovider on
>  >>  both machines. i tried also the reverse. so what happens is that the
>  >>
>  >
>  > <snip>
>  >
>  >
>  >>  >
>  >>  > Machine 1
>  >>  > Tomboy --> Network
>  >>  >
>  >>  > Machine 2
>  >>  > Network <--> Tomboy
>  >>  > Then start the sync
>  >>
>  >
>  > I am so sorry, I explained this wrongly!
>  >
>  > Machine 1 (what your screenshot shows)
>  > Tomboy --> Network
>  >
>  > Machine 2
>  > You should see in your logs that it detects machine 1 has shared a
>  > dataprovider. A new category is then created in the list of data
>  > providers on the list. The name of this category is the name of
>  > Machine 1. This category contains all dataproviders currently shared
>  > (connected --> Network) on Machine 1. There should be Tomboy in this
>  > list. Drag it to the canvas and connect it to a regular Tomboy
>  > Tomboy from Machine 1 <--> Tomboy
>  > Then start the sync
>  >
>  > Both machines must be running the same Conduit version. If this doesnt
>  > work can you please file a bug with the logs from both machines
>  > attached please.
>  >
>  > Regards, sorry I put you wrong
>  >
>  >
>  hi john,
>  nevermind...
>  thanks for your detailed explanation, but sadly this doesn't work here.
>  this new category is not created. see the attached logs for details.
>  proto1 is the workstation where i try to share my tomboy notes from and
>  lisabook is my laptop. i disabled ipv6 in avahi because i thought it
>  could be prob, but nothing has changed.

Hmm, this part looks interesting

(XMLRPCUtils.py:185)
[modules.Network     ][DEBUG  ] Resolved conduit service lisabook on
lisabook.local - 192.168.10.37:3400
Extra Info: ['version=0.3.6'] (Peers.py:242)
[modules.Network     ][DEBUG  ] Remote host 'lisabook.local' detected
(Client.py:48)
[modules.Network     ][DEBUG  ] Resolved conduit service proto1 on
proto1.local - 192.168.10.15:3400
Extra Info: ['version=0.3.6'] (Peers.py:242)
[modules.Network     ][DEBUG  ] Remote host 'proto1.local' detected
(Client.py:48)
[modules.Network     ][DEBUG  ] Remote host 'lisabook' removed (Client.py:72)
[modules.Network     ][DEBUG  ] Resolved conduit service lisabook on
lisabook.local - 192.168.10.28:3400
Extra Info: ['version=0.3.6'] (Peers.py:242)

3 IP addresses, for two computers, on the same subnet. I think Conduit
detects lisabook on .37,  then immediately detects it again on .28,
deletes the first one, and then does this in a loop for ever.

Thoughts?

John

>
>  best regards
>
>  zsolt
>
>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]