facing unusual behavior where recording will not happening, and in inspector it shows “stopped” and will not show play or download button (only delete button appears). Do not know what at what point this issue happens.
I am using s3 bucket and Openvidu 2.16 version and manual recording when I receive the Webhook event participantJoined.
On restart of Openvidu it starts working normally but we are loosing the recordings of sessions before restart.
This could be caused of an Exception in OpenVidu which keep the system failing after that. Could you reproduce this issue again and send the logs of OpenVidu Server Pro in this specific moment?
If you can reproduce the problem you can easily get the logs by using:
sudo su
cd /opt/openvidu
./openvidu logs
Alternatively you can reproduce the error and give us your Kibana credentials so we can check the logs.
We could not able to manually reproduce this issue as we do not know when this happens. Let me try to check in kibana if I could fetch the logs when it happened today.
[WARN] 2021-02-01 15:53:32,081 [SessionHandler-qt0npubb8cddmh81jv6nn6cra3-e400-t0] io.openvidu.server.rpc.RpcHandler - Error getting address location: The address ..*. is not in the database
[ERROR] 2021-02-01 15:53:31,417 [http-nio-0.0.0.0-5443-exec-7] io.openvidu.server.pro.recording.service.RecordingManagerUtilsS3 - AmazonServiceException when listing objects from bucket ******. S3 couldn’t process the call: The provided token has expired.
Your error is related with short-lived credentials. Presigned S3 URLs or IAM Users with rotation are not supported in OpenVidu Pro. Possible solutions:
You need to create an AWS user which have access to the S3 bucket which does not expire, and put its credentials in OPENVIDU_PRO_AWS_ACCESS_KEY and OPENVIDU_PRO_AWS_SECRET_KEY
Another possible solution is to modify the role of your EC2 instance to have access to your bucket: OpenVidu Pro S3 Upload - #7 by cruizba In this way you don’t need to use OPENVIDU_PRO_AWS_ACCESS_KEY and OPENVIDU_PRO_AWS_SECRET_KEY
@cruizba is right. You have basically two options: use an AWS user-pass key pair with access to the S3 bucket, or provide AWS credentials to the machine in any way accepted by the default credentials provider (OpenVidu Server Pro will automatically use that provider to initialize the internal AWS SDK)