From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: Logging
Date: Fri, 08 Jan 2021 13:40:27 +0100 [thread overview]
Message-ID: <87wnwnha9w.fsf@toke.dk> (raw)
In-Reply-To: <875z485swt.wl-jch@irif.fr>
Juliusz Chroboczek <jch@irif.fr> writes:
> It turns out that Pion's logging is controlled by environment variables.
> This is described here:
>
> https://github.com/pion/webrtc/wiki/Debugging-WebRTC
>
> Galène could potentially:
>
> - set the environment variables;
> - hook into Pion's internals to redirect the log somewhere (to a web page?).
>
> Opinions?
I just tried setting PIONS_LOG_INFO=ice and restarting. Which got me
this:
an 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Setting new connection state: Checking
Jan 08 12:35:14 video galene[532657]: ice WARNING: 2021/01/08 12:35:14 pingAllCandidates called with no candidate pairs. Connection is not possible yet.
Jan 08 12:35:14 video galene[532657]: ice WARNING: 2021/01/08 12:35:14 pingAllCandidates called with no candidate pairs. Connection is not possible yet.
Jan 08 12:35:14 video galene[532657]: ice WARNING: 2021/01/08 12:35:14 pingAllCandidates called with no candidate pairs. Connection is not possible yet.
Jan 08 12:35:14 video galene[532657]: ice WARNING: 2021/01/08 12:35:14 pingAllCandidates called with no candidate pairs. Connection is not possible yet.
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 45.145.xx.xx:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 10.36.yy.yy:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp6 host 2a0c:4d80:zz:zz::2:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 45.145.xx.xx:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 10.36.yy.yy:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp6 host 2a0c:4d80:zz:zz::2:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 45.145.xx.xx:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 10.36.yy.yy:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp6 host 2a0c:4d80:zz:zz::2:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 45.145.xx.xx:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp4 host 10.36.yy.yy:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Ignoring remote candidate with tcpType active: tcp6 host 2a0c:4d80:zz:zz::2:9
Jan 08 12:35:14 video galene[532657]: ice INFO: 2021/01/08 12:35:14 Setting new connection state: Connected
Jan 08 12:35:54 video galene[532657]: ice INFO: 2021/01/08 12:35:54 Setting new connection state: Closed
Which doesn't really tell me much. What's happening here, is the Turn
server working? What's with the remote candidates being ignored?
What would be most useful in terms of checking configuration is if
Galene would *on startup* emit something like:
Checking Turn server candidate turn.example.com:443?transport=tcp: success!
for each configured TURN server.
-Toke
next prev parent reply other threads:[~2021-01-08 12:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:38 [Galene] Logging Juliusz Chroboczek
2021-01-07 22:45 ` [Galene] Logging Michael Ströder
2021-01-08 0:35 ` Antonin Décimo
2021-01-08 12:40 ` Toke Høiland-Jørgensen [this message]
2021-01-08 13:28 ` Juliusz Chroboczek
2021-01-08 13:52 ` Toke Høiland-Jørgensen
2021-01-08 14:33 ` Michael Ströder
2021-01-08 15:13 ` Juliusz Chroboczek
2021-01-08 17:34 ` Michael Ströder
2021-01-08 18:00 ` Juliusz Chroboczek
2021-01-08 15:34 ` Juliusz Chroboczek
2021-01-08 19:34 ` Toke Høiland-Jørgensen
2021-01-08 19:56 ` Juliusz Chroboczek
2021-01-09 0:18 ` Toke Høiland-Jørgensen
2021-01-09 13:34 ` Juliusz Chroboczek
2021-01-10 13:47 ` Toke Høiland-Jørgensen
2021-01-10 15:14 ` [Galene] Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-10 15:23 ` [Galene] " Juliusz Chroboczek
2021-01-10 22:23 ` Toke Høiland-Jørgensen
2021-01-10 22:44 ` Dave Taht
2021-01-11 0:07 ` Juliusz Chroboczek
2021-01-11 0:20 ` Toke Høiland-Jørgensen
2021-01-11 0:28 ` Juliusz Chroboczek
2021-01-11 0:30 ` Dave Taht
2021-01-11 6:23 ` Dave Taht
2021-01-11 12:55 ` [Galene] Multichannel audio [was: Congestion control...] Juliusz Chroboczek
2021-01-11 17:25 ` [Galene] " Dave Taht
2021-01-11 13:38 ` [Galene] Re: Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-11 15:17 ` Toke Høiland-Jørgensen
2021-01-11 17:20 ` Dave Taht
2021-01-12 1:38 ` Juliusz Chroboczek
2021-01-10 15:17 ` [Galene] Re: Logging Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnwnha9w.fsf@toke.dk \
--to=toke@toke.dk \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--subject='[Galene] Re: Logging' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox