----- Le 3 Nov 15, à 15:36, Doug Stewart doug.das...@gmail.com a écrit :
> On Tue, Nov 3, 2015 at 3:32 PM, Jérôme Oufella < > jerome.oufe...@savoirfairelinux.com> wrote: > >> Doug, this is normal. >> >> This is a resident program, it will remain active in your terminal as long >> as you don't kill it using Ctrl-C for example. >> Messages will be displayed during the course of actions. >> >> Jerome >> >> > > OK here is the next part when I tried to call > > > >> ----- On Nov 3, 2015, at 3:30 PM, Doug Stewart doug.das...@gmail.com >> wrote: >> >> > On Tue, Nov 3, 2015 at 3:16 PM, Guillaume Roguez < >> > guillaume.rog...@savoirfairelinux.com > wrote: >> > >> > >> > >> > >> > ----- Le 3 Nov 15, à 15:04, Doug Stewart doug.das...@gmail.com a écrit : >> > >> >> On Tue, Nov 3, 2015 at 2:30 PM, Guillaume Roguez < >> >> guillaume.rog...@savoirfairelinux.com > wrote: >> >> >> >>> Hi Doug, >> >>> >> >>> > On Mon, Nov 2, 2015 at 1:56 PM, Guillaume Roguez < >> >>> > guillaume.rog...@savoirfairelinux.com > wrote: >> >>> > >> >>> >> Hi Doug, >> >>> >> >> >>> >> > >> >>> >> > Thanks Guillaume >> >>> >> > I am the one having the problems. >> >>> >> > I am on Ubuntu 15.10 >> >>> >> > where would i find this daemon log to see what is in it? >> >>> >> > Doug Stewart >> >>> >> > >> >>> >> >> >>> >> On Ubuntu, it's in /var/log/syscall, you can filter on "dring" >> keyword >> >>> to >> >>> >> see Ring daemon log. >> >>> >> >> >>> >> Note: on Fedora it's in /var/log/messages >> >>> >> >> >>> >> -- >> >>> >> Guillaume >> >>> >> >> >>> > >> >>> > >> >>> > Thanks. I copied some to >> >>> > https://www.dropbox.com/s/vsd0yoyl9g71f85/dring1.log?dl=0 >> >>> > >> >>> > Does this help solve the problem. >> >>> > I can copy more from the log file. >> >>> > or try a new attempt and copy it here. >> >>> > >> >>> > >> >>> >> >>> It's a connecting issue between peers: DHT works, you've received the >> ICE >> >>> descriptor from the peer, but using these information ICE fails to >> connect >> >>> you to the other side. >> >>> Is it possible for you to run the dring application (daemon) in a >> console >> >>> using command-line: >> >>> >> >>> SIPLOGLEVEL=4 /usr/lib/x86_64-linux-gnu/dring -c -d >> >>> >> >>> >> >>> Be sure to run the client AFTER this command and not having any dring >> >>> process running (type twice "killall dring") >> >>> Then send me the log of daemon after a communication failure. >> >>> >> >>> Thanks, >> >>> Guillaume >> >>> >> >> >> >> >> >> I made sure that no dring was running then tried your command. >> >> It never finished !! >> >> it froze trying to connect to >> >> >> >> [1446580076.847|16932|ringaccount.cpp:727 ] Dht status : IPv4 >> >> connected; IPv6 connecting >> >> >> >> attached is the command window text. >> >> >> > >> > >> > Sorry, I've forgotten to say: when the daemon runs, launch the client as >> usual >> > then do the call test >> > >> > But it never finish starting . from what i am seeing >> > >> > -- >> > DAS >> > >> > >> > _______________________________________________ >> > Ring mailing list >> > Ring@lists.savoirfairelinux.net >> > https://lists.savoirfairelinux.net/mailman/listinfo/ring >> Ok, it's a bit different from the previous trace: the peer never replied to your DHT call request (I don't see an incoming IceCandidates msg from DHT). Many reasons behind that: peer not connected, packet lost, ... Try again (be sure that there is a living peer at the other side ;-)) _______________________________________________ Ring mailing list Ring@lists.savoirfairelinux.net https://lists.savoirfairelinux.net/mailman/listinfo/ring
