Ok I killed the process 517 then then I was able to run the docker
container for KMS and start it.
In OpenMeetings I entered a room and tried to add my video and audio
but received the error: "Media server is inaccessible." for both video
and audio.Does this indicate that I need to configure a STUN/TURN
server?
Thanks,Dennis
On Mon, 2020-08-31 at 08:06 +0700, Maxim Solodovnik wrote:
> You have some java process with PID 517already listening port 8888you
> can check what is this by running `ps -ef|grep 517`
> then you have options
> kill this java process (or change the port it is using)
> OR
> change the KMS port 
> 
> On Mon, 31 Aug 2020 at 03:28, dww <dwort...@mykolab.com> wrote:
> > Hello,
> > 
> > I am trying to install OpenMeetings 5.0.0 on a Linode VM that has
> > Debian 10(Buster) using the tutorial for this OS from 
> > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
> > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%205.0.0%20on%20Debian%2010.pdf?version=1&modificationDate=1598088626000&api=v2
> > 
> > At the step where the docker container for Kurento Media Server:
> > 
> > docker run -d --name kms -p 8888:8888 --mount
> > type=bind,source=/opt/open500/webapps/openmeetings/data,target=/opt
> > /open500/webapps/openmeetings/data kurento/kurento-media-server
> > 
> > I get the following error:
> >     346acd541df9862de72d4cca2311ce901bfdb70362da3e808a39b53f0fab64e
> > 0
> >     docker: Error response from daemon: driver failed programming
> > external connectivity on endpoint kms
> > (89ecf38e0f841be2906042aa9a47735caecbd4121b2e1e797a06e10f6e96c554):
> > Error starting userland proxy: listen tcp 0.0.0.0:8888: bind:
> > address     already in use.
> > 
> > When I run:netstat -pnltu | grep -i "8888"
> > 
> >     tcp6       0      0
> > :::8888                 :::*                    LISTEN      517/jav
> > a 
> > 
> > Any help on how I can resolve this would be appreciated.
> > 
> > Thanks,
> > Dennis
> 
> 

Reply via email to