Open brunobottazzini opened 4 years ago
Hello,
Can you please try to replicate this issue with openvidu-server-kms Docker container and the openvidu-recording-java tutorial? I see that you tried, but your docker run command wasn't valid. Try this one:
docker run -p 4443:4443 --rm \
-e OPENVIDU_RECORDING=true \
-e OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /opt/openvidu/recordings:/opt/openvidu/recordings \
openvidu/openvidu-server-kms:2.15.0
(The recording path in this command is set to /opt/openvidu/recordings
)
If you are able to replicate the issue with this set up, we will be able to fix it very quickly if there's in fact a problem. Thank you.
Hello,
Thank you very much for the information. I could replicate the problem in question using the tutorials.
Steps:
{"session":"ses_L5JoKqYUUe","outputMode":"INDIVIDUAL","hasAudio":true,"hasVideo":true}
The behavior: The POST call hangs for about 10 seconds.
The response:
The application:
I used Docker to deploy the whole service normally, now I'm using your source code to develop OpenVidu-Server, the recording module is problematic. Recording alone with a REST-API call results are fine, but the generated ZIP file unzips only one JSON, which has been bothering me for a long time. Please help to check, thank you
I used Docker to deploy the whole service normally, now I'm using your source code to develop OpenVidu-Server, the recording module is problematic. Recording alone with a REST-API call results are fine, but the generated ZIP file unzips only one JSON, which has been bothering me for a long time. Please help to check, thank you
Hello,
Is any one worked on screen sharing and recording using Openvidu in iOS mobile application. if YES, please let me know the process.
Describe the bug java.lang.NullPointerException when starting a record right after the user has forcefully quit the conference.
In other words:
openvidu-server respond us with HTTP response code 500 and NullPointerException can be found in its log.
Expected behavior When calling openvidu server via rest template with POST the server should respond us with a meaningful response code or a message explaining why the record could not start. As shown the response code in the documentation.
Maybe it could ignore the "unreachable" users and start recording people who is reachable in the session at the moment?
Wrong current behavior The server is giving us a non predicted HTTP Response code: 500 as you can see it is not mapped in the documentation.
Or maybe as written above, it might not give us an error at all.
OpenVidu tutorial where to replicate the error Tried to replicate the problem using openvidu-recording-java but I could not start a record at all to see if it happens also in the tutorials. I think there are some missing information to use it, Am I missing any configuration?
docker run -p 4443:4443 --rm -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp -e openvidu.recording=true -e openvidu.recording.path=/tmp openvidu/openvidu-server-kms:2.15.0
OpenVidu deployment info How is your OpenVidu Server instance deployed when you get the bug. A couple of possible examples are listed below:
Could not find a way to test a record inside demos.openvidu.io
Client device info (if applicable) Describe the client device(s) or platform(s) where you are able to replicate the error. For example: