We installed OpenVideo Pro with 2 separate instance of KMS, After we stop the recording we get the following log. The file is missing in recording folder. What could be the issue
{“sessionId”:“ses_XZc5XYUmoP”,“timestamp”:1591394388690,“startTime”:1591394158127,“duration”:0.0,“reason”:“recordingStoppedByServer”,“id”:“ses_XZc5XYUmoP”,“name”:“ses_XZc5XYUmoP”,“outputMode”:“INDIVIDUAL”,“hasAudio”:true,“hasVideo”:true,“size”:0,“status”:“stopped”,“event”:“recordingStatusChanged”,“elastic_type”:“cdr”}http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_ZeH9_con_WT6uFMlRb6.webm http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_SWgq_con_Egv66WTMvX.webm http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_ZeH9_con_WT6uFMlRb6.webm is 0 KB in sizehttp://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_SWgq_con_Egv66WTMvX.webm is 0 KB in sizehttp://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_ZeH9_con_WT6uFMlRb6.webm http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_SWgq_con_Egv66WTMvX.webm http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_ZeH9_con_WT6uFMlRb6.webm http://10.10.12.5/recordings/ses_XZc5XYUmoP/str_CAM_SWgq_con_Egv66WTMvX.webm
Individual recordings are recorded by Kurento Media Server.
Can you share with us Kurento Media Server logs to see if there are something to guide us to the problem root?
micael.gallego:
root
Hi Micael,
I have performed fresh transaction and shared the logs of OpenVidu and KMS in dropbox
Shared with Dropbox
Thanks
Are you aware of these errors?
e[36mopenvidu-server_1 |e[0m [ERROR] 2020-06-05 23:29:52,544 [Thread-11] io.openvidu.server.pro.recording.RecordingKmsHttpDownloader - Cannot create a FileOutputStream to file /storage/openvidu/recordings/ses_U5tPs5q4tU/str_CAM_GLn4_con_C5bgp9zLvt.webm: http://10.9.208.5/recordings/ses_U5tPs5q4tU/str_CAM_GLn4_con_C5bgp9zLvt.webm
e[36mopenvidu-server_1 |e[0m [ERROR] 2020-06-05 23:29:52,544 [Thread-10] io.openvidu.server.pro.recording.RecordingKmsHttpDownloader - Cannot create a FileOutputStream to file /storage/openvidu/recordings/ses_U5tPs5q4tU/str_CAM_A87U_con_Po5glgODZV.webm: http://10.9.208.5/recordings/ses_U5tPs5q4tU/str_CAM_A87U_con_Po5glgODZV.webm
e[36mopenvidu-server_1 |e[0m [ERROR] 2020-06-05 23:29:52,544 [Thread-11] io.openvidu.server.pro.recording.RecordingKmsHttpDownloader - http://10.9.208.5/recordings/ses_U5tPs5q4tU/str_CAM_GLn4_con_C5bgp9zLvt.webm
e[36mopenvidu-server_1 |e[0m [ERROR] 2020-06-05 23:29:52,544 [Thread-10] io.openvidu.server.pro.recording.RecordingKmsHttpDownloader - http://10.9.208.5/recordings/ses_U5tPs5q4tU/str_CAM_A87U_con_Po5glgODZV.webm
Have you changed default recording folder? Can you use standard one?
After setting the recording folder to default value, it worked
OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings
Does this mean we cannot change the recording path?
Changing recording path should be possible.
Maybe /opt/openvidu/recordings has the proper user rights and the other folder not.
Are you using some kind of s3 mounting or similar? Some users reported problems.
We have NFS mount point, We can see .zip file generated only with JSON file in the custom recording path. The content of JSON file is
{
If there are permission issues, then how does the .zip file with JSON gets created?
Interesting…
So JSON files are created but some big files coming from media server are not created. It can be related to how these two kind of files are managed in the code. JSON files are created directly in the Java code while media files are copied from media nodes. Maybe the libraries to write files are slightly different. Or maybe the problem is related with the size of the files. It is hard to know.
Can you try to record a very short session to see if file size matters?
We logged into KMS docker shell and found that the webm files exist in the custom path on the KMS server. But in OpenVidu logs we can see File Size is 0 after downloading
root@ecsvkms1:/storage/openvidu/recordings/ses_KYuUpFQM1h# ls -l
Maybe we have a bug in the folder management.
Just to be sure, can you set a custom path for recording outside NFS?
micael.gallego:
NFS
We tried with local custom path as OPENVIDU_RECORDING_PATH=/ovrecordings
openvidu-server_1 | [INFO] 2020-06-06 02:07:46,107 [EventExec-e7-t9] io.openvidu.server.recording.service.SingleStreamRecordingService - Recording stopped event for stream str_CAM_OEs0_con_HjKm1DHhVqhttp://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_NuEP_con_Wr6ULhmSdJ.webm http://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_OEs0_con_HjKm1DHhVq.webm http://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_OEs0_con_HjKm1DHhVq.webm ishttp://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_NuEP_con_Wr6ULhmSdJ.webm ishttp://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_NuEP_con_Wr6ULhmSdJ.webm http://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_OEs0_con_HjKm1DHhVq.webm http://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_NuEP_con_Wr6ULhmSdJ.webm http://10.9.208.5/recordings/ses_CGhaG3UnPI/str_CAM_OEs0_con_HjKm1DHhVq.webm
OpenVidu PRO 2.14.0 is not working with custom recording path. So we changed the recording path in .env to default value (/opt/openvidu/recordings) and created symlink to our NFS and it works now.
ln -s /storage/openvidu/recordings /opt/openvidu/recordings
Now recordings are stored in NFS Path /storage/openvidu/recordings
Thanks a lot for your support
