sure, Thanks for the testing :))
On Tue, 31 Mar 2020 at 18:59, Mikhail Zhmurin <zhmurin.mikh...@gmail.com> wrote: > And once again thank you for your patience and your help! As soon as all > the conferences will end tonight I will try to install the snapshot you > shared and I will get back to you with that chrome hash problem. > > вт, 31 мар. 2020 г. в 17:56, Maxim Solodovnik <solomax...@gmail.com>: > >> NP :) >> we all humans >> >> I personally prefer the new way of starting Om under Ubuntu >> it is `openmeetings.service` bundled with OM >> and instructions are inside :) >> >> On Tue, 31 Mar 2020 at 18:51, Mikhail Zhmurin <zhmurin.mikh...@gmail.com> >> wrote: >> >>> Well I guess i'm just really dumb then. Sorry for waisting your time. To >>> start it properly I should use /etc/init.d/tomcat3 where user "nobody" >>> specified instead of service tomcat3 start that runs under root? Once again >>> sorry for this rookie mistakes it never crossed my mind that this could be >>> the reason. >>> >>> вт, 31 мар. 2020 г. в 17:39, Maxim Solodovnik <solomax...@gmail.com>: >>> >>>> Well >>>> >>>> This line: >>>> root 2092 1 0 Mar29 ? >>>> >>>> Actually means: Process with ID `2092` was started as user `root` >>>> ............... >>>> >>>> On Tue, 31 Mar 2020 at 18:35, Mikhail Zhmurin < >>>> zhmurin.mikh...@gmail.com> wrote: >>>> >>>>> root 2092 1 0 Mar29 ? 00:10:15 /usr/bin/java >>>>> -Djava.util.logging.config.file=/opt/open503/conf/logging.properties >>>>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >>>>> -Djdk.tls.ephemeralDHKeySize=2048 >>>>> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources >>>>> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 >>>>> -Dignore.endorsed.dirs= -classpath >>>>> /opt/open503/bin/bootstrap.jar:/opt/open503/bin/tomcat-juli.jar >>>>> -Dcatalina.base=/opt/open503 -Dcatalina.home=/opt/open503 >>>>> -Djava.io.tmpdir=/opt/open503/temp org.apache.catalina.startup.Bootstrap >>>>> -u >>>>> *nobody* -Dcatalina.base start >>>>> root 8251 22420 0 17:34 pts/2 00:00:00 grep --color=auto java >>>>> root 15608 1 21 Mar29 ? 10:08:21 /usr/bin/java >>>>> -Djava.util.logging.config.file=/opt/open503/conf/logging.properties >>>>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >>>>> -Djdk.tls.ephemeralDHKeySize=2048 >>>>> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources >>>>> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 >>>>> -Dignore.endorsed.dirs= -classpath >>>>> /opt/open503/bin/bootstrap.jar:/opt/open503/bin/tomcat-juli.jar >>>>> -Dcatalina.base=/opt/open503 -Dcatalina.home=/opt/open503 >>>>> -Djava.io.tmpdir=/opt/open503/temp org.apache.catalina.startup.Bootstrap >>>>> -u >>>>> *nobody* -Dcatalina.base start >>>>> root 31985 1 42 01:31 ? 06:46:15 /usr/bin/java >>>>> -Djava.util.logging.config.file=/opt/open503/conf/logging.properties >>>>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >>>>> -Djdk.tls.ephemeralDHKeySize=2048 >>>>> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources >>>>> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 >>>>> -Dignore.endorsed.dirs= -classpath >>>>> /opt/open503/bin/bootstrap.jar:/opt/open503/bin/tomcat-juli.jar >>>>> -Dcatalina.base=/opt/open503 -Dcatalina.home=/opt/open503 >>>>> -Djava.io.tmpdir=/opt/open503/temp org.apache.catalina.startup.Bootstrap >>>>> -u >>>>> *nobody* -Dcatalina.base start >>>>> >>>>> вт, 31 мар. 2020 г. в 17:33, Maxim Solodovnik <solomax...@gmail.com>: >>>>> >>>>>> This is usually means OM is run using user `root` >>>>>> >>>>>> `ps -ef|grep java` ?? >>>>>> >>>>>> On Tue, 31 Mar 2020 at 18:32, Mikhail Zhmurin < >>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>> >>>>>>> Hmm I think you were right. For some reasons root creates new >>>>>>> folders for rooms from moodle. What should I do? >>>>>>> drwxr-x--- 2 nobody root 4096 Feb 14 16:04 2 >>>>>>> drwxr-x--- 2 nobody root 4096 Mar 29 18:22 22 >>>>>>> drwxr-x--- 2 nobody root 4096 Feb 14 16:04 3 >>>>>>> drwxr-x--- 2 nobody root 4096 Mar 30 17:02 30 >>>>>>> drwxr-x--- 2 root root 4096 Mar 31 09:44 362 >>>>>>> drwxr-x--- 2 nobody root 4096 Mar 29 18:28 365 >>>>>>> drwxr-x--- 2 nobody root 4096 Mar 21 17:07 37 >>>>>>> drwxr-x--- 2 nobody root 4096 Mar 21 17:05 39 >>>>>>> drwxr-x--- 2 nobody root 4096 Feb 14 16:04 4 >>>>>>> drwxr-x--- 2 root root 4096 Mar 31 10:06 422 >>>>>>> drwxr-x--- 2 root root 4096 Mar 31 01:23 426 >>>>>>> drwxr-x--- 2 root root 4096 Mar 31 01:16 427 >>>>>>> >>>>>>> вт, 31 мар. 2020 г. в 17:27, Maxim Solodovnik <solomax...@gmail.com >>>>>>> >: >>>>>>> >>>>>>>> Sounds like folder permissions >>>>>>>> Do "ls -la" and check owners >>>>>>>> >>>>>>>> On Tue, Mar 31, 2020, 18:23 Mikhail Zhmurin < >>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>> >>>>>>>>> .webm should be created in the room folder or in the stream >>>>>>>>> folder? By that I mean when I start the recording in the room for the >>>>>>>>> first time OM creates a folder inside STREAM folder and names it >>>>>>>>> using ID >>>>>>>>> of the room. Ok so I checked and TEST_SETUP webms are definitely being >>>>>>>>> created and I'm able to play them back when testing audio video >>>>>>>>> devices >>>>>>>>> inside the room. BUT when i'm trying to record inside the room OM >>>>>>>>> doesn't >>>>>>>>> create webms even though it says it did(check logs a attached below). >>>>>>>>> When startin recording (look for logs for room 426) >>>>>>>>> DEBUG 03-31 17:12:19.864 o.a.o.c.r.KurentoHandler:221 >>>>>>>>> [io-5443-exec-49] - Searching for room 426 >>>>>>>>> DEBUG 03-31 17:12:19.865 o.a.o.c.r.KurentoHandler:235 >>>>>>>>> [io-5443-exec-49] - Room 426 found! >>>>>>>>> DEBUG 03-31 17:12:19.865 o.a.o.c.r.KurentoHandler:221 >>>>>>>>> [io-5443-exec-49] - Searching for room 426 >>>>>>>>> DEBUG 03-31 17:12:19.866 o.a.o.c.r.KurentoHandler:235 >>>>>>>>> [io-5443-exec-49] - Room 426 found! >>>>>>>>> DEBUG 03-31 17:12:19.866 o.a.o.c.r.KRoom:146 [io-5443-exec-49] - >>>>>>>>> ##REC:: recording in room 426 is starting :: >>>>>>>>> DEBUG 03-31 17:12:19.867 o.a.o.c.r.KRoom:171 [io-5443-exec-49] - >>>>>>>>> ##REC:: recording created by USER: 372 >>>>>>>>> DEBUG 03-31 17:12:19.873 o.a.o.d.d.r.PollDao:104 [Thread-2113337] >>>>>>>>> - :: hasPoll :: 414 >>>>>>>>> DEBUG 03-31 17:12:19.880 o.a.o.d.d.r.PollDao:98 [Thread-2113337] - >>>>>>>>> :: getArchived :: 414 >>>>>>>>> DEBUG 03-31 17:12:19.887 o.a.o.c.r.KurentoHandler:221 >>>>>>>>> [Thread-2113337] - Searching for room 414 >>>>>>>>> DEBUG 03-31 17:12:19.888 o.a.o.c.r.KurentoHandler:235 >>>>>>>>> [Thread-2113337] - Room 414 found! >>>>>>>>> DEBUG 03-31 17:12:19.889 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? false >>>>>>>>> DEBUG 03-31 17:12:19.890 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? false >>>>>>>>> DEBUG 03-31 17:12:19.890 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? false >>>>>>>>> DEBUG 03-31 17:12:19.890 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? false >>>>>>>>> DEBUG 03-31 17:12:19.891 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? false >>>>>>>>> DEBUG 03-31 17:12:19.891 o.a.o.c.r.KStream:213 [io-5443-exec-49] - >>>>>>>>> startRecord outMedia OK ? true >>>>>>>>> INFO 03-31 17:12:19.893 o.a.o.u.OmFileHelper:234 >>>>>>>>> [io-5443-exec-49] - Configured to record to >>>>>>>>> file:///opt/open503/webapps/openmeetings/data/streams/426/rec_4220_a643d852-a8c0-41b8-92f8-bcbb9dfaed3f.webm >>>>>>>>> Logs when recording is stopped >>>>>>>>> EBUG 03-31 17:15:37.751 o.a.o.c.c.RecordingConverter:52 >>>>>>>>> [taskExecutor-1] - recording 4220 >>>>>>>>> DEBUG 03-31 17:15:37.754 o.a.o.c.r.KRoom:220 [io-5443-exec-33] - >>>>>>>>> ##REC:: recording in room 426 is stopped :: >>>>>>>>> ERROR 03-31 17:15:37.757 o.a.o.c.c.RecordingConverter:111 >>>>>>>>> [taskExecutor-1] - [startConversion] >>>>>>>>> org.apache.openmeetings.core.converter.ConversionException: >>>>>>>>> screenMetaData is Null recordingId 4220 >>>>>>>>> at >>>>>>>>> org.apache.openmeetings.core.converter.RecordingConverter.startConversion(RecordingConverter.java:59) >>>>>>>>> at >>>>>>>>> org.apache.openmeetings.core.remote.StreamProcessor.lambda$startConvertion$9(StreamProcessor.java:447) >>>>>>>>> at >>>>>>>>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) >>>>>>>>> at >>>>>>>>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) >>>>>>>>> at java.base/java.lang.Thread.run(Thread.java:834) >>>>>>>>> вт, 31 мар. 2020 г. в 16:19, Maxim Solodovnik < >>>>>>>>> solomax...@gmail.com>: >>>>>>>>> >>>>>>>>>> well, >>>>>>>>>> >>>>>>>>>> stream doesn't exist and recording stopped are different issues :) >>>>>>>>>> the latter was reported as >>>>>>>>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2206 (with no >>>>>>>>>> clear steps) >>>>>>>>>> >>>>>>>>>> coturn user shouldn't be an issue, BUT i run it as user `nobody` >>>>>>>>>> (just in case) >>>>>>>>>> please check if when you start recording *.webm files are created >>>>>>>>>> or not? >>>>>>>>>> Also check file owner/permission on OM folders (especially `data` >>>>>>>>>> dir) >>>>>>>>>> >>>>>>>>>> On Tue, 31 Mar 2020 at 17:14, Mikhail Zhmurin < >>>>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I will try to use this snapshot and get back to you with results. >>>>>>>>>>> About recording: it says "recording file is not found". Stream >>>>>>>>>>> folder of the room is empty. KMS and OM are running under user >>>>>>>>>>> "nobody" BUT >>>>>>>>>>> since I'm behind NAT I'm using coturn which uses "kurento" as a >>>>>>>>>>> coturn >>>>>>>>>>> user. Could this be the problem? Also I noticed one interesting >>>>>>>>>>> detail, >>>>>>>>>>> when I reload my vps the recording actually works for a while and om >>>>>>>>>>> renders it in mp4. But after a while it just stops working and I get >>>>>>>>>>> DEBUG 03-31 16:13:24.439 o.a.o.c.r.KRoom:195 [nio-5443-exec-7] - >>>>>>>>>>> ##REC:: recording in room 426 is stopping 4172 :: >>>>>>>>>>> DEBUG 03-31 16:13:24.495 o.a.o.c.c.RecordingConverter:52 >>>>>>>>>>> [taskExecutor-2] - recording 4172 >>>>>>>>>>> DEBUG 03-31 16:13:24.497 o.a.o.c.r.KRoom:220 [nio-5443-exec-7] - >>>>>>>>>>> ##REC:: recording in room 426 is stopped :: >>>>>>>>>>> ERROR 03-31 16:13:24.499 o.a.o.c.c.RecordingConverter:111 >>>>>>>>>>> [taskExecutor-2] - [startConversion] >>>>>>>>>>> org.apache.openmeetings.core.converter.ConversionException: >>>>>>>>>>> screenMetaData is Null recordingId 4172 >>>>>>>>>>> >>>>>>>>>>> вт, 31 мар. 2020 г. в 15:16, Maxim Solodovnik < >>>>>>>>>>> solomax...@gmail.com>: >>>>>>>>>>> >>>>>>>>>>>> Databases are not compatible >>>>>>>>>>>> Usually for testing I'm starting new OM with internal H2 DB, >>>>>>>>>>>> this way original db remain unchanged :)) >>>>>>>>>>>> >>>>>>>>>>>> Your recording issues can be caused by >>>>>>>>>>>> 1) the fact OM and KMS were started using different accounts >>>>>>>>>>>> 2) missing converters >>>>>>>>>>>> >>>>>>>>>>>> click exclamation icon to see dialog with results >>>>>>>>>>>> >>>>>>>>>>>> On Tue, 31 Mar 2020 at 16:10, Mikhail Zhmurin < >>>>>>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Is it possible to somehow use existing db with this snapshot? >>>>>>>>>>>>> Because I'm pretty sure clear snapshot will do me no good. Also >>>>>>>>>>>>> I'm facing >>>>>>>>>>>>> problems with recordings they show up with yellow exclamation >>>>>>>>>>>>> mark in om >>>>>>>>>>>>> after I stop the recording and the stream folder of the room is >>>>>>>>>>>>> just empty. >>>>>>>>>>>>> Should I create another thread or we can continue here? >>>>>>>>>>>>> >>>>>>>>>>>>> вт, 31 мар. 2020 г. в 13:49, Maxim Solodovnik < >>>>>>>>>>>>> solomax...@gmail.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Well, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I would prefer if you can set up M4-SNAPSHOT and check if >>>>>>>>>>>>>> Moodle user can login >>>>>>>>>>>>>> This will require modified Moodle plugin (available in >>>>>>>>>>>>>> sources only >>>>>>>>>>>>>> https://github.com/openmeetings/openmeetings-moodle-plugin) >>>>>>>>>>>>>> Or if the issue is reproducible for you >>>>>>>>>>>>>> Maybe you can share your steps? >>>>>>>>>>>>>> Everything works as expected at my test system :( >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, 31 Mar 2020 at 14:11, Mikhail Zhmurin < >>>>>>>>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Ok that definetely worked! That's one problem solved! Thank >>>>>>>>>>>>>>> you very much. Still the problem with chrome stays. You >>>>>>>>>>>>>>> mentioned earlier >>>>>>>>>>>>>>> about this fix >>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2202 . >>>>>>>>>>>>>>> Does this address incorrect hash problem for chrome? If yes >>>>>>>>>>>>>>> what should I >>>>>>>>>>>>>>> do with this? Sorry for asking suck a newbie questions, I'm >>>>>>>>>>>>>>> fairly new to >>>>>>>>>>>>>>> system administration in general. If you need validation that >>>>>>>>>>>>>>> I'm >>>>>>>>>>>>>>> accesing om rooms from moodle having only 1 om tab opened I can >>>>>>>>>>>>>>> record a >>>>>>>>>>>>>>> video. I can also ask my colleague to make the video where he >>>>>>>>>>>>>>> succesfully logs into the room in chrome using the exact same >>>>>>>>>>>>>>> moodle user. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> вт, 31 мар. 2020 г. в 12:27, Maxim Solodovnik < >>>>>>>>>>>>>>> solomax...@gmail.com>: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> yep >>>>>>>>>>>>>>>> I was right: >>>>>>>>>>>>>>>> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy#Directives >>>>>>>>>>>>>>>> `display-capture >>>>>>>>>>>>>>>> <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy/display-capture>` >>>>>>>>>>>>>>>> should be added >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> can you try to add it locally (into `renderer.php`) and >>>>>>>>>>>>>>>> tell me if it will help? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, 31 Mar 2020 at 13:20, Maxim Solodovnik < >>>>>>>>>>>>>>>> solomax...@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Screen-sharing might be some additional restriction for >>>>>>>>>>>>>>>>> `iframe-based-paged` >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://github.com/openmeetings/openmeetings-moodle-plugin/blob/master/renderer.php#L138 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> And this might be FF limitation only >>>>>>>>>>>>>>>>> (I'll check) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Have you tried latest SNAPSHOT? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Mar 2020 at 13:15, Mikhail Zhmurin < >>>>>>>>>>>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Unfortunately I was not able to solve it using links you >>>>>>>>>>>>>>>>>> provided. >>>>>>>>>>>>>>>>>> To answer your questions: >>>>>>>>>>>>>>>>>> 1. We are using let'encrypt for ssl certificates >>>>>>>>>>>>>>>>>> 2. "Modulekey" is unique for every moodle instance >>>>>>>>>>>>>>>>>> Another thing I noticed about firefox: when I'm >>>>>>>>>>>>>>>>>> authorizing through moodle (when logging through moodle >>>>>>>>>>>>>>>>>> domain name remains >>>>>>>>>>>>>>>>>> the same) in firefox I can acces the room but cannot start >>>>>>>>>>>>>>>>>> screensharing with error " NotAllowedError: The request is >>>>>>>>>>>>>>>>>> not allowed by >>>>>>>>>>>>>>>>>> the user agent or the platform in the current context." BUT >>>>>>>>>>>>>>>>>> when I'm >>>>>>>>>>>>>>>>>> logging in firefox directly into OM (using om's own domain >>>>>>>>>>>>>>>>>> name) and >>>>>>>>>>>>>>>>>> accesing rooms from om's dashboard screensharing is working >>>>>>>>>>>>>>>>>> fine. Users who >>>>>>>>>>>>>>>>>> are able to acces rooms through moodle in chrome have no >>>>>>>>>>>>>>>>>> problems >>>>>>>>>>>>>>>>>> accesing screensharing. I'm growing suspicious that >>>>>>>>>>>>>>>>>> certificates that I >>>>>>>>>>>>>>>>>> installed for moodle might be the cause because one way or >>>>>>>>>>>>>>>>>> another logging >>>>>>>>>>>>>>>>>> through moodle causes different problems in different >>>>>>>>>>>>>>>>>> browsers but logging >>>>>>>>>>>>>>>>>> directly into OM through om's own domen name shows no >>>>>>>>>>>>>>>>>> problems on both >>>>>>>>>>>>>>>>>> browsers. Keep in mind that I logged into OM directly using >>>>>>>>>>>>>>>>>> only admin's >>>>>>>>>>>>>>>>>> account . Never checked direct om authorization with moodle >>>>>>>>>>>>>>>>>> users because >>>>>>>>>>>>>>>>>> moodle users don't have rights to acces om's dashboard. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> вт, 31 мар. 2020 г. в 11:41, Maxim Solodovnik < >>>>>>>>>>>>>>>>>> solomax...@gmail.com>: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This one I have already answered :))) >>>>>>>>>>>>>>>>>>> https://markmail.org/message/a7quq4clhxoojrc5 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> send some links >>>>>>>>>>>>>>>>>>> ask questions >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> can you answer those? >>>>>>>>>>>>>>>>>>> Additionally one NPE was fixed >>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2202 >>>>>>>>>>>>>>>>>>> Can you check if latest SNAPSHOT works better? ( >>>>>>>>>>>>>>>>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/ >>>>>>>>>>>>>>>>>>> ) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Tue, 31 Mar 2020 at 12:18, Mikhail Zhmurin < >>>>>>>>>>>>>>>>>>> zhmurin.mikh...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hello, I’m having a weird issue. When I’m trying to >>>>>>>>>>>>>>>>>>>> acces the room in OM from moodle I’m getting invalid hash >>>>>>>>>>>>>>>>>>>> error. What’s >>>>>>>>>>>>>>>>>>>> weird it’s that it works just fine in firefox but I’m >>>>>>>>>>>>>>>>>>>> getting “acces >>>>>>>>>>>>>>>>>>>> denied. You have no rights to enter this room ” in chrome. >>>>>>>>>>>>>>>>>>>> I’ve read here >>>>>>>>>>>>>>>>>>>> that it might happen if you have OM opened in 2 tabs, I’ve >>>>>>>>>>>>>>>>>>>> checked it in >>>>>>>>>>>>>>>>>>>> incognito with 1 tab only, closed everything else, issue >>>>>>>>>>>>>>>>>>>> stays. I have >>>>>>>>>>>>>>>>>>>> multiple moodle instances using 1 om. “Modulekeys” are >>>>>>>>>>>>>>>>>>>> different for each >>>>>>>>>>>>>>>>>>>> moodle instance. We’ve noticed that we have multiple users >>>>>>>>>>>>>>>>>>>> from different >>>>>>>>>>>>>>>>>>>> moodle instances under the same login. We deleted those >>>>>>>>>>>>>>>>>>>> users but the issue >>>>>>>>>>>>>>>>>>>> stays. Another weird thing is, same user can acces the >>>>>>>>>>>>>>>>>>>> room in chrome from >>>>>>>>>>>>>>>>>>>> 1 pc but cannot do it from another pc. You may say that >>>>>>>>>>>>>>>>>>>> the issue is with >>>>>>>>>>>>>>>>>>>> the particular pc but one of the moodle instances has like >>>>>>>>>>>>>>>>>>>> 150 users and >>>>>>>>>>>>>>>>>>>> about 20% of users reporting this problem in chrome and >>>>>>>>>>>>>>>>>>>> not a single >>>>>>>>>>>>>>>>>>>> problem with firefox. We installed 2 identical chrome >>>>>>>>>>>>>>>>>>>> versions on 2 >>>>>>>>>>>>>>>>>>>> different pcs one logs in with no problem and the other >>>>>>>>>>>>>>>>>>>> one getting error. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Here’s some logs >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> ERROR 03-31 10:55:47.566 >>>>>>>>>>>>>>>>>>>> o.a.w.DefaultExceptionMapper:170 [io-5443-exec-22] - >>>>>>>>>>>>>>>>>>>> Unexpected error >>>>>>>>>>>>>>>>>>>> occurred >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException: null >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I’m really lost at this point, please help. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Отправлено из приложения "Почта >>>>>>>>>>>>>>>>>>>> <https://go.microsoft.com/fwlink/?LinkId=550986>" для >>>>>>>>>>>>>>>>>>>> Windows 10 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> WBR >>>>>>>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> WBR >>>>>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> WBR >>>>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> WBR >>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> WBR >>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> WBR >>>>>>>>>> Maxim aka solomax >>>>>>>>>> >>>>>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >> >> -- >> WBR >> Maxim aka solomax >> > -- WBR Maxim aka solomax
