-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Egress not stopping RoomComposite recording correctly. Only end by sending CTRL-C or SIGINT #815
Comments
This is tested on Debian 12, go 1.23.2, livekit release 1.8.0, and egress tag 1.8.6. It was working until a an update... I will rollback as much as possible and update here. |
Still didn't found the right direction but the #817 may solve it... |
Finally solving it by "manually" closing the egress, but originally it was closing automatically on room disconnect |
When using your docker image here : https://hub.docker.com/r/livekit/egress/ I guess we must use Ubuntu as OS ? |
I'm using the latest version to stop room compounding by closing the room, hoping there's an elegant way to stop it. I am using ubuntu system. |
Hi @AutoScrape123TX |
@andrei-svistunou I use the default template. After digging, I found that the cause may be the participant's track not being correctly unpublished and you close the room before the unpublishing events reach egress. I ended up using a manual recording process. |
Describe the bug
Egress dont stop the records of the room composite if I dont manually stop the docker process.
Once the room end, the room composite is still recording empty data.
But it do records/stop individual tracks correctly when I also add
AutoTrackEgress
to the room creation requestEgress Version
Last git pull with commit c0e88d9
Egress Request
Additional context
The room composite is not ended until I manually close the docker process. But the individual tracks are correctly exported.
Logs
The text was updated successfully, but these errors were encountered: