https://livekit.io logo
Join Slack
Powered by
Traceback (most recent call last): File “/app/alf...
# ask-ai
g
Traceback (most recent call last): File “/app/alfin.py”, line 900, in entrypoint await lkapi.egress.start_room_composite_egress(egress_req) File “/usr/local/lib/python3.11/site-packages/livekit/api/egress_service.py”, line 41, in start_room_composite_egress return await self._client.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/usr/local/lib/python3.11/site-packages/livekit/api/twirp_client.py”, line 129, in request raise TwirpError( livekit.api.twirp_client.TwirpError: TwirpError(code=unavailable, message=twirp error unknown: no response from servers, status=503) {“pid”: 21949, “job_id”: “AJ_BB6r3TKiaARp”}
t
Thanks for reaching out, Rodrigo. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The error you're encountering, 
TwirpError
with code 
unavailable
and message 
no response from servers
, typically indicates that the server is unable to respond. This can be due to server unavailability, network issues, or rate limiting. Here are some steps to address this: 1. Check Server Availability: Ensure the server is running and accessible. Verify there are no ongoing maintenance activities or outages. 2. Review Logs: Investigate server-side logs for any internal errors or overload conditions. 3. Network Check: Test the connection to the server using tools like 
ping
or 
curl
. 4. Rate Limiting: Confirm that your client isn’t exceeding the server's request limits. 5. Implement Retries: Use exponential backoff to retry the request, allowing temporary issues to resolve. If you need further assistance, please provide additional details about your implementation, such as the specific endpoints you're accessing or any recent changes made to the server or client. Sources: livekit-api/livekit/api/twirp_client.py | errors.go | tools/server/README.md | packages/livekit-server-sdk/src/TwirpRPC.ts | livekit/livekit_room.twirp.go
g
how can I change egress server request limit on an on premise deployment
t
Hey there! If you’re looking to change the egress server request limit on your on-premise LiveKit setup, here’s a simple way to do it: 1. Find the Configuration File: The egress service uses a YAML config file. You can either point to this file using the 
EGRESS_CONFIG_FILE
environment variable or mount it directly inside your Docker container. 2. Update the Session Limits: In that YAML file, look for the 
session_limits
section and tweak the max durations to what you need. For example:
Copy code
session_limits:
  file_output_max_duration: 2h  # This sets file outputs to last up to 2 hours
  stream_output_max_duration: 4h  # This sets stream outputs to last up to 4 hours
3. Restart the Egress Service: Once you’ve made those changes, just restart the egress service so everything kicks in. If you hit any snags or want a hand with anything else, just give me a shout—I’m here to help!
Open in Slack
PreviousNext
Powered by