I definitely did that during installation on KMS on docker. I used my own
data_dir, the change is not needed.
Still I'm having the recording creation error mentioned before.
Could it be a bug in this version of OM?
بتاريخ الجمعة، 14 تموز 2023 في 06:03:47 ص غرينتش+3، Maxim Solodovnik
<solomax...@gmail.com> كتب:
On Fri, 14 Jul 2023 at 02:54, Online Use <foronlineuseem...@yahoo.com> wrote:
>
> The hibernate folder path is:
>
> /home/website_home/data_dir/streams/hibernate/
In such case docket should have parameter: `-v
/home/website_home/data_dir:/home/website_home/data_dir`
So both will write the same folder
>
> My comment regarding the installation guide before wasn't related to syntax,
> but was related to your recommendation to move the data_dir under docker,
> because this was not mentioned in the installation guide althought they used
> docker to install KMS.
>
@Alvaro maybe you can add data_dir mapping for the dockerized KMS to
user guide? :)
>
> بتاريخ الثلاثاء، 11 تموز 2023 في 05:44:34 ص غرينتش+3، Maxim Solodovnik
> <solomax...@gmail.com> كتب:
>
>
> On Tue, 11 Jul 2023 at 02:23, Online Use <foronlineuseem...@yahoo.com> wrote:
> >
> > Hello,
> >
> > You said that *.webm file is being written by KMS and being used as source
> > while creating recording file, but I see the recording .wav files under the
> > "streams/9/" folder are already created,
>
> If I remember correctly *.wav files are generated using silence.wav in
> case of any problem ....
>
> Could you share full path for the hibernate folder please?
>
> > meaning that the .webm files have been there is the "hibernate" folder and
> > have been consumed to create the final recording files and then deleted
> > afterwards. So the problem is neither with the data directory location nor
> > with permissions, the problem is with the recorded files themselves,
> > recording error, the .wav files are there with data, but only blan screen.
> > May be mal-formated?
> >
> > What do you think?
> >
> >
> >
> > بتاريخ الاثنين، 10 تموز 2023 في 05:25:34 م غرينتش+3، Maxim Solodovnik
> > <solomax...@gmail.com> كتب:
> >
> >
> > On Mon, 10 Jul 2023 at 19:33, Online Use <foronlineuseem...@yahoo.com>
> > wrote:
> > >
> > > In the installation guide, Kurento is installed inside docker using this
> > > command:
> > >
> > > sudo docker run -d --name kms -p 8888:8888 --mount
> > > type=bind,source=/opt/om_data,target=/opt/om_data
> > > kurento/kurento-media-server
> > >
> >
> > I have to mention:
> >
> > 1)
> > `--mount type=bind,source=/opt/om_data,target=/opt/om_data`
> > and
> > `-v /opt/om_data:/opt/om_data`
> > are the same option :) (I'm just using shorter syntax :)))
> >
> > 2) I read the installation guide long time ago, but never follow (The
> > guide is super clear and saves lots of time to many many users :))
> > I'm developing OM for ~10 years so I don't need guide ;)
> >
> > (my command contains local DATA_DIR I'm using during development)
> >
> > 3) In your original email you cut the real paths:
> > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav
> > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm
> > .....
> > So I can't guess what are your full paths :(
> >
> >
> >
> > > I just did the same during installation.
> > >
> > > It seems that you are trying to change the source and target directory
> > > values after installation using the command that you mentioned in your
> > > reply below, but I don't understand to where are the paths in your
> > > command referring? are these supposed to be the old om_data directory
> > > paths?
> > >
> >
> > By default OM uses DATA_DIR inside the folder it was extracted to
> > it is good idea to use **external** DATA_DIR in production, this way
> > you will NOT need to copy/paste lots of binary data during upgrades :)
> >
> > >
> > >
> > > بتاريخ الاثنين، 10 تموز 2023 في 02:09:41 م غرينتش+3، Maxim Solodovnik
> > > <solomax...@gmail.com> كتب:
> > >
> > >
> > > On Mon, 10 Jul 2023 at 18:06, Online Use <foronlineuseem...@yahoo.com>
> > > wrote:
> > > >
> > > > I set the permission of the data directory recursively as 777 so that
> > > > it's writable by all users. I tested but got same errors.
> > >
> > > Another point: DATA_DIR should be mapped inside docker
> > >
> > > Here is the example:
> > > ```
> > > docker run -it -v
> > > /home/solomax/work/openmeetings/kms/etc-kurento:/etc/kurento -v
> > > /home/solomax/work/openmeetings/data:/home/solomax/work/openmeetings/data
> > > --network host kurento/kurento-media-server:7.0.0 bash
> > > ```
> > >
> > > this way KMS will write to the correct folder :)
> > >
> > >
> > > >
> > > > Different users affect anything other than directory access permissions?
> > > >
> > > > How can I check and change the users? I installed everything using root
> > > > already.
> > > >
> > >
> > > running as root not very wise from security perspective of view ....
> > >
> > > >
> > > > بتاريخ الاثنين، 10 تموز 2023 في 01:58:11 م غرينتش+3، Maxim Solodovnik
> > > > <solomax...@gmail.com> كتب:
> > > >
> > > >
> > > > On Mon, 10 Jul 2023 at 17:17, Online Use <foronlineuseem...@yahoo.com>
> > > > wrote:
> > > > >
> > > > > Thank you so much Maxim, it worked perfectly, I just needed to change
> > > > > the port number in Kurento conf file.
> > > > >
> > > > > Now I tested recording and it shows some error. The data directory
> > > > > path is correct, folders exist and their permission is 750. I found a
> > > > > recording file but blank screen, with size exceeding 3MB.
> > > > >
> > > > > I checeked the error trace, and I see the following notices:
> > > > >
> > > > > process: generate MP4
> > > > > - hibernate folder is empty
> > > > > - The recording file name is:
> > > > > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav,
> > > > > but the error trace refers to file which doesn't exist:
> > > > > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm: No such
> > > > > file or directory
> > > > >
> > > >
> > > > I believe the issue is in
> > > > "rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm: No such file or
> > > > directory"
> > > > This is most probably is caused by the fact KMS and OM are started
> > > > using different users
> > > >
> > > > `*.webm` file is being written by KMS and being used as source while
> > > > creating recording file
> > > > Both KMS and OM should be started by the same user (might be tricky
> > > > with dockerized KMS)
> > > >
> > > > >
> > > > > process: generate preview PNG
> > > > > - streams/hibernate/79c499c1-ca69-4871-a82e-5f4229668698.mp4: No such
> > > > > file or directory
> > > > >
> > > > > I think the problem is something related to the hibernate folder, but
> > > > > it exists and with permission 750.
> > > > >
> > > > > What do you think?
> > > > >
> > > > >
> > > > >
> > > > > بتاريخ الاثنين، 10 تموز 2023 في 11:37:50 ص غرينتش+3، Maxim Solodovnik
> > > > > <solomax...@gmail.com> كتب:
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > On Sun, 9 Jul 2023 at 15:55, Online Use via user
> > > > > <user@openmeetings.apache.org> wrote:
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I installed this version, and it opens correctly, the KMS is
> > > > > > installed and started correctly under docker, but when I try to
> > > > > > turn on the mic or webcam it shows an error message "Multimedia
> > > > > > server is inaccessible".
> > > > > >
> > > > > > What could be possible reasons for this error message?
> > > > >
> > > > > OM trying to connect to KMS using 127.0.0.1:8888
> > > > > Can you confirm both started at the same physical machine and KMS is
> > > > > listening at 127.0.0.1:8888 ?
> > > > >
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > > بتاريخ الخميس، 11 أيار 2023 في 04:43:49 ص غرينتش+3، Maxim
> > > > > > Solodovnik <solo...@apache.org> كتب:
> > > > > >
> > > > > >
> > > > > > The Apache OpenMeetings project is pleased to announce
> > > > > > the release of Apache OpenMeetings 7.1.0.
> > > > > > The release is available for download from
> > > > > > https://openmeetings.apache.org/downloads.html
> > > > > >
> > > > > > OpenMeetings provides video conferencing, instant messaging,
> > > > > > white board, collaborative document editing and other groupware
> > > > > > tools.
> > > > > > It uses API functions of Kurento Media Server for Remoting and
> > > > > > Streaming.
> > > > > >
> > > > > > Release 7.1.0, provides following improvements:
> > > > > >
> > > > > > IMPORTANT: Java 17 and KMS 6.18.0+ are required
> > > > > >
> > > > > > Security:
> > > > > > * Invitation hash check made strict
> > > > > > * Set of user permissions is fixed
> > > > > > * Paths entered in Admin->Config are being verified
> > > > > > * All dependencies are updated with most recent versions
> > > > > >
> > > > > > Stability:
> > > > > > * TURN server config is passed to the client
> > > > > >
> > > > > > ***3 security vulnerabilities were addressed***
> > > > > >
> > > > > > Some other fixes and improvements, 12 issues were addressed
> > > > > >
> > > > > > Readme: https://github.com/apache/openmeetings/blob/7.1.0/README.md
> > > > > >
> > > > > > Changelog:
> > > > > > https://github.com/apache/openmeetings/blob/7.1.0/CHANGELOG.md
> > > > > >
> > > > > > List of fixed issues:
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312720&version=12352896
> > > > > >
> > > > > > For more information on Apache OpenMeetings please visit project
> > > > > > home
> > > > > > page: https://openmeetings.apache.org
> > > > > >
> > > > > > Apache OpenMeetings Team
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
>
> >
> > >
> > > >
> > > > >
> > > > > Maxim
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim
--
Best regards,
Maxim
