Re: OM and Media server separated-recording issue

2021-09-17 Thread Jeffry Johnson
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread Jeffry Johnson
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread seba.wag...@gmail.com
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

2021-09-17 Thread seba.wag...@gmail.com
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread Jeffry Johnson
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread Jeffry Johnson
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

OM and Media server separated-recording issue

2021-09-17 Thread Jeffry Johnson
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread seba.wag...@gmail.com
>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

2021-09-17 Thread seba.wag...@gmail.com
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

Re: OM and Media server separated-recording issue

2021-09-17 Thread seba.wag...@gmail.com
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?