Unable to restart openvidu from inspector - On Premise

Hello,

I am unable to restart openvidu from the inspector. The installation is on Digitalocean and the error I am getting is given below.

ERROR restarting OpenVidu Pro
Error restarting OpenVidu Server Pro: Cluster environment “on_premise” requires file
“/opt/openvidu/cluster/openvidu_launch_kms.sh” to exist, but cannot be found

The installation was successful even though I have noticed the below errors in the terminal.

1. I Ignored

failed: [media-node-1] (item=libglib2.0-0-dbgsym) => {“ansible_loop_var”: “item”,
“cache_update_time”: 1584509351, “cache_updated”: true, “changed”: false, “item”: “libglib2.0-0-dbgsym”, “msg”: “‘/usr/bin/apt-get -y -o "Dpkg::Options::=–force-confdef" -o "Dpkg::Options::=–force-confold" install ‘libglib2.0-0-dbgsym’’ failed: E: Unable to correct problems, you have held broken packages.\n”, “rc”: 100, “stderr”: “E: Unable to correct problems, you have held broken packages.\n”, “stderr_lines”: [“E: Unable to correct problems, you have held broken packages.”], “stdout”: “Reading package lists…\nBuilding dependency tree…\nReading state information…\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n libglib2.0-0-dbgsym : Depends: libglib2.0-0-dbg (= 2.48.2-0ubuntu4.5) but 2.48.2-0ubuntu4.4 is to be installed\n”, “stdout_lines”: [“Reading package lists…”, “Building dependency tree…”, “Reading state information…”, “Some packages could not be installed. This may mean that you have”, “requested an impossible situation or if you are using the unstable”, “distribution that some required packages have not yet been created”, “or been moved out of Incoming.”, “The following information may help to resolve the situation:”, “”, “The following packages have unmet dependencies:”, " libglib2.0-0-dbgsym : Depends: libglib2.0-0-dbg (= 2.48.2-0ubuntu4.5) but 2.48.2-0ubuntu4.4 is to be installed"]}

2. I Ignored

failed: [media-node-1] (item=libsrtp0-dbgsym) => {“ansible_loop_var”: “item”, “cache_update_time”:
1584509385, “cache_updated”: true, “changed”: false, “item”: “libsrtp0-dbgsym”, “msg”: “‘/usr/bin/apt-get -y -o "Dpkg::Options::=–force-confdef" -o "Dpkg::Options::=–force-confold" install ‘libsrtp0-dbgsym’’ failed: E: Unable to correct problems, you have held broken packages.\n”, “rc”: 100, “stderr”: “E: Unable to correct problems, you have held broken packages.\n”, “stderr_lines”: [“E: Unable to correct problems, you have held broken packages.”], “stdout”: “Reading package lists…\nBuilding dependency tree…\nReading state information…\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n libsrtp0-dbgsym : Depends: libsrtp0 (= 1.4.5~20130609~dfsg-1.1ubuntu1) but 1.6.0-0kurento1.16.04 is to be installed\n”, “stdout_lines”: [“Reading package lists…”, “Building dependency tree…”, “Reading state information…”, “Some packages could not be installed. This may mean that you have”, “requested an impossible situation or if you are using the unstable”, “distribution that some required packages have not yet been created”, “or been moved out of Incoming.”, “The following information may help to resolve the situation:”, “”, “The following packages have unmet dependencies:”, " libsrtp0-dbgsym : Depends: libsrtp0 (= 1.4.5~20130609~dfsg-1.1ubuntu1) but 1.6.0-0kurento1.16.04 is to be installed"]}
failed: [media-node-1] (item=libusrsctp-dbgsym) => {“ansible_loop_var”: “item”, “changed”: false, “item”: “libusrsctp-dbgsym”, “msg”: “No package matching ‘libusrsctp-dbgsym’ is available”}

3. Installed Manually

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: No module named passlib.apache
fatal: [openvidu-server]: FAILED! => {“changed”: false, “msg”: “Failed to import the required Python library (passlib) on palmnote-openvidu-pro’s Python /usr/bin/python. Please read module documentation and install in the appropriate location”}

Not sure these are related, but just letting you know what I have seen.

Please let me know why I am getting the error while restarting the service.

Best,

Hi,

Are you trying to set the openvidu.pro.cluster.mode to auto? Because if that’s so, then you need scripts to launch and drop Media Nodes of your environment (DigitalOcean in this case).

That’s what the error is saying: it expects script /opt/openvidu/cluster/openvidu_launch_kms.sh, which doesn’t exist in your OpenVidu Server Pro Node.

There’s no actual documentation of the scripts required for making an On Premise deployment work with auto mode. It works fine, as AWS deployment works the same way under the hood, but we have not documented it yet. We considered this to be a fairly advance use of OpenVidu Pro, and didn’t want to A) overwhelm developers with too much information in the docs during this first version B) document something that will probably change soon, as we are looking to move to a Kubernetes based deployment in the short term.

Regards

Hey Pablo,

No, I am not trying to set the openvidu.pro.cluster.mode to auto. I tried restarting without any configuration changes. The pro.cluster.mode is set to manual only.

I’m having the same error in Azure. No changes made but it fails because it can’t find /opt/openvidu/cluster/openvidu_launch_kms.sh.

Can you please post here the configuration copied from CONFIG page of OpenVidu Inspector? (You have a “Copy to clipboard” button below).

Change any domain name if you don’t want to paste it here.

Regards.

Hello,

Please find the configuration.

{
“version”: “2.12.0”,
“kmsUris”: [
“ws://IP:8888/kurento”
],
“openviduPublicurl”: “https://video.domain.com:4443”,
“openviduCdr”: false,
“maxRecvBandwidth”: 0,
“minRecvBandwidth”: 0,
“maxSendBandwidth”: 0,
“minSendBandwidth”: 0,
“openviduRecording”: true,
“openviduRecordingVersion”: “2.9.0”,
“openviduRecordingPath”: “/opt/openvidu/recordings/”,
“openviduRecordingPublicAccess”: true,
“openviduRecordingNotification”: “all”,
“openviduRecordingCustomLayout”: “/opt/openvidu/custom-layout/”,
“openviduRecordingAutostopTimeout”: 120,
“openviduRecordingComposedUrl”: “https://video.domain.com/inspector/”,
“openviduWebhook”: false,
“openviduServerDependencyVersion”: “2.12.0”,
“openviduProStatsMonitoringInterval”: 30,
“openviduProStatsWebrtcInterval”: 30,
“openviduProCluster”: true,
“openviduProClusterMode”: “manual”,
“openviduProClusterLoadStrategy”: “streams”,
“openviduProClusterPath”: “/opt/openvidu/cluster/”,
“openviduProClusterId”: “clu_AnvhbbOs”,
“openviduProElasticsearch”: true,
“openviduProElasticsearchHost”: “http://localhost:9200”,
“openviduProElasticsearchVersion”: “7.6.1”,
“openviduProKibana”: true,
“openviduProKibanaHost”: “http://localhost/kibana”,
“openviduProKibanaVersion”: “7.6.1”
}

Okey, I’m experiencing the exact same behavior, so some bug must have just appeared!
Let me take a look and I’ll come back with an answer

Okey,

It was indeed a bug. It has already been fixed, and I’ve generated a new SNAPSHOT version for you to try it.

To run the new SNAPSHOT version in your existing cluster, you just need to perform a very simple change in your cloned version of repository openvidu-pro-clustering:

In file roles/openvidu/templates/download_ov.sh.j2 simply change this line:

https://pro-stripe.openvidu.io/openvidu-server-pro-{{openvidu_version}}.jar \

for this line:

https://pro-stripe.openvidu.io/openvidu-server-pro-2.13.0-SNAPSHOT.jar \

And relaunch the playbook: ansible-playbook -i inventory.yaml play.yaml

Try it and post here if you are now able to restart your cluster from Inspector.

Thank you

I tried it out and worked. Saw the below error in the terminal though. Please let me know this is something serious.

Also, does Openvidu Restart restarts KMS media servers in the media nodes too?

failed: [media-node-1] (item=libsrtp0-dbgsym) => {“ansible_loop_var”: “item”, “cache_update_time”: 1585063332, “cache_updated”: true, “changed”: false, “item”: “libsrtp0-dbgsym”, “msg”: “‘/usr/bin/apt-get -y -o "Dpkg::Options::=–force-confdef" -o "Dpkg::Options::=–force-confold" install ‘libsrtp0-dbgsym’’ failed: E: Unable to correct problems, you have held broken packages.\n”, “rc”: 100, “stderr”: “E: Unable to correct problems, you have held broken packages.\n”, “stderr_lines”: [“E: Unable to correct problems, you have held broken packages.”], “stdout”: “Reading package lists…\nBuilding dependency tree…\nReading state information…\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n libsrtp0-dbgsym : Depends: libsrtp0 (= 1.4.5~20130609~dfsg-1.1ubuntu1) but 1.6.0-0kurento1.16.04 is to be installed\n”, “stdout_lines”: [“Reading package lists…”, “Building dependency tree…”, “Reading state information…”, “Some packages could not be installed. This may mean that you have”, “requested an impossible situation or if you are using the unstable”, “distribution that some required packages have not yet been created”, “or been moved out of Incoming.”, “The following information may help to resolve the situation:”, “”, “The following packages have unmet dependencies:”, " libsrtp0-dbgsym : Depends: libsrtp0 (= 1.4.5~20130609~dfsg-1.1ubuntu1) but 1.6.0-0kurento1.16.04 is to be installed"]}
failed: [media-node-1] (item=libusrsctp-dbgsym) => {“ansible_loop_var”: “item”, “changed”: false, “item”: “libusrsctp-dbgsym”, “msg”: “No package matching ‘libusrsctp-dbgsym’ is available”}

Try running git pull in your cloned repository and launch the ansible again.

You should see no error this time if you update your repository to the latest commit of the 2.12.0 branch.
And no, the restart method of OpenVidu Server Pro only restarts its own process, not the Media Server ones.

Regards.

1 Like