We got a recoding issue in AWS. And the error logs was shown as below.
io.openvidu.server.pro.recording.MedianNodeRecordingDownloader - File located at http://100.100.1.203:3000/media-node/recordings/SessionA/SessionA.mp4 successfully deleted Exception in thread "Thread-13" io.openvidu.client.OpenViduException: There was an error generating the metadata report file for the recording: /opt/openvidu/recordings/SessionA/SessionA.info (No such file or directory). Code: 702 at io.openvidu.server.recording.service.ComposedRecordingService.updateRecordingAttributes(ComposedRecordingService.java:432) at io.openvidu.server.recording.service.ComposedRecordingService.lambda$downloadComposedRecording$2(ComposedRecordingService.java:590) at io.openvidu.server.pro.recording.MedianNodeRecordingDownloader$2.run(MedianNodeRecordingDownloader.java:170)
It seems that we didn’t create directory(/opt/openvidu/recordings) correctly. But, in actually, the directory was exist as following.
/opt/openvidu# ls beats certificates custom-layout docker-compose.override.yml elasticsearch kurento-logs owncert cdr cluster custom-nginx-vhosts docker-compose.yml kms-crashes openvidu recordings
Besides, our config setting was shown as below.
# Whether to enable recording module or not OPENVIDU_RECORDING=true # Use recording module with debug mode. OPENVIDU_RECORDING_DEBUG=false # Openvidu Folder Record used for save the openvidu recording videos. Change it # with the folder you want to use from your host. OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings # System path where OpenVidu Server should look for custom recording layouts OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout # if true any client can connect to # https://OPENVIDU_SERVER_IP:OPENVIDU_PORT/recordings/any_session_file.mp4 # and access any recorded video file. If false this path will be secured with # OPENVIDU_SECRET param just as OpenVidu Server dashboard at # https://OPENVIDU_SERVER_IP:OPENVIDU_PORT # Values: true | false OPENVIDU_RECORDING_PUBLIC_ACCESS=true