Re: [ANNOUNCE] Apache OpenMeetings 7.1.0 is released

2023-08-03 Thread Maxim Solodovnik
Hello,

thanks for pinging! (too much day-time job :((( )

let's get back to the topic :)

On Fri, 4 Aug 2023 at 04:55, Online Use  wrote:
>
> Hello,
>
> I hope you have enough time to follow up with me regarding this issue. Can 
> you tell me what you think?
>
> Thanks.
>
> بتاريخ الجمعة، 28 تموز 2023 في 06:52:17 ص غرينتش+3، Online Use 
>  كتب:
>
>
> Yes the test files and folder 5 have been created successfully, and I already 
> had folders for other room number with files. As I mentioned before I have 
> empty video files inside room folder 
> "rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav"

I believe here might be misunderstanding

Actually your configuration consist of two isolated Linuxes running at
the same phisycal machine
- first one is OM: it server web interface sending commands to KMS and
do process the recordings
- second one is KMS which handling multimedia part

So the process of record in the room organized as follows:
- user press the button in UI
- OM send the command to KMS to start recording
- KMS start writing to
home/website_home/data_dir/streams/_ROOM_ID_/_LONG_UUID_.webm file and
sends ACK to OM
- OM displays "Recording has been started" to the user
- user stops recording in the UI (via button, room exit etc.)
- OM sends stop command to KMS
- KMS stops the recording, close the file and send ACK to the OM
- OM starts converting *.webm file
   -- For all rooms except INTERVIEW --
  * extracts audio from all webcam video OR create *.wav with silence
  * join the audio with **SCREEN SHARING** video
   -- For INTERVIEW rooms --
  * join video from cameras of all participants into big "video carpet"

So in case there is no *.webm file
- KMS might fail to write it (KMS logs need to be examined)
- **data_dir/streams** folder is mounted incorrectly and KMS writes
something inside it's Linux while OM can't see it
- permission issue
-
- something else

we need to check all vectors 


>
> The problem was in creating the temporary processing files in the hibernate 
> folder, I think.
>
>
> بتاريخ الجمعة، 28 تموز 2023 في 05:53:24 ص غرينتش+3، Maxim Solodovnik 
>  كتب:
>
>
> On Fri, 28 Jul 2023 at 03:17, Online Use  wrote:
> >
> > I got the following output in both cases, from outside and inside docker:
> >
> > total 16
> > drwxrwxrwx. 4 rootroot  4096 Apr 19 00:55.
> > drwx--x--x.8 cloud7843cloud7843 4096 Jul 27 00:00  ..
> > drwxrwxrwx. 6 rootroot  4096 Apr 21 22:03
> > streams
> > drwxrwxrwx. 5 rootroot  4096 Apr 19 01:05
> > upload
> >
> > I frankly don't know what is this cloud7843 user?
>
> This is the owner of "/home/website_home" folder
>
> KMS writes to "/home/website_home/data_dir/streams" and
> "/home/website_home/data_dir/streams/ROOM_ID"
>
> could you run following commands inside KMS docker:
>
> cat "test1" > /home/website_home/data_dir/streams/test1
> mkdir /home/website_home/data_dir/streams/5
> cat "test2" > /home/website_home/data_dir/streams/5/test2
>
> room_id -> 5 === "Public Presentation Room"
>
> And check if files were successfully created and visible and readable
> on host machine?
>
> >
> > Do you think this line is the problem?
> >
> >
> >
> > بتاريخ الخميس، 27 تموز 2023 في 07:26:46 ص غرينتش+3، Maxim Solodovnik 
> >  كتب:
> >
> >
> > Hello All,
> >
> > sorry for being silent
> > answering this email was in my TODO list :)
> >
> > Recently I was able to set up our demo server [1]
> > The recordings works as expected (can be tested with [2])
> > It is Ubuntu 22.04 + Dockerized KMS
> >
> > So I believe there is nothing wrong with such configuration or Dockerized 
> > KMS
> >
> > I would say something wrong with your
> > - folder mapping
> > and/or
> > - permissions
> >
> > BUT
> > since everything in your config is under `root` I don't think it can
> > be permission issue
> >
> > can you please check the following command
> >
> > `ls -la /home/website_home/data_dir`
> > ( and try some subfolders too)
> >
> > produces the same output
> > - from inside docker
> > - AND at your host machine (where OM process is working)
> > ?
> >
> > [1] https://demo-openmeetings.apache.org/openmeetings
> > [2] https://demo-openmeetings.apache.org/openmeetings/hash?app=settings
> >
> > On Thu, 27 Jul 2023 at 04:26, Online Use  
> > wrote:
> > >
> > > Hello,
> > >
> > > I haven't get response to this message. Would you please advise? the 
> > > issue is still persistent.
> > >
> > > Did you find out any cause within this version of OM?
> > >
> > >
> > >
> > > بتاريخ السبت، 15 تموز 2023 في 10:21:56 ص غرينتش+3، Online Use 
> > >  كتب:
> > >
> > >
> > > Thanks. I also now verified that KMS is started using root with uid 1.
> > >
> > > How can I check that OM is running using same user?
> > >
> > >
> > > بتاريخ السبت، 15 تموز 2023 في 07:48:37 ص غرينتش+3، Maxim Solodovnik 
> > >  كتب:
> > >
> > >
> > > On Fri, 14 Jul 2023 at 21:10, Online Use via user
> > >  wrote:
> > > >

Re: [ANNOUNCE] Apache OpenMeetings 7.1.0 is released

2023-08-03 Thread Online Use via user
 Hello,
I hope you have enough time to follow up with me regarding this issue. Can you 
tell me what you think?
Thanks.
بتاريخ الجمعة، 28 تموز 2023 في 06:52:17 ص غرينتش+3، Online Use 
 كتب:  
 
  Yes the test files and folder 5 have been created successfully, and I already 
had folders for other room number with files. As I mentioned before I have 
empty video files inside room folder 
"rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav"
The problem was in creating the temporary processing files in the hibernate 
folder, I think.

بتاريخ الجمعة، 28 تموز 2023 في 05:53:24 ص غرينتش+3، Maxim Solodovnik 
 كتب:  
 
 On Fri, 28 Jul 2023 at 03:17, Online Use  wrote:
>
> I got the following output in both cases, from outside and inside docker:
>
> total 16
> drwxrwxrwx. 4 root                root          4096 Apr 19 00:55        .
> drwx--x--x.    8 cloud7843    cloud7843 4096 Jul 27 00:00          ..
> drwxrwxrwx. 6 root                root          4096 Apr 21 22:03        
> streams
> drwxrwxrwx. 5 root                root          4096 Apr 19 01:05        
> upload
>
> I frankly don't know what is this cloud7843 user?

This is the owner of "/home/website_home" folder

KMS writes to "/home/website_home/data_dir/streams" and
"/home/website_home/data_dir/streams/ROOM_ID"

could you run following commands inside KMS docker:

cat "test1" > /home/website_home/data_dir/streams/test1
mkdir /home/website_home/data_dir/streams/5
cat "test2" > /home/website_home/data_dir/streams/5/test2

room_id -> 5 === "Public Presentation Room"

And check if files were successfully created and visible and readable
on host machine?

>
> Do you think this line is the problem?
>
>
>
> بتاريخ الخميس، 27 تموز 2023 في 07:26:46 ص غرينتش+3، Maxim Solodovnik 
>  كتب:
>
>
> Hello All,
>
> sorry for being silent
> answering this email was in my TODO list :)
>
> Recently I was able to set up our demo server [1]
> The recordings works as expected (can be tested with [2])
> It is Ubuntu 22.04 + Dockerized KMS
>
> So I believe there is nothing wrong with such configuration or Dockerized KMS
>
> I would say something wrong with your
> - folder mapping
> and/or
> - permissions
>
> BUT
> since everything in your config is under `root` I don't think it can
> be permission issue
>
> can you please check the following command
>
> `ls -la /home/website_home/data_dir`
> ( and try some subfolders too)
>
> produces the same output
> - from inside docker
> - AND at your host machine (where OM process is working)
> ?
>
> [1] https://demo-openmeetings.apache.org/openmeetings
> [2] https://demo-openmeetings.apache.org/openmeetings/hash?app=settings
>
> On Thu, 27 Jul 2023 at 04:26, Online Use  wrote:
> >
> > Hello,
> >
> > I haven't get response to this message. Would you please advise? the issue 
> > is still persistent.
> >
> > Did you find out any cause within this version of OM?
> >
> >
> >
> > بتاريخ السبت، 15 تموز 2023 في 10:21:56 ص غرينتش+3، Online Use 
> >  كتب:
> >
> >
> > Thanks. I also now verified that KMS is started using root with uid 1.
> >
> > How can I check that OM is running using same user?
> >
> >
> > بتاريخ السبت، 15 تموز 2023 في 07:48:37 ص غرينتش+3، Maxim Solodovnik 
> >  كتب:
> >
> >
> > On Fri, 14 Jul 2023 at 21:10, Online Use via user
> >  wrote:
> > >
> > > Can you tell me how to verify the user name who is running KMS? I 
> > > installed it from shell using root, just like all OM installation steps.
> >
> > your KMS is running in docker
> >
> > so you have to do the following:
> >
> > run
> > `docker ps`
> >
> > in terminal
> > You will get output like
> > ```
> > docker ps
> > CONTAINER ID  IMAGE                                COMMAND
> >    CREATED        STATUS                            PORTS    NAMES
> > 8d89d696012f  kurento/kurento-media-server:7.0.0  "/entrypoint.sh
> > bash"  6 seconds ago  Up 5 seconds (health: starting)
> > sad_gagarin
> > ```
> > now you have to copy "CONTAINER ID"
> >
> > and run following command
> > `docker exec -it 8d89d696012f bash`
> >
> > in terminal (please use your own "CONTAINER ID")
> > please NOTE "CONTAINER ID" is unique and generated on every new run
> >
> > now you are inside the docker
> >
> > you can use `ps -ef|grep kurento`
> > for my machine the output is:
> > ```
> > root          1      0  0 04:38 pts/0    00:00:00
> > /usr/bin/kurento-media-server bash
> > root          61      52  0 04:39 pts/1    00:00:00 grep --color=auto 
> > kurento
> > ```
> >
> > so the KMS is started as user with login `root` and uid `1`
> >
> > *.webm files on my machine are being created as
> >
> > ```
> > -rw-r--r-- 1 root    root    80134 Jul 15 11:45
> > TEST_SETUP_4a7fa3f6-e284-4d42-be2c-94309b753a2d.webm
> > ```
> >
> > BTW good option to test recordings would be test recording at following 
> > address:
> > https://localhost:5443/openmeetings/hash?app=settings
> >
> > (please use your own server-name/IP+port :)))
> >
> > >
> > >
> > > بتاريخ الجمعة، 14 تموز 2023 في 01:55:43 م غرينتش+3،