This message was deleted.
# helpdesk
s
This message was deleted.
s
Also I have a question about some failed egresses
Copy code
| EG_DArVa85Mwjrz | EGRESS_FAILED   | 2023-05-17 17:34:05.53971      | pipeline frozen |
| EG_XdbPgQJFyQLZ | EGRESS_FAILED   | 2023-05-18 14:11:57.802194     | pipeline frozen |
Can you check on these? What are the reasons for pipeline frozen and what does it mean? Maybe it wasn't able to write to the storage I've provided?
Here is a screenshot from one of the session dashboards
d
hmm, that's definitely unexpected. Do you know what conditions would typically cause them to show up?
CC: @able-gigabyte-21598 re: pipeline frozen
s
Hi @dry-elephant-14928. Since it doesn't happen every time, it's hard to tell but it looks like multiple successive reconnects may help to reproduce it.
d
got it, we'll take a look to see if we can repro
s
Hi @dry-elephant-14928. Here is an additional note. Not sure if it is important. Since we don't know if someone entered the room first, each participant sends a request for room creation with egress (with configuration settings) before entering the room.
@dry-elephant-14928 Here is one more session. One of our testers experiencing often app crashes (apparently it's something on our side) during the call. She is reconnecting to the same room after that. The average duration of the session is ~7.5-8 minutes. Maybe those "ghost" participants are caused by the improper room disconnect? For context: I'm talking about our app that is written in Flutter. https://cloud.livekit.io/projects/p_519ctfqf1bf/sessions/RM_HCCsuNFSV7eT
Hi @dry-elephant-14928. Update on room creation. I've asked my coworker about how he configured room creation with egress and it turns out that he actually checks if the room already exists. So I'm not sure why it is even happening.
a
@silly-train-16715 I havenโ€™t been able to reproduce the
pipeline frozen
issue yet, but I found a few problems that might have potentially been causing it. I plan to have fixes deployed tomorrow
๐Ÿ‘ 1
s
Hi @able-gigabyte-21598. Thanks for response. Hope it'll help. I have one more question. I didn't notice at first but it turns out that there can be multiple session per one room name. It is really confusing. What are those sessions and how are they related to rooms?
I guess I figured it out. "Session" is a session that has at least one participant and ends after the last participant leaves the room. Is that right?
d
yeah
a session is an instance of the room (like classes and objects ๐Ÿ˜Š
s
Hi @able-gigabyte-21598. Any idea on those "ghost" users with egress IDs? I'm still getting those in my session dashboards. And the main cloud dashboard shows that those are considered as Go clients
As far as I understand the recording works as follows: Go client joins the room, subscribes to the track and saves it to the file. If that's true then it explains the "ghost" participants. Can you do something on a server side or change clients so they won't appear in the list of participants and SDK users won't need to filter them out?
d
ok, those are Egress bots that join the room and record them.
and you are correct that they should not be visible to clients. Egress participants have identities with prefix
EG_
, and they are joining the room as
hidden
participants
s
OK, so what is the eventual recommendation on this one? Should I, as SDK user, manually filter them out so the end users of my app doesn't see them or they should not be visible to me (as a developer) in the first place and that's something you'll fix in the future? That's an interesting concept of hidden participants. Is it possible for me to create one and if yes then how I do that? Thanks
d
You should not need to filter them out. They are visible in the dashboard, but should not be visible to your client SDK. If you are seeing them in the UI, that would mean it's a bug. Is that what you are observing in recent sessions? (we did have a bug where allowed them to slip through in some conditions. I believe we've fixed it) You can create hidden participants too (tho they cannot publish anything, otherwise they'll become visible). You'd just need to give it the
hidden
grant in their token: https://docs.livekit.io/concepts/authentication/#video-grant
s
When this bug was fixed? I didn't turn it off (just in case) when making new builds for our testers. That's why I may not have noticed the fix.
d
it was fixed about a week ago
๐Ÿ‘ 1
s
Oh, OK. That may be the case. I didn't see anything related to this in the changelog so I didn't remove the filter. I'll try removing the filter.
๐Ÿ‘ 1
d
Sounds good. if it remains an issue, please let us know. We have not gotten any recent reports for this.
๐Ÿ‘ 1