Actually current master is still M1 .... And it was working last time I test it :) Checking it right now
On Fri, Sep 20, 2019, 20:53 YUP <[email protected]> wrote: > Sure, it should start, but it doesn't. Something is wrong with environment > in ubuntu in docker, that is why commands /etc/init.d/kurento-media-server > start or service kurento-media-server start fails. > > > On Fri, Sep 20, 2019, 15:47 Maxim Solodovnik <[email protected]> wrote: > >> Actually https://github.com/openmeetings/openmeetings-docker >> Is a little bit outdated (will update it to M2 ASAP) >> KMS currently being started every time docker is started >> please check >> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh >> >> On Fri, 20 Sep 2019 at 19:59, YUP <[email protected]> wrote: >> >>> I'm not using KMS in a standalone docker. I'm using docker with >>> OM+mysql+kurento: >>> >>> docker build -t om-server-full --build-arg BUILD_TYPE=full . >>> >>> пт, 20 вер. 2019 о 14:56 Maxim Solodovnik <[email protected]> пише: >>> > >>> > Why do you using KMS in docker in Ubuntu? >>> > >>> > On Fri, 20 Sep 2019 at 19:54, YUP <[email protected]> wrote: >>> >> >>> >> Well, I reinstalled Openmeetings full version >>> >> (ubuntu+OM+mysql+kurento) in a docker, and I have to say that >>> >> installation of Kurento Media Server >>> >> is broken. Kurrento have never started. Something is wrong with >>> >> kurento init script, or most likely with ubuntu installation. >>> >> You can easily check it. Steps to reproduce: >>> >> 1. Install OM full using instructions >>> >> 2. Start container >>> >> 3. Enter container: docker exec -it <CONTAINER ID> bash >>> >> 4. Check whether kurento runs: >>> >> ps xuaw | grep kurento >>> >> or try to start service: >>> >> service kurento-media-server start >>> >> This gives error: >>> >> * Start Kurento Media Server >>> >> * Configure Kernel resource limits for Kurento Media Server >>> >> /etc/init.d/kurento-media-server: 118: >>> >> /etc/init.d/kurento-media-server: Pipe call failed >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> 3. >>> >> >>> >> пт, 20 вер. 2019 о 12:07 YUP <[email protected]> пише: >>> >> > >>> >> > You gave me a hint. Ill check it. >>> >> > >>> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik <[email protected]> >>> пише: >>> >> > > >>> >> > > WebM files are being written by KMS >>> >> > > Maybe you get some info from KMS logs on your system? >>> >> > > >>> >> > > (I'm using Ubuntu on daily basis, never saw such behavior) >>> >> > > >>> >> > > On Fri, 20 Sep 2019 at 14:13, YUP <[email protected]> wrote: >>> >> > >> >>> >> > >> nobody:nogroup >>> >> > >> >>> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik <[email protected]> >>> пише: >>> >> > >> > >>> >> > >> > Can you check files have correct owner? >>> >> > >> > >>> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP <[email protected]> wrote: >>> >> > >> >> >>> >> > >> >> That's right, they are placed in correct places, but have 0 >>> bytes. >>> >> > >> >> >>> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik < >>> [email protected]> пише: >>> >> > >> >> > >>> >> > >> >> > Hello Yarema, >>> >> > >> >> > >>> >> > >> >> > so `webm` files are being created in correct place? but >>> they are empty? >>> >> > >> >> > >>> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP <[email protected]> >>> wrote: >>> >> > >> >> >> >>> >> > >> >> >> Hi, >>> >> > >> >> >> I installed full OM by means of docker on archlinux host >>> machine, >>> >> > >> >> >> using provided instruction. I even managed to work >>> >> > >> >> >> kurento-media-server, which doesn't work out of a box in >>> OM container. >>> >> > >> >> >> When I try to test recordings in camera setting window or >>> session >>> >> > >> >> >> recording, I get only empty webm files. >>> >> > >> >> >> Then I installed OM normally, i.e. without docker, but the >>> result was >>> >> > >> >> >> the same as in docker version. >>> >> > >> >> >> I forgot to mention that I am using OM behind nginx as a >>> reverse >>> >> > >> >> >> proxy. Everything works correctly except recordings. >>> >> > >> >> >> Does anyone noticed the same behaviour? Have I missed >>> something? Or it is a bug? >>> >> > >> >> >> Regards, >>> >> > >> >> >> Yarema >>> >> > >> >> > >>> >> > >> >> > >>> >> > >> >> > >>> >> > >> >> > -- >>> >> > >> >> > WBR >>> >> > >> >> > Maxim aka solomax >>> >> > >> > >>> >> > >> > >>> >> > >> > >>> >> > >> > -- >>> >> > >> > WBR >>> >> > >> > Maxim aka solomax >>> >> > > >>> >> > > >>> >> > > >>> >> > > -- >>> >> > > WBR >>> >> > > Maxim aka solomax >>> > >>> > >>> > >>> > -- >>> > WBR >>> > Maxim aka solomax >>> >> >> >> -- >> WBR >> Maxim aka solomax >> >
