https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
a
What versions are you running? I received another report of this last week which I could not reproduce on the latest
s
I am using 1.4.2
@able-gigabyte-21598 Some additional information: In the logs I can see that livekit only sends 
engress_end
after 
room_finished
webhook event has been handled. So until 
room_finished
event isn’t processed it doesn’t even try to send 
egress_end
. Also I can in the logs that 
track egress
participants only leaves the room after the room finished and not after the connected participant left.
Copy code
2023-05-15T17:15:36.307Z INFO livekit service/roommanager.go:113 deleting room state {"room": "8f5vbht4ilwlqaqq"}

2023-05-15T17:15:36.309Z INFO livekit service/roommanager.go:455 room closed {"room": "8f5vbht4ilwlqaqq", "roomID": "RM_aqCmzcvr6x92"}

2023-05-15T17:15:36.322Z DEBUG livekit service/roommanager.go:493 RTC session finishing {"room": "8f5vbht4ilwlqaqq", "roomID": "RM_aqCmzcvr6x92", "participant": "EG_Z3aMaNp4QFZG", "pID": "PA_XfjCbz7J2ni6", "remote": false}

2023-05-15T17:15:36.349Z DEBUG livekit service/roommanager.go:493 RTC session finishing {"room": "8f5vbht4ilwlqaqq", "roomID": "RM_aqCmzcvr6x92", "participant": "EG_iifhfMWtYJsd", "pID": "PA_Y5GcuYEdbTCT", "remote": false}

2023/05/15 17:15:36 [DEBUG] POST XXXX/webhook

2023-05-15T17:15:36.693Z INFO livekit service/ioinfo.go:78 egress ended {"egressID": "EG_iifhfMWtYJsd"}

2023-05-15T17:15:36.813Z INFO livekit service/ioinfo.go:78 egress ended {"egressID": "EG_Z3aMaNp4QFZG"}

2023/05/15 17:16:05 [DEBUG] POST XXXX/webhook (status: 504): retrying in 1s (4 left)
.....
2023/05/15 17:17:39 [DEBUG] POST XXXX/webhook (status: 504): retrying in 8s (1 left)

2023-05-15T17:18:16.451Z WARN livekit webhook/url_notifier.go:70 failed to send webhook {"url": "XXXX/webhook", "event": "room_finished", "error": "POST XXXX/webhook giving up after 5 attempt(s)"}

2023/05/15 17:18:16 [DEBUG] POST XXXX/webhook

2023-05-15T17:18:16.599Z INFO livekit webhook/url_notifier.go:73 sent webhook {"url": "XXXX/webhook", "event": "egress_ended"}

2023/05/15 17:18:16 [DEBUG] POST XXXX/webhook

2023-05-15T17:18:16.705Z INFO livekit webhook/url_notifier.go:73 sent webhook {"url": "XXXX/webhook", "event": "egress_ended"}
a
I’ve added tests that confirm that if the room continues, the track egress participants leave and the 
egress_ended
event is sent without waiting for the room to close. If the egress and the room end at the same time, we don’t make any guarantees about the ordering of the events. The egress service needs to do things like wait for any dropped packets, close out the pipeline, and upload files, which might take a bit of extra time
2 Views
Open in Slack
PreviousNext
Powered by