purple-rainbow-1246
05/12/2025, 4:17 PMDEBUG:livekit.agents:stream closed
2025-05-12 11:12:09,597 - DEBUG livekit.agents - stream closed {"participant": "roleplay_user_50664401_1483912-da70c0d1-75f8-4dac-8c30-20f713d2f76f", "source": "SOURCE_MICROPHONE"}
WARNING:livekit:livekit::rtc_engine:446:livekit::rtc_engine - received session close: "signal client closed: \"stream closed\"" UnknownReason Resume
2025-05-12 11:12:09,601 - WARNING livekit - livekit::rtc_engine:446:livekit::rtc_engine - received session close: "signal client closed: \"stream closed\"" UnknownReason Resume
DEBUG:livekit.agents:shutting down job task
2025-05-12 11:12:09,611 - DEBUG livekit.agents - shutting down job task {"reason": "", "user_initiated": false}
DEBUG:livekit.agents:job exiting
2025-05-12 11:12:09,669 - DEBUG livekit.agents - job exiting {"reason": "", "tid": 26032, "job_id": "AJ_n56zy5rALMir"}
DEBUG:livekit.agents:http_session(): closing the httpclient ctx
2025-05-12 11:12:10,138 - DEBUG livekit.agents - http_session(): closing the httpclient ctx
tall-airline-16756
05/12/2025, 4:17 PMtall-airline-16756
05/12/2025, 4:17 PMStreamError.abnormalEnd(reason: String)
indicates an abnormal closure by a remote participant.
• In the Python SDK, debug logs such as "stream closed" or "input stream detached" often include details about the participant and source, which can help identify the issue.
• When closing a stream programmatically in Python, you can specify a reason and attributes, which might clarify why the stream was closed.
• In the Android SDK, disconnect reasons like ROOM_CLOSED
or SIGNAL_CLOSE
might be relevant to sudden closures.
To further investigate, you may want to check the specific participant and source details in the logs, as well as any related error messages or reasons provided during the closure process.
Sources: Tree View: | dse-workbench | livekit.rtc.data_stream API documentation | ROOM_CLOSED | SIGNAL_CLOSE | StreamError | Documentation