Hello Alex,

thanks for your feedback!
and I'm really glad everything works as expected :)

On Tue, 13 Oct 2020 at 16:06, Ninnig, Alexander <
alexander.nin...@rechnungshof.rlp.de> wrote:

> Hello Maxim,
>
> thank you so much for all your help (not only with this issue).
>
> Please consider this issue as closed: our group policies (GPO) seem to be
> the problem.
> I didn't think of that, because of the weird behaviour (stopping after one
> minute).
> If it hadn't been working right from the start, I may have guessed it.
> Anyway, I moved my active directory accounts to organization units without
> group policies: webcam is stable since about half an hour.
>
> Sorry for bothering you here, Maxim.
> To all you folks out there: in case you are using Firefox (or other
> browsers) in a business-environment with group policies, you might wanna
> check that.
>
> Best regards,
> Alex
>
>
> PS: The new OpenMeetings looks very nice! Nice layout, good translation
> (german), and it works really well in Firefox (Screensharing, Camera,
> Microphone, etc.).
> Also, I had no problems installing OM5, deploying a certificate,
> configuring and importing LDAP so far.
> Really well done!
>
>
> -----Ursprüngliche Nachricht-----
> Von: Maxim Solodovnik <solomax...@gmail.com>
> Gesendet: Dienstag, 13. Oktober 2020 03:48
> An: Openmeetings user-list <user@openmeetings.apache.org>
> Betreff: Re: Media server connection for user test is disconnected, will
> try to re-connect
>
> Hello Alex,
>
> On Mon, 12 Oct 2020 at 21:09, Ninnig, Alexander
> <alexander.nin...@rechnungshof.rlp.de> wrote:
> >
> > Hello Maxim,
> >
> >
> >
> > This line was in an openmeetings.log:
> >
> > DEBUG 10-08 09:23:39.469 o.a.o.c.r.KurentoHandler:152 [ntLoopGroup-3-1]
> - JsonRpcWsClient disconnected from ws://127.0.0.1:8888/kurento because
> Channel closed.
> >
> >
> >
> > Is this the problem?
>
> Yes, your KMS is down
> so no audio/video anymore
> please check if Docker is up and running and KMS is alive inside of it
>
> >
> > The manual states the applicationContext.xml should be edited to
> kurentoWsUrl="ws://127.0.0.1:8888/kurento"
> >
>
> since you are using local docker this should be correct URL
>
> >
> >
> >
> >
> > The OM-Server is an intern server, so there is no need to go through a
> firewall.
> >
> > So I don’t know, if I even need this coturn-stuff.
>
>
> most probably not
> Multimedia server is down so no broadcasting
>
> >
> >
> >
> > You asked:
> >
> > Am I right thinking you get "Connection to Media server has been
> established" and then "Media server connection for user test is
> disconnected, will try to re-connect" ?
> >
> > That’s right, it works fine for about one minute.
>
> it seems KMS is able to work for 1 minute
> you have to check what is wrong with it
>
> >
> >
> >
> > I couldn’t find any turnserver-logs (/var/log/turnserver is empty).
> >
> >
> >
> > Here is some more of the openmeetings.log:
> >
> >
> >
> > DEBUG 10-08 09:11:02.651 o.a.o.d.u.AuthLevelUtil:40 [nio-5443-exec-8] -
> Level ADMIN :: [GRANTED]
> >
> > DEBUG 10-08 09:11:02.657 o.a.o.d.u.AuthLevelUtil:40 [nio-5443-exec-8] -
> Level ADMIN :: [GRANTED]
> >
> > DEBUG 10-08 09:11:02.657 o.a.o.d.u.AuthLevelUtil:40 [nio-5443-exec-8] -
> Level ADMIN :: [GRANTED]
> >
> > DEBUG 10-08 09:11:02.747 o.a.o.w.c.OmWebSocketPanel:74 [nio-5443-exec-8]
> - pingTimer is attached
> >
> > DEBUG 10-08 09:11:02.758 o.a.o.w.p.MainPage:102 [nio-5443-exec-8] -
> renderHead:: newAreaBehavior
> >
> > DEBUG 10-08 09:14:59.712 o.a.o.s.q.s.ReminderJob:93 [Bean#0_Worker-4] -
> Rss disabled by Admin
> >
> > INFO 10-08 09:23:39.468 o.k.j.c.JsonRpcClientNettyWebSocket:275
> [ntLoopGroup-2-1] -  channel closed
> >
> > INFO 10-08 09:23:39.468 o.k.j.c.JsonRpcClientNettyWebSocket:275
> [ntLoopGroup-3-1] -  channel closed
> >
> > DEBUG 10-08 09:23:39.469 o.a.o.c.r.KurentoHandler:152 [ntLoopGroup-3-1]
> - JsonRpcWsClient disconnected from ws://127.0.0.1:8888/kurento because
> Channel closed.
> >
> > DEBUG 10-08 09:23:39.469 o.a.o.c.r.KurentoHandler:152 [ntLoopGroup-2-1]
> - JsonRpcWsClient disconnected from ws://127.0.0.1:8888/kurento because
> Channel closed.
> >
> > INFO 10-08 09:23:39.469 o.a.o.c.r.KurentoHandler:143 [ntLoopGroup-3-1] -
> !!! Kurento disconnected
> >
> > INFO 10-08 09:23:39.469 o.a.o.c.r.KurentoHandler:143 [ntLoopGroup-2-1] -
> !!! Kurento disconnected
> >
> > DEBUG 10-08 09:23:39.470 o.a.o.c.r.KurentoHandler:192 [ntLoopGroup-2-1]
> - Client will destroyed ...
> >
> > WARN 10-08 09:23:39.558 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [ntLoopGroup-2-1] -  Trying to close a JsonRpcClientNettyWebSocket with
> channel == null
> >
> > WARN 10-08 09:23:39.559 o.k.j.c.JsonRpcClientNettyWebSocket:291
> [ntLoopGroup-2-1] -  Trying to close a JsonRpcClientNettyWebSocket with
> group == null
> >
> > DEBUG 10-08 09:23:39.559 o.a.o.c.r.KurentoHandler:194 [ntLoopGroup-2-1]
> - .... Client is destroyed
> >
> > WARN 10-08 09:23:39.563 o.a.o.c.r.KRoom:274 [ntLoopGroup-2-1] -
> PARTICIPANT 15: Could not release Pipeline
> >
> > DEBUG 10-08 09:23:39.563 o.a.o.c.r.KRoom:277 [ntLoopGroup-2-1] - Room 15
> closed
> >
> > DEBUG 10-08 09:23:44.302 o.a.o.c.r.KurentoHandler:132 [pool-1-thread-1]
> - Reconnecting KMS
> >
> > INFO 10-08 09:23:44.303 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [pool-1-thread-1] -  Connecting native client
> >
> > INFO 10-08 09:23:44.303 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [pool-1-thread-1] -  Creating new NioEventLoopGroup
> >
> > INFO 10-08 09:23:44.308 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-4-1] -  Initiating new Netty channel. Will create new handler
> too!
> >
> > INFO 10-08 09:23:44.318 o.a.o.c.r.KurentoHandler:162 [pool-1-thread-1] -
> !!! Kurento connected
> >
> > INFO 10-08 09:23:52.993 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy: Wicket extensions initializer
> >
> > INFO 10-08 09:23:52.994 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
> >
> > INFO 10-08 09:23:52.994 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
> >
> > INFO 10-08 09:23:52.994 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy: Wicket core library initializer
> >
> > INFO 10-08 09:23:52.994 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
> >
> > INFO 10-08 09:23:52.994 o.a.w.Application:539 [main] -
> [OpenmeetingsApplication] destroy:
> org.wicketstuff.dashboard.DashboardContextInitializer@2102268c
> >
> > INFO 10-08 09:23:52.995 c.h.c.LifecycleService:65 [main] -
> [172.17.0.1]:5701 [dev] [4.0.2] [172.17.0.1]:5701 is SHUTTING_DOWN
> >
> > INFO 10-08 09:23:53.016 c.h.i.p.i.MigrationManager:65 [cached.thread-5]
> - [172.17.0.1]:5701 [dev] [4.0.2] Shutdown request of Member
> [172.17.0.1]:5701 - 579db232-2b17-405d-990f-f6cbb6d952fb this is handled
> >
> > INFO 10-08 09:23:53.179 c.h.i.impl.Node:65 [main] - [172.17.0.1]:5701
> [dev] [4.0.2] Shutting down connection manager...
> >
> > INFO 10-08 09:23:53.181 c.h.i.impl.Node:65 [main] - [172.17.0.1]:5701
> [dev] [4.0.2] Shutting down node engine...
> >
> > INFO 10-08 09:23:53.222 c.h.i.i.NodeExtension:65 [main] -
> [172.17.0.1]:5701 [dev] [4.0.2] Destroying node NodeExtension.
> >
> > INFO 10-08 09:23:53.223 c.h.i.impl.Node:65 [main] - [172.17.0.1]:5701
> [dev] [4.0.2] Hazelcast Shutdown is completed in 212 ms.
> >
> > INFO 10-08 09:23:53.224 c.h.c.LifecycleService:65 [main] -
> [172.17.0.1]:5701 [dev] [4.0.2] [172.17.0.1]:5701 is SHUTDOWN
> >
> >
> >
> > Is this helpful?
>
> I would say
> KMS was down, then OM was shutdown
>
>
> >
> >
> >
> > Best regards,
> >
> > Alex
> >
> >
> >
> >
> >
> > Von: Maxim Solodovnik <solomax...@gmail.com>
> > Gesendet: Freitag, 9. Oktober 2020 15:08
> > An: Openmeetings user-list <user@openmeetings.apache.org>
> > Betreff: Re: Media server connection for user test is disconnected, will
> try to re-connect
> >
> >
> >
> > The logs need to be checked are
> >
> >
> >
> > 1) openmeetings.log (openmeetings.<date>.log if <date> != today)
> >
> > 2) KMS logs (should be available if docker was started in "interactive"
> mode, or you can mount docker's /var/log to some local folder)
> >
> > 3) TURN logs
> >
> >
> >
> > Am I right thinking you get "Connection to Media server has been
> established" and then "Media server connection for user test is
> disconnected, will try to re-connect" ?
> >
> >
> >
> > >> But still: no webcam/mic after about 1 minute. Same error.
> >
> >
> >
> > On Fri, 9 Oct 2020 at 20:02, Ninnig, Alexander <
> alexander.nin...@rechnungshof.rlp.de> wrote:
> >
> > Hello Maxim,
> >
> >
> >
> > thanks for your response.
> >
> >
> >
> > I used the manual: Installation of Apache OpenMeetings 5.0.1 on Ubuntu
> 20.04 lts. Step by step.
> >
> > in my last mail there was a typo, actually it’s /opt/501, not /opt/504.
> >
> > I downloaded: sudo wget
> https://downloads.apache.org/openmeetings/5.0.1/bin/apache-openmeetings-5.0.1.tar.gz
> >
> > Is that the problem? Do I have to use a newer version of OM?
> >
> >
> >
> > As KMS I use Docker, just like in the manual.
> >
> > I am testing on Firefox ESR 68 (latest update) and Windows 10 Enterprise
> 1909.
> >
> >
> >
> > Yes, there are some logs, which ones would be the most helpful to
> analyze? Openmeetings.<date>.log?
> >
> >
> >
> > /opt/open501/logs
> >
> > catalina.2020-10-07.log              openmeetings.log
> >
> > catalina.2020-10-08.log              root.2020-10-07.0.log
> >
> > catalina.out                         root.2020-10-07.1.log
> >
> > host-manager.2020-10-07.log          root.2020-10-07.2.log
> >
> > host-manager.2020-10-08.log          root.2020-10-07.3.log
> >
> > localhost.2020-10-07.log             root.2020-10-07.4.log
> >
> > localhost.2020-10-08.log             root.2020-10-07.5.log
> >
> > localhost_access_log.2020-10-07.txt  root.2020-10-07.6.log
> >
> > localhost_access_log.2020-10-08.txt  root.2020-10-07.7.log
> >
> > logs                                 root.2020-10-07.8.log
> >
> > manager.2020-10-07.log               root.2020-10-07.9.log
> >
> > manager.2020-10-08.log               root.log
> >
> > openmeetings.2020-10-07.0.log
> >
> >
> >
> > Best regards,
> >
> > Alex
> >
> >
> >
> >
> >
> > Von: Maxim Solodovnik <solomax...@gmail.com>
> > Gesendet: Donnerstag, 8. Oktober 2020 17:22
> > An: Openmeetings user-list <user@openmeetings.apache.org>
> > Betreff: Re: Media server connection for user test is disconnected, will
> try to re-connect
> >
> >
> >
> > Hello Alex,
> >
> >
> >
> > this is definitely not SSL certificate
> >
> >
> >
> > What exact OM version are you using (the path is /opt/open504 so I guess
> it is 5.0.0-M4 ?)
> >
> > What KMS version are you using
> >
> >
> >
> > What browser/OS are you using for testing?
> >
> >
> >
> > Any errors in server logs (logs/openmeetings.log and/or KMS logs)
> >
> >
> >
> >
> >
> > On Thu, 8 Oct 2020 at 21:33, Ninnig, Alexander <
> alexander.nin...@rechnungshof.rlp.de> wrote:
> >
> > Hello,
> >
> > I'm sure this has been answered before, but I couldn't make it work yet.
> I just set up a new OpenMeetings-Server (Ubuntu Server 20.04 LTS, OM 5),
> using the official manual.
> >
> > After entering a room, Webcam/Micro work fine for about 1 minute, then
> there is no picture/no sound ("Media server connection for user test is
> disconnected, will try to re-connect"). After that, I can turn off/turn on
> webcam/micro, using the OpenMeetings-buttons, but again it will work for
> only about one minute.
> >
> > My first mistake was, not to setup Coturn, because I somehow thought, I
> wouldn't need the second manual. So I installed Coturn, using the second
> manual, and I thought, that was it, because after entering a room, I saw:
> "Connection to Media server has been established", which I don't remember
> seeing before. But still: no webcam/mic after about 1 minute. Same error.
> >
> > My scenario:
> > It's an intern OpenMeetings-Server, so I don't have to go through any
> firewall. We have about 200 users, who don't use OM all at once, so we
> don't need any high-perfomance-tweaks. As certificate, I use a real
> domain-certificate from an intern Microsoft domain-CA. I didn't follow the
> manual here, but just changed the /opt/open504/conf/server.xml, changing
> the lines [that's the way, someone suggested it here in the mailinglist, as
> I was testing OM5 a few months ago]:
> >
> >     <Connector port="5443"
> protocol="org.apache.coyote.http11.Http11NioProtocol"
> >                maxThreads="150" SSLEnabled="true">
> >         <SSLHostConfig>
> >             <Certificate certificateKeystoreFile="conf/localhost.jks"
> >                          certificateKeystorePassword="openmeetings"
> >                          certificateKeystoreType="JKS"
> >                          certificateVerification="false"
> >                          sslProtocol="TLS"
> >                          type="RSA" />
> >         </SSLHostConfig>
> >     </Connector>
> >
> > into
> >
> >     <Connector port="5443"
> >     SSLEnabled="true">
> >         <SSLHostConfig>
> >             <Certificate certificateFile="/etc/myfirm/myserver.pem"
> >                          certificateKeyFile="/etc/myfirm/key.pem"
> >                          certificateChainFile="/etc/myfirm/chain.pem"
> >                               sslProtocol="TLS"/>
> >         </SSLHostConfig>
> >     </Connector>
> >
> > EXCEPT for that, I think I followed the manuals thoroughly. I got LDAP
> working, HTTPS seems fine. I just can't get a stable webcam/mic.
> >
> > If you think, my certificate-deployment could be the problem, I would
> change that (following the new manual). If not, can you give me some advice
> on where to look? I can post logs, if needed.
> >
> > Best regards,
> > Alex
> >
> >
> >
> >
> > --
> >
> > Best regards,
> > Maxim
> >
> >
> >
> >
> > --
> >
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim
>


-- 
Best regards,
Maxim

Reply via email to