This is frustrating , I checked docker ps and got:CONTAINER
ID        IMAGE                          COMMAND             CREATED   
          STATUS                   PORTS                    NAMES518e88
f02d50        kurento/kurento-media-server   "/entrypoint.sh"    7 days
ago          Up 5 hours (healthy)     0.0.0.0:8888->8888/tcp   kms

However is see no folder named /var/log/kurento-media-server and
therefore no log files
Also where I installed OM: /opt/open500/logs I see no file
openmeetings.log, I see file that start with catalina, host-manager,
localhose, localhose_access_log, manager. But there is no error in
those as far as I can see. In syslog there was a problem with rabbitmq-
server which I solved but I think is unrelated.
Why am I seeing no OM or KMS log files?
DennisOn Mon, 2020-09-07 at 09:45 +0700, Maxim Solodovnik wrote:
> Hello Dennis,
> 
> On Mon, 7 Sep 2020 at 02:39, dww <[email protected]> wrote:
> > On Thu, 2020-09-03 at 22:39 +0700, Maxim Solodovnik wrote:
> > > What is the client OS/browser?
> >     Tried on laptop with PureOS , debian derived distro and with
> > PureBrowser a derivative of Firefox
> >     Also tried on 64 bit Windows 10 laptop with both Firefox and
> > Chrom
> >     Same problem with both.
> 
> 1-2 clients usually works without issues 
> > > Do you have enough resources on server?
> >     I have OM and KMS installed on a Linode (VM) with 8GB, 4
> > Cores,  160 GB SSD storage, Network Transfer-5TB, Network In-
> > 40Gpbs, Network Out-5000Mbps
> 
> 8GB might be not enough, start/stop params and logs need to be
> examined 
> > > Can you check OM and KMS logs? are there any errors?
> >     Sorry to ask, but are the locations of the logs on the server?
> 
> OM logs are here: ${OM_HOME}/logs/openmeetings.logKMS logs are in
> /var/log/kurento-media-server/  (I would recommend to stop KMS, clean
> log dir, start it and then try to reproduce)
> Additionally system logs can be checked something
> like: /var/log/syslog 
> In case KMS is being disconnected it might be1) KMS crash (usually
> being reported to  /var/log/kurento-media-server/error* )2) system
> kill the process due to lack of resources (should be in system
> logs)3) something else ...
>  
> > Thanks,Dennis
> > > On Tue, 1 Sep 2020 at 23:31, dww <[email protected]> wrote:
> > > > Hello all,I followed the steps in the tutorial for SSL
> > > > certificates and Coturn.
> > > > After restarting I now can get my video and audio to show up in
> > > > the room, but after about a minute the video and audio suddenly
> > > > go away and I get the error message "Media server connection
> > > > for user {firstname lastname} is failed, will try to
> > > > reconnect."If I try to reallow withWebRTC, the same behavior
> > > > repeats.
> > > > Dennis
> > > > On Mon, 2020-08-31 at 08:02 +0200, Alvaro wrote:
> > > > > Please Dww, read  the tutorial, after install kurento, is a
> > > > > link:
> > > > > Download Installation SSL certificates and Coturn for
> > > > > OpenMeetings 5.0.0 on Debian 10
> > > > > Download it and follow it from step 5.
> > > > > 
> > > > > ....................
> > > > > 
> > > > > El dom, 30-08-2020 a las 23:39 -0400, dww escribió:
> > > > > > 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 <[email protected]>
> > > > > > > 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:
> > > > > > > >         346acd541df9862de72d4cca2311ce901bfdb70362da3e8
> > > > > > > > 08a39b53f0fab64e0
> > > > > > > >         docker: Error response from daemon: driver
> > > > > > > > failed programming external connectivity on endpoint
> > > > > > > > kms
> > > > > > > > (89ecf38e0f841be2906042aa9a47735caecbd4121b2e1e797a06e1
> > > > > > > > 0f6e96c554): 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/java 
> > > > > > > > 
> > > > > > > > Any help on how I can resolve this would be
> > > > > > > > appreciated.
> > > > > > > > 
> > > > > > > > Thanks,
> > > > > > > > Dennis
> > > > > > > 
> > > > > > > 
> > > 
> > > 
> 
> 

Reply via email to