Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Logging
Date: Fri, 08 Jan 2021 14:52:21 +0100	[thread overview]
Message-ID: <87turrh6y2.fsf@toke.dk> (raw)
In-Reply-To: <87v9c77e20.wl-jch@irif.fr>

Juliusz Chroboczek <jch@irif.fr> writes:

>> Which doesn't really tell me much. What's happening here, is the Turn
>> server working?
>
> The direct connection was successful, so the TURN server was never
> contacted.

Right, I see. What are the conditions where a direct connection fails?
Is it just when the client is behind a NAT?

>> What's with the remote candidates being ignored?
>
> They're active TCP candidates, and I've disabled support for ICE-TCP in Galène:
>
>   https://github.com/pion/webrtc/issues/1356
>
> ICE-TCP has the potential to make TURN redundant, so it would greatly
> simplify the deployment of Galène.  Unfortunately, I've found it to be
> unreliable in Pion, so I've disabled it until I can find the time to work
> out what the issue is.

Right, gotcha.

>> 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!
>
> Ah. What you want is not logging, but active monitoring.

Well, both, ideally :)
As for just logging, Galene does propagate JSON parsing errors from the
Go JSON parser, but because the files are not read on startup you can
start up the daemon and everything looks fine until someone tries to
connect...

> Could you please file an issue?

Sure: https://github.com/jech/galene/issues/30

-Toke

  reply	other threads:[~2021-01-08 13:52 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
2021-01-08 13:28   ` Juliusz Chroboczek
2021-01-08 13:52     ` Toke Høiland-Jørgensen [this message]
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=87turrh6y2.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox