Re: [ANNOUNCE] Apache OpenMeetings 7.1.0 is released
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 IMAGECOMMAND > CREATEDSTATUSPORTSNAMES > 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/000:00:00 > /usr/bin/kurento-media-server bash > root 61 52 0 04:39 pts/100: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 rootroot80134 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، Maxim Solodovnik > > كتب: > > > > > > > > > > from mobile (sorry for typos ;) > > > > > > On Fri, Jul 14, 2023, 14:29 Online Use wrote: > > > > 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. > > > > > > Maybe you can check with dockerized OM? > > Does it works for you? > > > > Usually recordings works as expected if there are no permission issues :( > > > > Additionally you can try to enter running KMS docker > > And try to write to data dir using same user who started KMS > > And check the result in real folder > > > > > > Could it be a bug in this version of OM? > > > > > > بتاريخ الجمعة، 14 تموز 2023 في 06:03:47 ص غرينتش+3، Maxim Solodovnik > > كتب: > > > > > > On Fri, 14 Jul 2023 at 02:54, Online Use > > 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 > > > كتب: > > > > > > > > > On Tue, 11 Jul 2023 at 02:23, Online Use > > > 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
[DISCUSSION] new release
Hello All, recently I've fixed following blocker: https://issues.apache.org/jira/browse/OPENMEETINGS-2775 Due to source artifact is very important to be buildable I believe this one worth release WDYT? -- Best regards, Maxim
Re: Error while building Openmeetings 7.1.0
Hello S Rajagopal, sorry for late response (was busy at my day time job) Please do not write direct emails: write to the user@ mailing list instead: https://openmeetings.apache.org/mailing-lists.html I've just tried to build 1) Git tag 7.1.0 (https://github.com/apache/openmeetings/tree/7.1.0/) - the build is GREEN 2) Our src artifact (apache-openmeetings-7.1.0-src.tar.gz) - the build was FAILED I have created https://issues.apache.org/jira/browse/OPENMEETINGS-2775 I'll try to release 7.2.0 with source artifact fixed ASAP Please use git tag for now :) Thanks for the report! On Tue, 25 Jul 2023 at 00:18, Rajagopal Subramanian wrote: > > Dear Sir, > I am a developer and trying to build the recent > release of Openmeetings 7.1.0. While doing so with Eclipse I got the > following error. > Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:4.0.0-M5:site (generate-site) on > project openmeetings-util: Execution generate-site of goal > org.apache.maven.plugins:maven-site-plugin:4.0.0-M5:site failed: > decoration.skin cannot be null. > I need your help to fix it. Kindly help to resolve this issue. > Thanks and Regards, > S Rajagopal. > -- Best regards, Maxim
Re: [ANNOUNCE] Apache OpenMeetings 7.1.0 is released
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، Maxim Solodovnik > كتب: > > > > > from mobile (sorry for typos ;) > > > On Fri, Jul 14, 2023, 14:29 Online Use wrote: > > 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. > > > Maybe you can check with dockerized OM? > Does it works for you? > > Usually recordings works as expected if there are no permission issues :( > > Additionally you can try to enter running KMS docker > And try to write to data dir using same user who started KMS > And check the result in real folder > > > Could it be a bug in this version of OM? > > > بتاريخ الجمعة، 14 تموز 2023 في 06:03:47 ص غرينتش+3، Maxim Solodovnik > كتب: > > > On Fri, 14 Jul 2023 at 02:54, Online Use 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 > > كتب: > > > > > > On Tue, 11 Jul 2023 at 02:23, Online Use > > 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 > > > كتب: > > > > > > > > > On Mon, 10 Jul 2023 at 19:33, Online Use > > > wrote: > > > > > > > > In the installation guide, Kurento is installed inside docker using > > > > this command: > > > > > > > > sudo docker run -d --name kms -p : --mount > > > > type=bind,source=/opt/om_data,target=/opt/om_data > > > > kurento/kurento-media-server > > > > > > > > > > I have to mention: > > > > > > 1) > > > `--mount
