https://livekit.io logo
Join Slack
Powered by
# helpdesk
  • d
    set the channel topic: question or issues with using LiveKit
  • w
    have a quick bug to report if the backend tries to send a message to a closed socket, the whole server responds with 503s till the server is restarted
  • w
    Copy code
    <http://github.com/livekit/livekit-server/pkg/rtc.(*MediaTrack).forwardRTPWorker|github.com/livekit/livekit-server/pkg/rtc.(*MediaTrack).forwardRTPWorker>
    /workspace/pkg/rtc/mediatrack.go:292
2021-01-26T23:13:27.272Z    DEBUG    rtc/mediatrack.go:152    removing peerconnection track    {"track": "TR_rptjQ44gqBTpu5fuEMFYUW", "srcParticipant": "PA_VYiQGM2cxMgs4DN7Tipnm", "destParticipant": "PA_m32jPaCTCFyiS79P2oq4h4"}
2021-01-26T23:13:27.372Z    DEBUG    rtc/participant.go:444    starting negotiation    {"participant": "PA_m32jPaCTCFyiS79P2oq4h4"}
2021-01-26T23:13:27.373Z    DEBUG    rtc/participant.go:463    sending available offer to participant
2021-01-26T23:13:27.392Z    DEBUG    rtc/participant.go:128    ICE connection state changed    {"state": "disconnected"}
2021-01-26T23:13:27.392Z    DEBUG    rtc/participant.go:481    updating participant state    {"state": "DISCONNECTED"}
panic: send on closed channel

goroutine 1387 [running]:
<http://github.com/livekit/livekit-server/pkg/routing.(*MessageChannel).WriteMessage(0xc0004002f0|github.com/livekit/livekit-server/pkg/routing.(*MessageChannel).WriteMessage(0xc0004002f0>, 0xe77140, 0xc00018a240, 0xc0005947e0, 0xc0002b3090)
    /workspace/pkg/routing/messagechannel.go:23 +0x4c
<http://github.com/livekit/livekit-server/pkg/rtc.(*ParticipantImpl).negotiate(0xc00007c300)|github.com/livekit/livekit-server/pkg/rtc.(*ParticipantImpl).negotiate(0xc00007c300)>
    /workspace/pkg/rtc/participant.go:464 +0x41f
created by time.goFunc
    /usr/local/go/src/time/sleep.go:167 +0x4
  • w
    happens quite often where peers might disconnect abruptly
  • d
    yeah thanks for the report. I'm looking at fixing this right now
  • w
    cool beans
  • d
    🙏 for the bug reports
  • d
    are you running in multi-node
  • w
    single node
  • w
    although multi-node is set to 
    true
  • w
    if you'd rather I file bug reports on github please lmk, happy to
  • d
    thanks, slack works well for now 🙂
  • w
    sounds good
  • w
    in 
    pkg/routing/messagechannel.go
    shouldn't the message be sent asynchronously? line 23, prepend with 
    go
  • d
    would that change anything materially?
  • d
    I think the channel is still closed in that case.
  • d
    so I'm trying to figure out why it's going to a messagechannel.. in a multi-node setup, it should be going into a RedisSink
  • w
    good point, I figured the coroutine would fail silently rather than killing the main process
  • w
    I'll toggle multi-node off because we actually only have 1 node running. Would that effect anything?
  • d
    it's fine to leave multi-node on, it's something we'll have to fix either way
  • w
    ok, I'll leave it on then
  • d
    can you share the message that it prints out on startup? i.e.
    Copy code
    2021-01-26T16:32:15.186-0800	INFO	server/main.go:145	configured key provider	{"num_keys": 2}
2021-01-26T16:32:15.309-0800	INFO	server/main.go:178	using multi-node routing via redis	{"address": "localhost:6379"}
2021-01-26T16:32:15.315-0800	INFO	service/server.go:100	starting LiveKit server	{"address": ":7880", "nodeId": "ND_0000ACDE48001122"}
  • w
    yes one moment
  • w
    Copy code
    2021-01-27T00:35:02.654Z	INFO	server/main.go:145	configured key provider	{"num_keys": 1}
2021-01-27T00:35:02.821Z	INFO	server/main.go:192	using single-node routing
2021-01-27T00:35:02.822Z	INFO	service/server.go:100	starting LiveKit server	{"address": ":7880", "nodeId": "ND_0000000000000000"}
  • d
    ahh, so it looks like it's doing single node
  • d
    that's odd..
  • w
    odd, one moment, I need to change this deployment pattern
  • w
    its hard for me to change config the way its deployed
  • w
    could you enable forks on the livekit server project?
  • d
    oh def.. I didn't realize it's not enabled
12345...91Latest