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 see the initial/first error in this processing chain. The location exists, I can see the webm files now that our Server team > created the NFS mount for me. That is just half the job. You also need to tell OpenMeetings the new location of your shared files/drive. Otherwise it assumes it is relative to the path of OpenMeetings base installation. You achieve that by either: A) Mount the same shared drive replacing the default "data" folder in $OPENMEETINGS_HOME/webapps/openmeetings/data or better: B) Point OpenMeetings Data directory to your shared drive location using the DATA_DIR parameter An example how to pass in the DATA_DIR when starting OpenMeetings up is in the Docker script for the OpenMeetings image: https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L43 (A) can be a bit tricky if you don't know the internal folder structure of OpenMeetings that well. Please keep in mind that changing the data dir means _all_ files are on the shared drive. Not just recordings. So you may need to move all existing files from the current OpenMeetings data folder to the shared drive. Which again can be a bit tricky if you happen to mess up the exact folder paths to match. 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 <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> On Sat, 18 Sept 2021 at 10:57, Jeffry Johnson <jeffry.s.john...@gmail.com> wrote: > 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.java:58) > at > org.apache.openmeetings.core.remote.StreamProcessor.lambda$startConvertion$10(StreamProcessor.java:439) > 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:829) > > > Is this what you mean? If I seem inept it's because I only started this job > less than 4 months ago with ZERO experience in any of this and have had to > learn it all on the fly. The location exists, I can see the webm files now > that our Server team created the NFS mount for me. > > > On Fri, Sep 17, 2021 at 4:45 PM seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> 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 OpenMeetings >> >> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> >> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >> >> >> On Sat, 18 Sept 2021 at 10:29, Jeffry Johnson <jeffry.s.john...@gmail.com> >> wrote: >> >>> 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 <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 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 >>>> >>>> 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 >>>> >>>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> >>>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >>>> >>>> >>>> On Sat, 18 Sept 2021 at 10:04, Jeffry Johnson < >>>> jeffry.s.john...@gmail.com> wrote: >>>> >>>>> 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 before the file is seen by om in the data directory. >>>>> Has this been encountered before? Should we put in a delay in the >>>>> conversion function? If so, where would be the best place to put that >>>>> delay >>>>> in? >>>>> >>>>
