Yes,
That’s my pleasure!
Please @lihuapeng…
here is the openvidu log file link.
https://drive.google.com/file/d/1N84UI0AKCNQYNAiIzBESsbqffilBLxSQ/view
please help me
The error on the browsers console is telling you whats happening: “There is no available Media Node where to initialize the sessions”
Your don’t have any Media Node in your cluster. You must have at least one to initialize a session.
The doc is not public
Hello @Tolga_Kaprol, we have identified a critical bug in OpenVidu with the symptoms you describe.
It is really hard for us to reproduce and to identify the root cause. Please can you help us to get more information about it? Can you take a look to github issue and test with a beta version we have just published?
@lihuapeng your problem seems very different. Can you give us access to the doc with OpenVidu logs so we can investigate?
Regards
Just a moment.
Let me turn to public
Hello, micael!
Can’t you download the log file yet?
Let me know after you try.
And, pablo, I used the openvidu-react-call source by its way.
The session is initialized as following method.
this.OV = new OpenVidu()
session = this.OV.initSession()
It requires no special parameter when initialize session.
What does means the Media Node cluster exactly?
Based on the log you share with us, the Kurento Media Server is being disconnected from OpenVidu Server.
Usually this occurs because KMS has crashed.
Can you please follow this instructions to generate a crash report to know the origin of the crash?
https://docs.openvidu.io/en/2.14.0/deployment/deploying-on-premises/#kurento-media-server-crash
For last a week, the openvidu is not crashed
well working…
strange…
Anyway, thank you
I have a question.
Originally, I installed the KMS on my ubuntu server, but this new version is working on docker.
Is this docker running the another KMS?
From OpenVidu 2.13, all services (including KMS) are dockerized.
Hi Micael,
I just read your message.
We are rebooting the server nightly, and it is working at the moment.
If it works for you, I can provide some cloud servers from our cloud infrastructure (OpenStack) to replicate the issue. I guess it will going to happen on another instance too.
Perfect. If you can replicate the problem, we can take a look to logs to try to understand the root cause.