dazzling-truck-32153
09/13/2025, 7:33 PMtall-airline-16756
09/13/2025, 7:33 PMtall-airline-16756
09/13/2025, 7:33 PMlibcuda.so.1
is included in your system’s library path.
• It’s also a good idea to update your NVIDIA driver to a version that supports at least CUDA 11.0.
• Try using tools like nvidia-smi
to see if your GPU is available and not being used by other processes.
For VAAPI:
• Make sure you have the required libraries and drivers installed, such as libva-dev
, libva-drm2
, and libdrm-dev
.
• Check that you have access to the render device (like /dev/dri/renderD128
) and that your user permissions allow this.
• Running vainfo
can help confirm if VAAPI is properly initialized and if encoding support is available.
If you’re still running into issues after these steps, it might help to look at your system logs and LiveKit runtime logs for more detailed messages. Feel free to share those with me, and we can troubleshoot further together!
Sources: webrtc-sys/src/vaapi/vaapi_display_drm.hdazzling-truck-32153
09/13/2025, 7:34 PMdazzling-truck-32153
09/13/2025, 7:34 PMtall-airline-16756
09/13/2025, 7:34 PMdazzling-truck-32153
09/13/2025, 7:34 PMtall-airline-16756
09/13/2025, 7:35 PMcuDriverGetVersion
.
2. Monitor and Collect Logs:
• Try using the LiveKit CLI to monitor the agent status and collect logs. For example, running lk agent logs
will let you follow runtime logs in real-time.
• Also, enabling debug logging by setting the log level to 'debug' can provide more detailed insights.
3. Review Specific Error Messages:
• Take a look at the error codes returned by CUDA APIs or NVENC (NVIDIA Encoder) — these often give valuable clues.
4. Check GPU and CUDA Context Initialization:
• Make sure the CUDA context is properly initialized with cuInit
and that a valid device is selected with cuDeviceGet
.
• Also, confirm that a CUDA context is successfully created with cuCtxCreate
.
5. External Monitoring Integration:
• If you want, you might consider forwarding runtime logs to external monitoring services like Datadog for more advanced analytics.
If you find that the issue is still there after these steps, please don’t hesitate to share more details with us — things like the specific error messages, project ID, or room ID will really help us dig deeper and assist you better.
Sources: Deploying to production | LiveKit Docs | Log collection | LiveKit Docs | client/web/.github/ISSUE_TEMPLATE/bug_report.yaml | Community & Support | livekit/livekit_composite | DeepWiki | webrtc-sys/src/nvidia/NvCodec/include/nvEncodeAPI.hrefined-appointment-81829
09/15/2025, 8:20 PMdazzling-truck-32153
09/15/2025, 9:37 PMsteep-mechanic-38687
09/24/2025, 3:04 PMfrom livekit.plugins.turn_detector.multilingual import MultilingualModel
turn detector and I am seeing the same error in my livekit cloud agent (might be unrelated, not sure).
But since I am using a transformer based detector, I assume the GPU is needed. Should I ignore that error?refined-appointment-81829
09/24/2025, 3:59 PMrefined-appointment-81829
09/24/2025, 4:00 PMsteep-mechanic-38687
09/25/2025, 9:14 AMrefined-appointment-81829
09/25/2025, 1:10 PMrefined-appointment-81829
09/25/2025, 1:11 PMsteep-mechanic-38687
09/25/2025, 1:16 PM