Re: OM and Media server separated-recording issue

Congratulations! - On Fri, 1 Oct 2021 09:26:27 -0600 Jeffry Johnson wrote: > FYI, I had the entire DB dropped and reinstalled 7.0.0 snapshot fresh with > new DB and we are back to seeing everything working as expected. Now we are > pursuing updates from here. THank you all for the marvel

Re: OM and Media server separated-recording issue

Oracle DB works for me as expected (as well as for some other users) So DB shouldn't be a problem On Wed, 22 Sept 2021 at 04:07, Jeffry Johnson wrote: > I am working on a fresh install using mariadb instead of the Oracle sql db > we've been using. Just running into some issues with internet acce

Re: OM and Media server separated-recording issue

I am working on a fresh install using mariadb instead of the Oracle sql db we've been using. Just running into some issues with internet access for the servers in installing on. Waiting on our network team to open it up. I will let you know asap what my findings are On Tue, Sep 21, 2021, 10:16 Alv

Re: OM and Media server separated-recording issue

I just made a fresh installation of Centos 7 and installed OM 6.1.0 following the tutorial. Testing Chrome 93, and later Chromium 90 as user "A", and Chrome 87 and 93, Chromium 92, Safari 14.1.2 and Yandex 21.6 successively as user "B", al them show cams and makes recordings rightly. Firefox brin

Re: OM and Media server separated-recording issue

Don't worry about the files itself. Its the folder that matters. As Maxim suggested, you need to dig a bit deeper: Can you check the table recording_chunk in your OpenMeetings database that it contains an entry with stream of type="SCREEN" for recording_id=568 ? What's that entry looking like? Are

Re: OM and Media server separated-recording issue

So I looked at all the screen files and they all have good recordings of video. I have tried all weekend to set the acl to have x perms and they show on the getfacl for the directories, but every time a new webm files is created it lacks x on ALL levels. On Sun, Sep 19, 2021, 10:18 Maxim Solodovn

Re: OM and Media server separated-recording issue

The error "screenMetaData is Null recordingId 568" usually mean there's no stream for screen sharing available (streams from cameras, microphones might be OK) You need to check what is recorded (A bit detective work) from mobile (sorry for typos ;) On Sun, Sep 19, 2021, 22:28 Alvaro wrote: >

Re: OM and Media server separated-recording issue

...try Sebastian indications... --- On Sat, 18 Sep 2021 12:49:51 -0600 Jeffry Johnson wrote: > I have upgraded to running on tomcat34. Issue remains identical. > > Unfortunately, the version of chrome and ff on my machine are set by the > organization and we are on front motion ff 67 a

Re: OM and Media server separated-recording issue

I have upgraded to running on tomcat34. Issue remains identical. Unfortunately, the version of chrome and ff on my machine are set by the organization and we are on front motion ff 67 and version 92 of chrome. I can't change then. I am attempting to set the facl on the data dir to have x perms on

Re: OM and Media server separated-recording issue

...or Chrome-Chromium 87 On Sat, 18 Sep 2021 10:29:12 +0200 Alvaro wrote: > ...if you are working on CentOS 7 please try > recording with Firefox 78... > > > > > > > On Sat, 18 Sep 2021 08:43:31 +0200 > Alvaro wrote: > > > Hi Sebastian, Jeffry do you install kure

Re: OM and Media server separated-recording issue

...if you are working on CentOS 7 please try recording with Firefox 78... On Sat, 18 Sep 2021 08:43:31 +0200 Alvaro wrote: > Hi Sebastian, Jeffry do you install kurento media server indicating > the path to qcom_data? > Please take a look in the last tutorials for OM 6.1.0 > tha

Re: OM and Media server separated-recording issue

Hi Sebastian, Jeffry do you install kurento media server indicating the path to qcom_data? Please take a look in the last tutorials for OM 6.1.0 that use the script "tomcat34" not "tomcat3" to run OM. Thanks Alvaro --- On Fri, 17 Sep 2021 17:30:54 -0600 Jeffry Johnson wrote: > ok,

Re: OM and Media server separated-recording issue

>From memory I think you still need to chmod +x on the shared drive though to make it writable. Thanks Seb Sebastian Wagner Director Arrakeen Solutions, OM-Hosting.com http://arrakeen-solutions.co.nz/ https://om-hosting.com - Cloud & Server Hosting for HTML5 Video-Conferencing OpenMeetings

Re: OM and Media server separated-recording issue

I will send the db info tomorrow but I can say that I have tomcat running as root because I wrote a service and enabled it in systemd to automatically run when the server is rebooted. On Fri, Sep 17, 2021, 18:51 seba.wag...@gmail.com wrote: > The shared drive needs to be made writable by the ope

Re: OM and Media server separated-recording issue

The shared drive needs to be made writable by the openmeetings user running the OpenMeetings Tomcat service yes. Can you check the table recording_chunk in your OpenMeetings database that it contains an entry with stream of type="SCREEN" for recording_id=568 ? Whats that entry looking like? Thank

Re: OM and Media server separated-recording issue

ok, now i"m getting more confident here. I've redirected the Data Dir to /qcom_data/ on the root directory. THis is the NFS share that our server team set up for me. I accomplished the redirect by inserting the following line into the tomcat3 file: export JAVA_OPTS="-Djava.awt.headless=true -DDATA_

Re: OM and Media server separated-recording issue

Sry that won't be all of the stack trace. There must be some exception / error before that. There is also a way to look at the error in the UI I think. I think there is an icon to see the commands it tried to execute and any errors with it. Maybe have a look at that to read all commands until you

Re: OM and Media server separated-recording issue

ERROR 09-17 17:40:56.229 o.a.o.c.c.RecordingConverter:100 [taskExecutor-1] - [startConversion] org.apache.openmeetings.core.converter.ConversionException: screenMetaData is Null recordingId 567 at org.apache.openmeetings.core.converter.RecordingConverter.startConversion(RecordingConverter.

Re: OM and Media server separated-recording issue

Can you post the actual stack trace? What's the file path, have you verified this file really exists or not? Thanks Seb Sebastian Wagner Director Arrakeen Solutions, OM-Hosting.com http://arrakeen-solutions.co.nz/ https://om-hosting.com - Cloud & Server Hosting for HTML5 Video-Conferencing OpenMe

Re: OM and Media server separated-recording issue

Error in the application is file not found. In the logs the error is that the metadata is null. On Fri, Sep 17, 2021, 16:14 seba.wag...@gmail.com wrote: > Sry I think you just need to fix your shared drive. I have been mounting > NFS drives before and I have not seen any such issues. > > What is

Re: OM and Media server separated-recording issue

Sry I think you just need to fix your shared drive. I have been mounting NFS drives before and I have not seen any such issues. What is your error? File not found? Have you checked the path in the exception stack trace message and if that resolves to an actual file or not? Thanks Sebastian Sebas

OM and Media server separated-recording issue

We discovered we had an issue with recordings and I believe it's because we separated our media server and om server for stability. I had an nfs mounted share created and now we are seeing the webm files. The issue now is, I believe, that the prices to convert the recording is being kicked off bef