Trouble installing OpenVidu server

OpenVidu v2 Issues with deployment
1

I’m trying to follow this https://openvidu.io/docs/deployment/deploying-ubuntu/ guide on Ubuntu 18. I did all steps and ended up with an error. The message is the following

KMS in ws://localhost:8888/kurento is not reachable by OpenVidu Server

Any idea what went wrong? How can I fix it?

2

Is KMS running? Check it by entering this command:

systemctl status kurento-media-server

if it is stopped, run this command:

systemctl start kurento-media-server

Also if Kurento Media Server is running, run this command:

curl -i -N \
    -H "Connection: Upgrade" \
    -H "Upgrade: websocket" \
    -H "Host: 127.0.0.1:8888" \
    -H "Origin: 127.0.0.1" \
    http://127.0.0.1:8888/kurento

It should return this if KMS is working correctly:

HTTP/1.1 500 Internal Server Error

Best Regards,
Carlos

3

gives me this message

kurento-media-server.service - LSB: Kurento Media Server daemon
Loaded: loaded (/etc/init.d/kurento-media-server; generated)
Active: active (exited) since Wed 2020-02-19 14:34:03 UTC; 20h ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 4646)
CGroup: /system.slice/kurento-media-server.service

I also tried this command

but I’m getting

(7) Failed to connect to 127.0.0.1 port 8888: Connection refused

I think I’ve done something wrong in these steps

ov-setup
ov-setup937×571 16.9 KB

Am I supposed to access these files and just copy paste the given properties? That’s what I did.

4

Maybe your configuration is wrong and the KMS did not run correctly. Did you replace YOUR_MACHINE_PUBLIC_IP with your actual public ip in those configuration files?

5

Yes, I did that. But anyway I think it works now. I think the issue was I didn’t initialize services properly.

1 Like
6

@angi can you please expain the way, you set up this error ?

7

@Rishabh_Khandelwal this is an old post and the deployment have changed. Can you create a new one and explain your problem? Thanks

8

@cruizba I want to create a deployment of openvidu in minikube cluster. I am doing this by using a yaml file. KMS container and other containers has been launched successfully but openvidu-server is unable to start. I got this type of logs in openvidu-server:

KMS in ws://localhost:8888/kurento is not reachable by OpenVidu Server

In logs, I find that openvidu-server is started initially with all the environment variables and due to this error, openvidu-server gets shut down.

I think may be issue due to networking in the cluster. Can you please suggest me the network configuration so that openvidu-server can reach ws://localhost:8888/kurento . And for other pods, they would be able to make an internal network between them.

Please suggest me some way so that I can make this whole deployment in one network and openvidu-server has access to kms, coturn, redis, etc and their required ports.

9

Well, if you know how kubernetes works:

  1. You need A LOT of ports bindings if you want to use KMS deployed as a Service in K8s and use the K8S DNS to access the service. So your only way to manage this excessive port binding is to run KMS in network=host.

  2. Running KMS as network=host implies that you can not use the k8s DNS for this specific service. In minikube it may works (I don’t know i did not try it) because your cluster has only one node, and it will find what localhost is, but in real clusters, you will need to guess in what Node the KMS is deployed.

In conclustion, I don’t recomend you to deploy OpenVidu CE in a kubernetes cluster (it is not tested and we don’t support it). But in your case, I think that running all the services as network=host should do the trick.

10

@Rishabh_Khandelwal could you please share your yaml file? I would really appreciate it. Thanks.