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 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?

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

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




On Sat, 18 Sept 2021 at 10:04, Jeffry Johnson 
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?
>

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 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
>
> 
> 
>
>
> On Sat, 18 Sept 2021 at 10:04, Jeffry Johnson 
> 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?
>>
>

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 OpenMeetings




On Sat, 18 Sept 2021 at 10:29, Jeffry Johnson 
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 
> 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
>>
>> 
>> 
>>
>>
>> On Sat, 18 Sept 2021 at 10:04, Jeffry Johnson 
>> 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?
>>>
>>

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 
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 
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
>
> 
> 
>
>
> On Sat, 18 Sept 2021 at 10:29, Jeffry Johnson 
> 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 
>> 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
>>>
>>> 
>>> 
>>>
>>>
>>> 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?

>>>

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 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




On Sat, 18 Sept 2021 at 10:57, Jeffry Johnson 
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
>>
>> 
>> 
>>
>>
>> On Sat, 18 Sept 2021 at 10:29, Jeffry Johnson 
>> 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 
>>> 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

 
 


 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 o

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 -DDATA_DIR=/qcom_data/"

Here is what the files look like after stopping the recording:

[image: image.png]

This is what appears when clicking the caution icon:

[image: image.png]

Here are the streaming files in the right directory:

[image: image.png]

Here is the full stack trace from beginning of recording to the end in the
logs:

DEBUG 09-17 19:21:56.691 o.a.o.c.r.KRoom:120 [ventExec-e2-t23] - ##REC::
recording in room 241 is starting ::
DEBUG 09-17 19:21:56.692 o.a.o.c.r.KRoom:147 [ventExec-e2-t23] - ##REC::
recording created by USER: 1
DEBUG 09-17 19:21:56.718 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3031263214
1 tcp 1518280447 10.43.204.201 9 typ host tcptype active generation 0 ufrag
Fie8 network-id
1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:56.725 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:2078137933
1 tcp 1518217471 2601:680:ca00:6cb0:7584:5137:c3a5:f49 9 typ host tcptype
active generation 0 ufrag Fie8 network-id 3 network-cost
10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:56.730 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:1021992780
1 tcp 1518151935 2601:680:ca00:6cb0::635 9 typ host tcptype active
generation 0 ufrag Fie8 network-id 4 network-cost
10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:56.735 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:428269470
1 tcp 1518086399 2601:680:ca00:6cb0:d4ec:98a1:247d:6c5a 9 typ host tcptype
active generation 0 ufrag Fie8 network-id 5 network-cost
10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:56.740 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3105188002
1 tcp 1518018303 10.0.0.202 9 typ host tcptype active generation 0 ufrag
Fie8 network-id 2 network-cost
10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:56.825 o.a.o.c.r.KurentoHandler:502 [pool-3-thread-6] -
Kurento::ObjectCreated -> New Endpoint
8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint
detected, tags: {uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd,
outUid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd}, kStream: KStream
[kRoom=org.apache.openmeetings.core.remote.KRoom@42c72392,
streamType=SCREEN, profile=WEBM_VIDEO_ONLY, recorder=null,
outgoingMedia=[RemoteObject: type=WebRtcEndpoint
remoteRef=8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint],
listeners={}, flowoutFuture=Optional.empty, chunkId=null, type=SCREEN,
sid=7c541378-cf4c-429a-9a89-e9be993c8897,
uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd]
DEBUG 09-17 19:21:56.889 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-3] -
Incoming message from user with ID '1':
{"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:133411719
1 udp 41885439 172.17.129.147 57439 typ relay raddr 10.43.204.201 rport
54669 generation 0 ufrag Fie8 network-id
1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
DEBUG 09-17 19:21:57.687 o.a.o.c.r.KStream:345 [ventExec-e2-t23] -
startRecord outMedia OK ? true
 INFO 09-17 19:21:57.688 o.a.o.u.OmFileHelper:236 [ventExec-e2-t23] -
Configured to record to
file:///qcom_data/streams/241/rec_568_06e13054-286a-4b18-8959-15980ded64e9.webm
DEBUG 09-17 19:21:57.691 o.a.o.c.r.KurentoHandler:433 [ventExec-e2-t28] -
Kurento::ObjectCreated -> [RemoteObject: type=RecorderEndpoint
remoteRef=8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/e6fe24a7-1073-4e06-a657-329214ec7e72_kurento.RecorderEndpoint],
source [RemoteObject: type=ServerManager remoteRef=manager_ServerManager]
DEBUG 09-17 19:21:57.701 o.a.o.c.r.KStream:345 [ventExec-e2-t23] -
startRe

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?

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




On Sat, 18 Sept 2021 at 11:31, Jeffry Johnson 
wrote:

> 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_DIR=/qcom_data/"
>
> Here is what the files look like after stopping the recording:
>
> [image: image.png]
>
> This is what appears when clicking the caution icon:
>
> [image: image.png]
>
> Here are the streaming files in the right directory:
>
> [image: image.png]
>
> Here is the full stack trace from beginning of recording to the end in the
> logs:
>
> DEBUG 09-17 19:21:56.691 o.a.o.c.r.KRoom:120 [ventExec-e2-t23] - ##REC::
> recording in room 241 is starting ::
> DEBUG 09-17 19:21:56.692 o.a.o.c.r.KRoom:147 [ventExec-e2-t23] - ##REC::
> recording created by USER: 1
> DEBUG 09-17 19:21:56.718 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3031263214
> 1 tcp 1518280447 10.43.204.201 9 typ host tcptype active generation 0 ufrag
> Fie8 network-id
> 1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.725 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:2078137933
> 1 tcp 1518217471 2601:680:ca00:6cb0:7584:5137:c3a5:f49 9 typ host tcptype
> active generation 0 ufrag Fie8 network-id 3 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.730 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:1021992780
> 1 tcp 1518151935 2601:680:ca00:6cb0::635 9 typ host tcptype active
> generation 0 ufrag Fie8 network-id 4 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.735 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:428269470
> 1 tcp 1518086399 2601:680:ca00:6cb0:d4ec:98a1:247d:6c5a 9 typ host tcptype
> active generation 0 ufrag Fie8 network-id 5 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.740 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3105188002
> 1 tcp 1518018303 10.0.0.202 9 typ host tcptype active generation 0 ufrag
> Fie8 network-id 2 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.825 o.a.o.c.r.KurentoHandler:502 [pool-3-thread-6] -
> Kurento::ObjectCreated -> New Endpoint
> 8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint
> detected, tags: {uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd,
> outUid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd}, kStream: KStream
> [kRoom=org.apache.openmeetings.core.remote.KRoom@42c72392,
> streamType=SCREEN, profile=WEBM_VIDEO_ONLY, recorder=null,
> outgoingMedia=[RemoteObject: type=WebRtcEndpoint
> remoteRef=8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint],
> listeners={}, flowoutFuture=Optional.empty, chunkId=null, type=SCREEN,
> sid=7c541378-cf4c-429a-9a89-e9be993c8897,
> uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd]
> DEBUG 09-17 19:21:56.889 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-3] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:133411719
> 1 udp 41885439 172.17.129.147 57439 typ relay raddr 10.43.204.201 rport
> 54669

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 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?
>
> 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
>
> 
> 
>
>
> On Sat, 18 Sept 2021 at 11:31, Jeffry Johnson 
> wrote:
>
>> 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_DIR=/qcom_data/"
>>
>> Here is what the files look like after stopping the recording:
>>
>> [image: image.png]
>>
>> This is what appears when clicking the caution icon:
>>
>> [image: image.png]
>>
>> Here are the streaming files in the right directory:
>>
>> [image: image.png]
>>
>> Here is the full stack trace from beginning of recording to the end in
>> the logs:
>>
>> DEBUG 09-17 19:21:56.691 o.a.o.c.r.KRoom:120 [ventExec-e2-t23] - ##REC::
>> recording in room 241 is starting ::
>> DEBUG 09-17 19:21:56.692 o.a.o.c.r.KRoom:147 [ventExec-e2-t23] - ##REC::
>> recording created by USER: 1
>> DEBUG 09-17 19:21:56.718 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
>> Incoming message from user with ID '1':
>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3031263214
>> 1 tcp 1518280447 10.43.204.201 9 typ host tcptype active generation 0 ufrag
>> Fie8 network-id
>> 1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>> DEBUG 09-17 19:21:56.725 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
>> Incoming message from user with ID '1':
>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:2078137933
>> 1 tcp 1518217471 2601:680:ca00:6cb0:7584:5137:c3a5:f49 9 typ host tcptype
>> active generation 0 ufrag Fie8 network-id 3 network-cost
>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>> DEBUG 09-17 19:21:56.730 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
>> Incoming message from user with ID '1':
>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:1021992780
>> 1 tcp 1518151935 2601:680:ca00:6cb0::635 9 typ host tcptype active
>> generation 0 ufrag Fie8 network-id 4 network-cost
>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>> DEBUG 09-17 19:21:56.735 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
>> Incoming message from user with ID '1':
>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:428269470
>> 1 tcp 1518086399 2601:680:ca00:6cb0:d4ec:98a1:247d:6c5a 9 typ host tcptype
>> active generation 0 ufrag Fie8 network-id 5 network-cost
>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>> DEBUG 09-17 19:21:56.740 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
>> Incoming message from user with ID '1':
>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3105188002
>> 1 tcp 1518018303 10.0.0.202 9 typ host tcptype active generation 0 ufrag
>> Fie8 network-id 2 network-cost
>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>> DEBUG 09-17 19:21:56.825 o.a.o.c.r.KurentoHandler:502 [pool-3-thread-6] -
>> Kurento::ObjectCreated -> New Endpoint
>> 8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint
>> detected, tags: {uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd,
>> outUid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd}, kStream: KStream
>> [kRoom=org.apache.openmeetings.core.remote.KRoom@42c72392,
>> streamType=SCREEN, profile=WEBM_VIDEO_ONLY, recorder=null,
>> outgoingMedia=[RemoteObject: type=WebRtcEndpoint
>> remoteRef=8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint],
>> listeners={}, flowoutFuture=Optional.empty, chunkId=null, type=SCREEN,
>> sid=7c541378-cf4c-429

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




On Sat, 18 Sept 2021 at 14:35, Jeffry Johnson 
wrote:

> 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 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?
>>
>> 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
>>
>> 
>> 
>>
>>
>> On Sat, 18 Sept 2021 at 11:31, Jeffry Johnson 
>> wrote:
>>
>>> 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_DIR=/qcom_data/"
>>>
>>> Here is what the files look like after stopping the recording:
>>>
>>> [image: image.png]
>>>
>>> This is what appears when clicking the caution icon:
>>>
>>> [image: image.png]
>>>
>>> Here are the streaming files in the right directory:
>>>
>>> [image: image.png]
>>>
>>> Here is the full stack trace from beginning of recording to the end in
>>> the logs:
>>>
>>> DEBUG 09-17 19:21:56.691 o.a.o.c.r.KRoom:120 [ventExec-e2-t23] - ##REC::
>>> recording in room 241 is starting ::
>>> DEBUG 09-17 19:21:56.692 o.a.o.c.r.KRoom:147 [ventExec-e2-t23] - ##REC::
>>> recording created by USER: 1
>>> DEBUG 09-17 19:21:56.718 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7]
>>> - Incoming message from user with ID '1':
>>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3031263214
>>> 1 tcp 1518280447 10.43.204.201 9 typ host tcptype active generation 0 ufrag
>>> Fie8 network-id
>>> 1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>>> DEBUG 09-17 19:21:56.725 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7]
>>> - Incoming message from user with ID '1':
>>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:2078137933
>>> 1 tcp 1518217471 2601:680:ca00:6cb0:7584:5137:c3a5:f49 9 typ host tcptype
>>> active generation 0 ufrag Fie8 network-id 3 network-cost
>>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>>> DEBUG 09-17 19:21:56.730 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7]
>>> - Incoming message from user with ID '1':
>>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:1021992780
>>> 1 tcp 1518151935 2601:680:ca00:6cb0::635 9 typ host tcptype active
>>> generation 0 ufrag Fie8 network-id 4 network-cost
>>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>>> DEBUG 09-17 19:21:56.735 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7]
>>> - Incoming message from user with ID '1':
>>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:428269470
>>> 1 tcp 1518086399 2601:680:ca00:6cb0:d4ec:98a1:247d:6c5a 9 typ host tcptype
>>> active generation 0 ufrag Fie8 network-id 5 network-cost
>>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>>> DEBUG 09-17 19:21:56.740 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7]
>>> - Incoming message from user with ID '1':
>>> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3105188002
>>> 1 tcp 1518018303 10.0.0.202 9 typ host tcptype active generation 0 ufrag
>>> Fie8 network-id 2 network-cost
>>> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
>>> DEBUG 09-17 19:21:56.825 o.a.o.c.r.KurentoHandler:502 [pool-3-thread-6]
>>> - Kurento::ObjectCreated -> New Endpoint
>>> 8479330b-47c2-4070-9718-e7071f235534_kure

Re: OM and Media server separated-recording issue

2021-09-17 Thread Alvaro 
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, 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_DIR=/qcom_data/"
> 
> Here is what the files look like after stopping the recording:
> 
> [image: image.png]
> 
> This is what appears when clicking the caution icon:
> 
> [image: image.png]
> 
> Here are the streaming files in the right directory:
> 
> [image: image.png]
> 
> Here is the full stack trace from beginning of recording to the end in the
> logs:
> 
> DEBUG 09-17 19:21:56.691 o.a.o.c.r.KRoom:120 [ventExec-e2-t23] - ##REC::
> recording in room 241 is starting ::
> DEBUG 09-17 19:21:56.692 o.a.o.c.r.KRoom:147 [ventExec-e2-t23] - ##REC::
> recording created by USER: 1
> DEBUG 09-17 19:21:56.718 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3031263214
> 1 tcp 1518280447 10.43.204.201 9 typ host tcptype active generation 0 ufrag
> Fie8 network-id
> 1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.725 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:2078137933
> 1 tcp 1518217471 2601:680:ca00:6cb0:7584:5137:c3a5:f49 9 typ host tcptype
> active generation 0 ufrag Fie8 network-id 3 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.730 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:1021992780
> 1 tcp 1518151935 2601:680:ca00:6cb0::635 9 typ host tcptype active
> generation 0 ufrag Fie8 network-id 4 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.735 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:428269470
> 1 tcp 1518086399 2601:680:ca00:6cb0:d4ec:98a1:247d:6c5a 9 typ host tcptype
> active generation 0 ufrag Fie8 network-id 5 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.740 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-7] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:3105188002
> 1 tcp 1518018303 10.0.0.202 9 typ host tcptype active generation 0 ufrag
> Fie8 network-id 2 network-cost
> 10","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:56.825 o.a.o.c.r.KurentoHandler:502 [pool-3-thread-6] -
> Kurento::ObjectCreated -> New Endpoint
> 8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint
> detected, tags: {uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd,
> outUid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd}, kStream: KStream
> [kRoom=org.apache.openmeetings.core.remote.KRoom@42c72392,
> streamType=SCREEN, profile=WEBM_VIDEO_ONLY, recorder=null,
> outgoingMedia=[RemoteObject: type=WebRtcEndpoint
> remoteRef=8479330b-47c2-4070-9718-e7071f235534_kurento.MediaPipeline/4e72fc3a-ff84-44d1-95dd-dd51bd2e8811_kurento.WebRtcEndpoint],
> listeners={}, flowoutFuture=Optional.empty, chunkId=null, type=SCREEN,
> sid=7c541378-cf4c-429a-9a89-e9be993c8897,
> uid=8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd]
> DEBUG 09-17 19:21:56.889 o.a.o.c.r.StreamProcessor:90 [nio-5443-exec-3] -
> Incoming message from user with ID '1':
> {"type":"kurento","id":"onIceCandidate","candidate":{"candidate":"candidate:133411719
> 1 udp 41885439 172.17.129.147 57439 typ relay raddr 10.43.204.201 rport
> 54669 generation 0 ufrag Fie8 network-id
> 1","sdpMid":"0","sdpMLineIndex":0},"uid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd","luid":"8cf8103e-dc75-4f66-bcd8-5e21fb20fbbd"}
> DEBUG 09-17 19:21:57.687 o.a.o.c.r.KStream:345 [ventExec-e2-t23] -
> startRecord outMedia OK ? true
>  INFO 09-17 19:21:57.688 o.a.o.u.OmFileHelper:236 [ventExec-e2-t23] -
> Configured to record to
> file:///qcom_data/streams/241/rec_568_06e13054-28