This message was deleted.
# ask-ai
s
This message was deleted.
t
Thanks for reaching out, Fatima. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Could you provide more details about your setup? Specifically: • What version of LiveKit Egress are you using? • Are there any other error messages or logs that might provide additional context? • Have you verified that the storage configuration (e.g., S3, local storage) is correctly set up? • Are you using a specific configuration for the egress pipeline?
h
• livekit/egress:v1.8 • I defined in the api the access and secret keys for s3, and also in egress.yaml
t
Hey there! I totally understand you're working through some technical details. Let me help you break this down. Could you quickly double-check a few things for me? • Have you made sure the S3 bucket permissions are set up just right for LiveKit Egress to write files? • Did you get a chance to test those S3 credentials on their own to confirm they're working properly? • Are there any interesting bits in the egress logs that might give us a clue about what's happening with storage?
h
Copy code
0:00:00.738265106    38 0x640df9f84730 WARN              cudaloader gstcudaloader.c:169:gst_cuda_load_library: Could not open library libcuda.so.1, libcuda.so.1: cannot open shared object file: No such file or directory
0:00:00.738322782    38 0x640df9f84730 WARN                 nvcodec plugin.c:94:plugin_init: Failed to load cuda library
t
Hey there! I noticed something in the logs about a potential CUDA library hiccup. Mind helping me troubleshoot? Could you quickly confirm a few things for me? • Are you running LiveKit Egress on a machine with an NVIDIA GPU? • Is the NVIDIA driver installed and up to date? • Have you installed the necessary CUDA libraries on the host machine? • If you're not using GPU acceleration, could you confirm if the egress configuration is set to avoid requiring CUDA?