Add Media Node to OpenVidu Cluster

Hello,
I had setup the environment as the “Deployment document”(OpenVidu Docs). But I got a error when add another media node to cluster as following picture.

圖片
I wonder to know if anything goes wrong. Thanks.
Best Regards

What deployment is this one? Is a PRO or ENTERPISE one?

If you’re in AWS, are you using the Cloudformation template?

I use the PRO version to deploy on AWS EC2.

Then, it is an On premises deployment in AWS?, or are you using Cloudformation?

Can you share your configuration at /opt/openvidu/.env?

configuration

...
OPENVIDU_PRO_CLUSTER_MODE=manual
OPENVIDU_PRO_CLUSTER_ENVIRONMENT=on_premise
# OPENVIDU_PRO_CLUSTER_ID=
#OPENVIDU_PRO_CLUSTER_MEDIA_NODES=
# OPENVIDU_PRO_CLUSTER_LOAD_INTERVAL=
OPENVIDU_PRO_CLUSTER_AUTOSCALING=false
...

Why don’t you use the Cloudformation template? It is prepared to work natively with AWS.

Can you please tell me step by step how did you deploy OpenVidu?

If you are in AWS, please follow this guide over here AWS.



Here you have two examples of parameters to have a minimal installation for selfsigned and another one for letsencrypt using Cloudformation:

Selfigned:





Letsencrypt





There are more possible combinations, but I am exposing here two basic configurations to have the deployment working with S3. More detailed explanations are in the AWS documentation. This cloudformation will also create a role attached to your EC2 instance, so you don’t need to configure S3. Just fill the parameters, and it is ready to go.

To enable Enterprise when everything is deployed, you just need to SSH into your master node and change the variable OPENVIDU_EDITION with:

OPENVIDU_EDITION=enterprise

A 404 means the OpenVidu Server cannot reach the Media Server manually indicated in the URI parameter. This is probably caused because your Media Node does not meet the required pre-requisites:

Make sure that your Media Node instances fulfill those requisites before deploying the services as stated in here.

If services are properly launched and the Media Node allows connections from the Master Node through the required ports, everything should work just fine and you should be able to add your new Media Node to the OpenVidu cluster through the Inspector, just as you tried before.

Hi, @cruizba I installed it according to the link below.
https://docs.openvidu.io/en/2.19.0/deployment/pro-enterprise/on-premises/
Hi, @pabloFuente
I installed the media node to the second EC2, but only the port 3000 exists.
I installed it according to the link below.
https://docs.openvidu.io/en/2.19.0/deployment/pro-enterprise/on-premises/#3-media-nodes

Configuration

DOMAIN_OR_PUBLIC_IP=XXXXXXXX.compute.amazonaws.com
OPENVIDU_PRO_LICENSE=XXXXXXXXXXXXXXXXXXXX
OPENVIDU_SECRET=openvidu
CERTIFICATE_TYPE=selfsigned
HTTPS_PORT=443
SUPPORT_DEPRECATED_API=true
REDIRECT_WWW=false
WORKER_CONNECTIONS=10240
OPENVIDU_PRO_CLUSTER_MODE=manual
OPENVIDU_PRO_CLUSTER_ENVIRONMENT=on_premise
OPENVIDU_PRO_CLUSTER_AUTOSCALING=false
OPENVIDU_PRO_CLUSTER_LOAD_STRATEGY=streams
OPENVIDU_PRO_ELASTICSEARCH_MAX_DAYS_DELETE=1
OPENVIDU_PRO_RECORDING_STORAGE=s3
OPENVIDU_PRO_AWS_S3_BUCKET=XXXXXX
OPENVIDU_PRO_AWS_ACCESS_KEY=XXXXXXXXXXXXXX
OPENVIDU_PRO_AWS_SECRET_KEY=XXXXXXXXXXXXX
OPENVIDU_PRO_AWS_REGION=us-east-2
OPENVIDU_RECORDING=true
OPENVIDU_RECORDING_DEBUG=false
OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings
OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout
OPENVIDU_RECORDING_PUBLIC_ACCESS=true
OPENVIDU_RECORDING_NOTIFICATION=publisher_moderator
OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120
OPENVIDU_STREAMS_VIDEO_MAX_RECV_BANDWIDTH=1000
OPENVIDU_STREAMS_VIDEO_MIN_RECV_BANDWIDTH=300
OPENVIDU_STREAMS_VIDEO_MAX_SEND_BANDWIDTH=1000
OPENVIDU_STREAMS_VIDEO_MIN_SEND_BANDWIDTH=300
OPENVIDU_WEBHOOK=false
OPENVIDU_WEBHOOK_EVENTS=[sessionCreated,sessionDestroyed,participantJoined,participantLeft,webrtcConnectionCreated,webrtcConnectionDestroyed,recordingStatusChanged,filterEventDispatched,mediaNodeStatusChanged]

OPENVIDU_SESSIONS_GARBAGE_INTERVAL=900
OPENVIDU_SESSIONS_GARBAGE_THRESHOLD=3600
OPENVIDU_CDR=true
OPENVIDU_CDR_PATH=/opt/openvidu/cdr
ES_JAVA_OPTS=-Xms512m -Xmx512m
ELASTICSEARCH_USERNAME=elasticadmin
ELASTICSEARCH_PASSWORD=XXXXXXXXX
KMS_IMAGE=kurento/kurento-media-server:6.16.0

Install the components in the first EC2 as follows

  1. Openvidu
  2. media node

Install the components in the second EC2 as follows

  1. media node

I solved this problem. I forgot to open port 3000.

Told you so :wink: Port configuration must comply all of the pre-requisites listed in the documentation.