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 <[email protected]>
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 [email protected] <[email protected]>
> 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 <[email protected]>
>> 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?
>>>
>>

Reply via email to