Recording is not working on v2.17

Hi,

I have setup openvidu to save recording to s3 and Im trying to run a test session from openvidu inspector to test the recording functionality of openvidu but I have had no luck. It returns “error 500”.

Below you can find the logs of the session:

11:02:54.753

INFO

REST API: POST /openvidu/api/recordings/start {session=ses_QkeEjjrbKL, name=RecordingTest}

11:02:54.881

INFO

New recording id (ses_QkeEjjrbKL) and final name (RecordingTest)

11:02:54.881

INFO

Incremented active recordings in Media Node media_i-03b9e201f6e2ce92e. Currently: [ses_QkeEjjrbKL=ses_QkeEjjrbKL]

11:02:54.882

INFO

Starting composed (video + audio) recording ses_QkeEjjrbKL of session ses_QkeEjjrbKL

11:02:54.891

INFO

{“id”:“ses_QkeEjjrbKL”,“object”:“recording”,“name”:“RecordingTest”,“outputMode”:“COMPOSED”,“resolution”:“1920x1080”,“recordingLayout”:“BEST_FIT”,“sessionId”:“ses_QkeEjjrbKL”,“uniqueSessionId”:“ses_QkeEjjrbKL_1632211365971”,“mediaNode”:“media_i-03b9e201f6e2ce92e”,“createdAt”:1632211374882,“size”:0,“duration”:0.0,“url”:null,“hasAudio”:true,“hasVideo”:true,“status”:“started”}

11:02:54.891

INFO

Recorder connecting to url OpenVidu Inspector

11:02:54.896

INFO

Running container ‘openvidu/openvidu-recording:2.17.0’ in 172.31.35.26

11:02:54.898

INFO

Media Node Controller HTTP-POST request: POST http://172.31.35.26:3000/media-node/ HTTP/1.1

11:02:54.914

ERROR

Recording start failed for session ses_QkeEjjrbKL: Couldn’t initialize recording container. Error: status code: 500, reason phrase: Internal Server Error

11:02:54.924

ERROR

Couldn’t overwrite file /opt/openvidu/recordings/ses_QkeEjjrbKL/.recording.ses_QkeEjjrbKL. Error: /opt/openvidu/recordings/ses_QkeEjjrbKL/.recording.ses_QkeEjjrbKL (No such file or directory)

11:02:54.924

INFO

Stopping composed (video + audio) recording ses_QkeEjjrbKL of session ses_QkeEjjrbKL. Reason: null

11:02:54.925

INFO

Decremented active recordings in Media Node media_i-03b9e201f6e2ce92e. Remaining: []

Below you find part of the openvidu configuration file:

OPENVIDU_PRO_RECORDING_STORAGE=s3

OPENVIDU_PRO_AWS_S3_BUCKET=waavia-openvidu-recordings

#OPENVIDU_PRO_AWS_S3_HEADERS=

OPENVIDU_PRO_AWS_ACCESS_KEY=

OPENVIDU_PRO_AWS_SECRET_KEY=

OPENVIDU_PRO_AWS_REGION=eu-central-1

OPENVIDU_RECORDING=true

OPENVIDU_RECORDING_DEBUG=true

OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings/

OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout/

OPENVIDU_RECORDING_PUBLIC_ACCESS=false

OPENVIDU_RECORDING_NOTIFICATION=all

OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120

For the record I have executed docker ps -a (on the openvidu server) while I was trying to start the recording and there was no relevant container running at that time.

We need more information to help you.

  1. How did you deployed? Are you using AWS deployment or On Premise deployment?
  2. Did you upgraded the infrastructure.

Please send us this information:
Master Node:

  • Content of /opt/openvidu/.env and /opt/openvidu/docker-compose.yml
    Media Node:
  • Content of /opt/kms/docker-compose.yml

Regards

1: Yes I deployed on AWS.
2: Yes I have upgraded openvidu from v2.12 to v2.17.

Below you can find a link to a zip containing all the files you requested:
https://we.tl/t-A5ypH0ade0

For the record the ec2 instance that Im running openvidu has the relevant permissions (through it’s role) to write to s3.

I think is better to reinstall latest version (2.20) from scratch to avoid any of issues with upgrading process.