subject:"Re\: Empty Recording files in OM 5.0.0\-M2"

Re: Empty Recording files in OM 5.0.0-M2

2020-03-24 Thread YUP

Yes, the openmeeting server is behind restrictive firewall with the only
one 443 port opened fo incoming connections ofrom outside and only 80,
8080, 22 and 443 opened for http requests from inside. Consequently, when I
am not in the same network of the openmeeting server the mentioned issue is
happening. I understood it when tried to configure kurento and turn server.
I seems to me that turn server need more open ports for media streams, I
can't put them all into one 443 "hole" even by means of advanced traffic
balancer. I don't know how...
Regards,
Yarema

On Tue, Mar 24, 2020, 06:26 Maxim Solodovnik  wrote:

> Is this still an issue?
>
> On Mon, 23 Sep 2019 at 12:20, YUP  wrote:
> >
> > My OM section in nginx config file looks as follows:
> >
> >   location /openmeetings {
> > proxy_pass https://localhost:5443/openmeetings;
> > proxy_http_version 1.1;
> > proxy_set_header Upgrade $http_upgrade;
> > proxy_set_header Connection "upgrade";
> > proxy_set_header Host $host;
> > proxy_set_header X-Real-IP $remote_addr;
> > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> > proxy_set_header X-Forwarded-Proto $scheme;
> > proxy_set_header X-Forwarded-Protocol $scheme;
> > proxy_set_header X-Forwarded-Host $http_host;
> > }
> >
> > нд, 22 вер. 2019 о 17:10 YUP  пише:
> > >
> > > Hi again,
> > > There are a few things which I discovered:
> > > 1. When I install openmeetings locally and KMS in docker (using
> > > provided instruction for Archlinux) on my laptop with archlinux and
> > > without (!) nginx and proxy_pass it runs out of the box without any
> > > problems and records everything I want. But:
> > > 2. If i do the same but with nginx as a proxy, the behavior is the
> > > same as I described in my first email.
> > > 3. When I install full version of openmeetings with mysql and kurento
> > > by means of docker on host machine with archlinux, the kurento server
> > > is dead. The reason is very simple, the start script can't define max
> > > size of the open file. I don't know why it happen for Archlinux.  As a
> > > workaround it is enough to enter running container with openmeetings,
> > > comment line with DAEMON_MAX_FILE=... in kurento configuration file
> > > /etc/default/kurento-media-server, save and start kms: service
> > > kurento-media-server  start. Then kurento server starts without
> > > errors. But with nginx and proxy_pass recording doesn't work, and
> > > works without proxy_pass.
> > > 4. For some understandable reasons I have only port 443 opened to the
> > > world, so a method how to get OM work with this environment would be
> > > highly appreciated.
> > > Regards,
> > > Yarema
> > >
> > > нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
> > > >
> > > > This actually make no sense :(
> > > > I always thought docker should work the same for different machines
> > > >
> > > > This is my start command and first lines of the output:
> > > >
> > > > `docker run -i --rm --name om-server-full --expose=5443
> --expose= -p 5443:5443 -p :
> openmeetings-docker-images.bintray.io/server-full:latest`
> 
> > > >  * Stopping MySQL database server mysqld
> > > >...done.
> > > >  * Starting MySQL database server mysqld
> > > >...done.
> > > > OM server of type full will be run
> > > >  * Start Kurento Media Server
> > > >  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
> > > >  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
> > > >  * Configure Kernel resource limits for Kurento Media Server
> > > >...done.
> > > >
> > > > This is the line the KMS is being started:
> > > >
> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
> > > >
> > > > Have no idea what is going on :(
> > > >
> > > >
> > > > On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
> > > >>
> > > >> I checked your image, and got the same result, kurento is dead. I
> > > >> gonna give up
> > > >>
> > > >> $ docker info
> > > >> Client:
> > > >>  Debug Mode: false
> > > >>
> > > >> Server:
> > > >>  Containers: 4
> > > >>   Running: 4
> > > >>   Paused: 0
> > > >>   Stopped: 0
> > > >>  Images: 45
> > > >>  Server Version: 19.03.2-ce
> > > >>  Storage Driver: overlay2
> > > >>   Backing Filesystem: extfs
> > > >>   Supports d_type: true
> > > >>   Native Overlay Diff: false
> > > >>  Logging Driver: json-file
> > > >>  Cgroup Driver: cgroupfs
> > > >>  Plugins:
> > > >>   Volume: local
> > > >>   Network: bridge host ipvlan macvlan null overlay
> > > >>   Log: awslogs fluentd gcplogs gelf journald json-file local
> > > >> logentries splunk syslog
> > > >>  Swarm: inactive
> > > >>  Runtimes: runc
> > > >>  Default Runtime: runc
> > > >>  Init Binary: docker-init
> > > >>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
> > > >>  runc version:

Re: Empty Recording files in OM 5.0.0-M2

2020-03-23 Thread Maxim Solodovnik

Is this still an issue?

On Mon, 23 Sep 2019 at 12:20, YUP  wrote:
>
> My OM section in nginx config file looks as follows:
>
>   location /openmeetings {
> proxy_pass https://localhost:5443/openmeetings;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection "upgrade";
> proxy_set_header Host $host;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_set_header X-Forwarded-Proto $scheme;
> proxy_set_header X-Forwarded-Protocol $scheme;
> proxy_set_header X-Forwarded-Host $http_host;
> }
>
> нд, 22 вер. 2019 о 17:10 YUP  пише:
> >
> > Hi again,
> > There are a few things which I discovered:
> > 1. When I install openmeetings locally and KMS in docker (using
> > provided instruction for Archlinux) on my laptop with archlinux and
> > without (!) nginx and proxy_pass it runs out of the box without any
> > problems and records everything I want. But:
> > 2. If i do the same but with nginx as a proxy, the behavior is the
> > same as I described in my first email.
> > 3. When I install full version of openmeetings with mysql and kurento
> > by means of docker on host machine with archlinux, the kurento server
> > is dead. The reason is very simple, the start script can't define max
> > size of the open file. I don't know why it happen for Archlinux.  As a
> > workaround it is enough to enter running container with openmeetings,
> > comment line with DAEMON_MAX_FILE=... in kurento configuration file
> > /etc/default/kurento-media-server, save and start kms: service
> > kurento-media-server  start. Then kurento server starts without
> > errors. But with nginx and proxy_pass recording doesn't work, and
> > works without proxy_pass.
> > 4. For some understandable reasons I have only port 443 opened to the
> > world, so a method how to get OM work with this environment would be
> > highly appreciated.
> > Regards,
> > Yarema
> >
> > нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
> > >
> > > This actually make no sense :(
> > > I always thought docker should work the same for different machines
> > >
> > > This is my start command and first lines of the output:
> > >
> > > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> > > 5443:5443 -p : 
> > > openmeetings-docker-images.bintray.io/server-full:latest`
> > >  * Stopping MySQL database server mysqld
> > >...done.
> > >  * Starting MySQL database server mysqld
> > >...done.
> > > OM server of type full will be run
> > >  * Start Kurento Media Server
> > >  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
> > >  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
> > >  * Configure Kernel resource limits for Kurento Media Server
> > >...done.
> > >
> > > This is the line the KMS is being started:
> > > https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
> > >
> > > Have no idea what is going on :(
> > >
> > >
> > > On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
> > >>
> > >> I checked your image, and got the same result, kurento is dead. I
> > >> gonna give up
> > >>
> > >> $ docker info
> > >> Client:
> > >>  Debug Mode: false
> > >>
> > >> Server:
> > >>  Containers: 4
> > >>   Running: 4
> > >>   Paused: 0
> > >>   Stopped: 0
> > >>  Images: 45
> > >>  Server Version: 19.03.2-ce
> > >>  Storage Driver: overlay2
> > >>   Backing Filesystem: extfs
> > >>   Supports d_type: true
> > >>   Native Overlay Diff: false
> > >>  Logging Driver: json-file
> > >>  Cgroup Driver: cgroupfs
> > >>  Plugins:
> > >>   Volume: local
> > >>   Network: bridge host ipvlan macvlan null overlay
> > >>   Log: awslogs fluentd gcplogs gelf journald json-file local
> > >> logentries splunk syslog
> > >>  Swarm: inactive
> > >>  Runtimes: runc
> > >>  Default Runtime: runc
> > >>  Init Binary: docker-init
> > >>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
> > >>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
> > >>  init version: fec3683
> > >>  Security Options:
> > >>   seccomp
> > >>Profile: default
> > >>  Kernel Version: 4.19.73-1-lts
> > >>  Operating System: Arch Linux
> > >>  OSType: linux
> > >>  Architecture: x86_64
> > >>  CPUs: 2
> > >>  Total Memory: 3.789GiB
> > >>  Name: archmoodle
> > >>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
> > >>  Docker Root Dir: /home/docker
> > >>  Debug Mode: false
> > >>  Registry: https://index.docker.io/v1/
> > >>  Labels:
> > >>  Experimental: false
> > >>  Insecure Registries:
> > >>   127.0.0.0/8
> > >>  Live Restore Enabled: false
> > >>
> > >> сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
> > >> >
> > >> > `docker info`
> > >> >
> > >> > Server Version: 19.03.2
> > >> >
> > >> >
> > >> > The image is uploaded, everything works as expected
> > >> > Just have double-checked
> > >> > `docker run

Re: Empty Recording files in OM 5.0.0-M2

2019-09-22 Thread YUP

My OM section in nginx config file looks as follows:

  location /openmeetings {
proxy_pass https://localhost:5443/openmeetings;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;
}

нд, 22 вер. 2019 о 17:10 YUP  пише:
>
> Hi again,
> There are a few things which I discovered:
> 1. When I install openmeetings locally and KMS in docker (using
> provided instruction for Archlinux) on my laptop with archlinux and
> without (!) nginx and proxy_pass it runs out of the box without any
> problems and records everything I want. But:
> 2. If i do the same but with nginx as a proxy, the behavior is the
> same as I described in my first email.
> 3. When I install full version of openmeetings with mysql and kurento
> by means of docker on host machine with archlinux, the kurento server
> is dead. The reason is very simple, the start script can't define max
> size of the open file. I don't know why it happen for Archlinux.  As a
> workaround it is enough to enter running container with openmeetings,
> comment line with DAEMON_MAX_FILE=... in kurento configuration file
> /etc/default/kurento-media-server, save and start kms: service
> kurento-media-server  start. Then kurento server starts without
> errors. But with nginx and proxy_pass recording doesn't work, and
> works without proxy_pass.
> 4. For some understandable reasons I have only port 443 opened to the
> world, so a method how to get OM work with this environment would be
> highly appreciated.
> Regards,
> Yarema
>
> нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
> >
> > This actually make no sense :(
> > I always thought docker should work the same for different machines
> >
> > This is my start command and first lines of the output:
> >
> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> > 5443:5443 -p : 
> > openmeetings-docker-images.bintray.io/server-full:latest`
> >  * Stopping MySQL database server mysqld
> >...done.
> >  * Starting MySQL database server mysqld
> >...done.
> > OM server of type full will be run
> >  * Start Kurento Media Server
> >  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
> >  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
> >  * Configure Kernel resource limits for Kurento Media Server
> >...done.
> >
> > This is the line the KMS is being started:
> > https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
> >
> > Have no idea what is going on :(
> >
> >
> > On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
> >>
> >> I checked your image, and got the same result, kurento is dead. I
> >> gonna give up
> >>
> >> $ docker info
> >> Client:
> >>  Debug Mode: false
> >>
> >> Server:
> >>  Containers: 4
> >>   Running: 4
> >>   Paused: 0
> >>   Stopped: 0
> >>  Images: 45
> >>  Server Version: 19.03.2-ce
> >>  Storage Driver: overlay2
> >>   Backing Filesystem: extfs
> >>   Supports d_type: true
> >>   Native Overlay Diff: false
> >>  Logging Driver: json-file
> >>  Cgroup Driver: cgroupfs
> >>  Plugins:
> >>   Volume: local
> >>   Network: bridge host ipvlan macvlan null overlay
> >>   Log: awslogs fluentd gcplogs gelf journald json-file local
> >> logentries splunk syslog
> >>  Swarm: inactive
> >>  Runtimes: runc
> >>  Default Runtime: runc
> >>  Init Binary: docker-init
> >>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
> >>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
> >>  init version: fec3683
> >>  Security Options:
> >>   seccomp
> >>Profile: default
> >>  Kernel Version: 4.19.73-1-lts
> >>  Operating System: Arch Linux
> >>  OSType: linux
> >>  Architecture: x86_64
> >>  CPUs: 2
> >>  Total Memory: 3.789GiB
> >>  Name: archmoodle
> >>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
> >>  Docker Root Dir: /home/docker
> >>  Debug Mode: false
> >>  Registry: https://index.docker.io/v1/
> >>  Labels:
> >>  Experimental: false
> >>  Insecure Registries:
> >>   127.0.0.0/8
> >>  Live Restore Enabled: false
> >>
> >> сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
> >> >
> >> > `docker info`
> >> >
> >> > Server Version: 19.03.2
> >> >
> >> >
> >> > The image is uploaded, everything works as expected
> >> > Just have double-checked
> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> >> > 5443:5443 -p : 
> >> > openmeetings-docker-images.bintray.io/server-full:latest`
> >> >
> >> > On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
> >> >>
> >> >> BTW, what version of docker do you use?
> >> >> $ docker info
> >> >>
> >> >> сб, 21 вер. 2019 о

Re: Empty Recording files in OM 5.0.0-M2

2019-09-22 Thread YUP

Hi again,
There are a few things which I discovered:
1. When I install openmeetings locally and KMS in docker (using
provided instruction for Archlinux) on my laptop with archlinux and
without (!) nginx and proxy_pass it runs out of the box without any
problems and records everything I want. But:
2. If i do the same but with nginx as a proxy, the behavior is the
same as I described in my first email.
3. When I install full version of openmeetings with mysql and kurento
by means of docker on host machine with archlinux, the kurento server
is dead. The reason is very simple, the start script can't define max
size of the open file. I don't know why it happen for Archlinux.  As a
workaround it is enough to enter running container with openmeetings,
comment line with DAEMON_MAX_FILE=... in kurento configuration file
/etc/default/kurento-media-server, save and start kms: service
kurento-media-server  start. Then kurento server starts without
errors. But with nginx and proxy_pass recording doesn't work, and
works without proxy_pass.
4. For some understandable reasons I have only port 443 opened to the
world, so a method how to get OM work with this environment would be
highly appreciated.
Regards,
Yarema

нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
>
> This actually make no sense :(
> I always thought docker should work the same for different machines
>
> This is my start command and first lines of the output:
>
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : 
> openmeetings-docker-images.bintray.io/server-full:latest`
>  * Stopping MySQL database server mysqld
>...done.
>  * Starting MySQL database server mysqld
>...done.
> OM server of type full will be run
>  * Start Kurento Media Server
>  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
>  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
>  * Configure Kernel resource limits for Kurento Media Server
>...done.
>
> This is the line the KMS is being started:
> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
>
> Have no idea what is going on :(
>
>
> On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
>>
>> I checked your image, and got the same result, kurento is dead. I
>> gonna give up
>>
>> $ docker info
>> Client:
>>  Debug Mode: false
>>
>> Server:
>>  Containers: 4
>>   Running: 4
>>   Paused: 0
>>   Stopped: 0
>>  Images: 45
>>  Server Version: 19.03.2-ce
>>  Storage Driver: overlay2
>>   Backing Filesystem: extfs
>>   Supports d_type: true
>>   Native Overlay Diff: false
>>  Logging Driver: json-file
>>  Cgroup Driver: cgroupfs
>>  Plugins:
>>   Volume: local
>>   Network: bridge host ipvlan macvlan null overlay
>>   Log: awslogs fluentd gcplogs gelf journald json-file local
>> logentries splunk syslog
>>  Swarm: inactive
>>  Runtimes: runc
>>  Default Runtime: runc
>>  Init Binary: docker-init
>>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
>>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
>>  init version: fec3683
>>  Security Options:
>>   seccomp
>>Profile: default
>>  Kernel Version: 4.19.73-1-lts
>>  Operating System: Arch Linux
>>  OSType: linux
>>  Architecture: x86_64
>>  CPUs: 2
>>  Total Memory: 3.789GiB
>>  Name: archmoodle
>>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
>>  Docker Root Dir: /home/docker
>>  Debug Mode: false
>>  Registry: https://index.docker.io/v1/
>>  Labels:
>>  Experimental: false
>>  Insecure Registries:
>>   127.0.0.0/8
>>  Live Restore Enabled: false
>>
>> сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
>> >
>> > `docker info`
>> >
>> > Server Version: 19.03.2
>> >
>> >
>> > The image is uploaded, everything works as expected
>> > Just have double-checked
>> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
>> > 5443:5443 -p : 
>> > openmeetings-docker-images.bintray.io/server-full:latest`
>> >
>> > On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
>> >>
>> >> BTW, what version of docker do you use?
>> >> $ docker info
>> >>
>> >> сб, 21 вер. 2019 о 18:30 YUP  пише:
>> >> >
>> >> > Great, thanks!
>> >> >
>> >> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>> >> > >
>> >> > > Well
>> >> > > I can upload my image to the bintray
>> >> > > And you can try it
>> >> > > Will do it tomorrow
>> >> > >
>> >> > > On Sat, Sep 21, 2019, 23:14 YUP  wrote:
>> >> > >>
>> >> > >> So something is wrong with Archlinux as a host machine and OM in
>> >> > >> docker. But it is nonsense, created image should not depend from host
>> >> > >> machine and om+mysql+kurento must run the same way...
>> >> > >>
>> >> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  
>> >> > >> пише:
>> >> > >> >
>> >> > >> > Kurento and mysql are both started right before om
>> >> > >> > It is very clear from the logs
>> >> > >> > And both video and recording works in om :)
>> >> > >> >
>> >> > >> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>> >> > >>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

This actually make no sense :(
I always thought docker should work the same for different machines

This is my start command and first lines of the output:

`docker run -i --rm --name om-server-full --expose=5443 --expose= -p
5443:5443 -p :
openmeetings-docker-images.bintray.io/server-full:latest`
 * Stopping MySQL database server mysqld
   ...done.
 * Starting MySQL database server mysqld
   ...done.
OM server of type full will be run
 * Start Kurento Media Server
 * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
 * Changed owner of '/var/log/kurento-media-server' to 'nobody'
 * Configure Kernel resource limits for Kurento Media Server
   ...done.

This is the line the KMS is being started:
https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44

Have no idea what is going on :(


On Sun, 22 Sep 2019 at 01:29, YUP  wrote:

> I checked your image, and got the same result, kurento is dead. I
> gonna give up
>
> $ docker info
> Client:
>  Debug Mode: false
>
> Server:
>  Containers: 4
>   Running: 4
>   Paused: 0
>   Stopped: 0
>  Images: 45
>  Server Version: 19.03.2-ce
>  Storage Driver: overlay2
>   Backing Filesystem: extfs
>   Supports d_type: true
>   Native Overlay Diff: false
>  Logging Driver: json-file
>  Cgroup Driver: cgroupfs
>  Plugins:
>   Volume: local
>   Network: bridge host ipvlan macvlan null overlay
>   Log: awslogs fluentd gcplogs gelf journald json-file local
> logentries splunk syslog
>  Swarm: inactive
>  Runtimes: runc
>  Default Runtime: runc
>  Init Binary: docker-init
>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
>  init version: fec3683
>  Security Options:
>   seccomp
>Profile: default
>  Kernel Version: 4.19.73-1-lts
>  Operating System: Arch Linux
>  OSType: linux
>  Architecture: x86_64
>  CPUs: 2
>  Total Memory: 3.789GiB
>  Name: archmoodle
>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
>  Docker Root Dir: /home/docker
>  Debug Mode: false
>  Registry: https://index.docker.io/v1/
>  Labels:
>  Experimental: false
>  Insecure Registries:
>   127.0.0.0/8
>  Live Restore Enabled: false
>
> сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
> >
> > `docker info`
> >
> > Server Version: 19.03.2
> >
> >
> > The image is uploaded, everything works as expected
> > Just have double-checked
> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p
> 5443:5443 -p :
> openmeetings-docker-images.bintray.io/server-full:latest`
> 
> >
> > On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
> >>
> >> BTW, what version of docker do you use?
> >> $ docker info
> >>
> >> сб, 21 вер. 2019 о 18:30 YUP  пише:
> >> >
> >> > Great, thanks!
> >> >
> >> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik 
> пише:
> >> > >
> >> > > Well
> >> > > I can upload my image to the bintray
> >> > > And you can try it
> >> > > Will do it tomorrow
> >> > >
> >> > > On Sat, Sep 21, 2019, 23:14 YUP  wrote:
> >> > >>
> >> > >> So something is wrong with Archlinux as a host machine and OM in
> >> > >> docker. But it is nonsense, created image should not depend from
> host
> >> > >> machine and om+mysql+kurento must run the same way...
> >> > >>
> >> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik 
> пише:
> >> > >> >
> >> > >> > Kurento and mysql are both started right before om
> >> > >> > It is very clear from the logs
> >> > >> > And both video and recording works in om :)
> >> > >> >
> >> > >> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
> >> > >> >>
> >> > >> >> OK. Please enter your container with running OM:
> >> > >> >>
> >> > >> >> docker exec -it CONTAINER_ID bash
> >> > >> >> and then check whether kurento running:
> >> > >> >> ps xuaw | grep kurento
> >> > >> >> or
> >> > >> >> service kurento-media-server status
> >> > >> >> and post the result, please.
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik 
> пише:
> >> > >> >> >
> >> > >> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> >> > >> >> > `docker run -i --rm --name om-server-full --expose=5443
> --expose= -p 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> >> > >> >> >
> >> > >> >> > works as expected :)
> >> > >> >> >
> >> > >> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> >> > >> >> >>
> >> > >> >> >> > Will provide you with the complete list of commands I run
> >> > >> >> >> Thanks, it will be useful!
> >> > >> >> >>
> >> > >> >> >> > BTW just found this thread:
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> >> > >> >> >> > Might be useful for nginx users
> >> > >> >> >>
> >> > >> >> >> I'll check it.
> >> > >> >> >> Regards,
> >> > >> >> >> Yarema
> >> > >> >> >
> >> > >> >> >
> >> > >> >> >
> >> > >> >> > --
> >> > >> >> > WBR
> >> > >> >> > Maxim aka solomax
> >
> >
> >
> > --
> > WBR
> >

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

I checked your image, and got the same result, kurento is dead. I
gonna give up

$ docker info
Client:
 Debug Mode: false

Server:
 Containers: 4
  Running: 4
  Paused: 0
  Stopped: 0
 Images: 45
 Server Version: 19.03.2-ce
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local
logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.73-1-lts
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.789GiB
 Name: archmoodle
 ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
 Docker Root Dir: /home/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
>
> `docker info`
>
> Server Version: 19.03.2
>
>
> The image is uploaded, everything works as expected
> Just have double-checked
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : 
> openmeetings-docker-images.bintray.io/server-full:latest`
>
> On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
>>
>> BTW, what version of docker do you use?
>> $ docker info
>>
>> сб, 21 вер. 2019 о 18:30 YUP  пише:
>> >
>> > Great, thanks!
>> >
>> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>> > >
>> > > Well
>> > > I can upload my image to the bintray
>> > > And you can try it
>> > > Will do it tomorrow
>> > >
>> > > On Sat, Sep 21, 2019, 23:14 YUP  wrote:
>> > >>
>> > >> So something is wrong with Archlinux as a host machine and OM in
>> > >> docker. But it is nonsense, created image should not depend from host
>> > >> machine and om+mysql+kurento must run the same way...
>> > >>
>> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>> > >> >
>> > >> > Kurento and mysql are both started right before om
>> > >> > It is very clear from the logs
>> > >> > And both video and recording works in om :)
>> > >> >
>> > >> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>> > >> >>
>> > >> >> OK. Please enter your container with running OM:
>> > >> >>
>> > >> >> docker exec -it CONTAINER_ID bash
>> > >> >> and then check whether kurento running:
>> > >> >> ps xuaw | grep kurento
>> > >> >> or
>> > >> >> service kurento-media-server status
>> > >> >> and post the result, please.
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  
>> > >> >> пише:
>> > >> >> >
>> > >> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> > >> >> > `docker run -i --rm --name om-server-full --expose=5443 
>> > >> >> > --expose= -p 5443:5443 -p : -e OM_TYPE=full -it 
>> > >> >> > om-server-full`
>> > >> >> >
>> > >> >> > works as expected :)
>> > >> >> >
>> > >> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> > >> >> >>
>> > >> >> >> > Will provide you with the complete list of commands I run
>> > >> >> >> Thanks, it will be useful!
>> > >> >> >>
>> > >> >> >> > BTW just found this thread: 
>> > >> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> > >> >> >> > Might be useful for nginx users
>> > >> >> >>
>> > >> >> >> I'll check it.
>> > >> >> >> Regards,
>> > >> >> >> Yarema
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > --
>> > >> >> > WBR
>> > >> >> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

`docker info`

Server Version: 19.03.2


The image is uploaded, everything works as expected
Just have double-checked
`docker run -i --rm --name om-server-full --expose=5443 --expose= -p
5443:5443 -p :
openmeetings-docker-images.bintray.io/server-full:latest`

On Sat, 21 Sep 2019 at 23:43, YUP  wrote:

> BTW, what version of docker do you use?
> $ docker info
>
> сб, 21 вер. 2019 о 18:30 YUP  пише:
> >
> > Great, thanks!
> >
> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
> > >
> > > Well
> > > I can upload my image to the bintray
> > > And you can try it
> > > Will do it tomorrow
> > >
> > > On Sat, Sep 21, 2019, 23:14 YUP  wrote:
> > >>
> > >> So something is wrong with Archlinux as a host machine and OM in
> > >> docker. But it is nonsense, created image should not depend from host
> > >> machine and om+mysql+kurento must run the same way...
> > >>
> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik 
> пише:
> > >> >
> > >> > Kurento and mysql are both started right before om
> > >> > It is very clear from the logs
> > >> > And both video and recording works in om :)
> > >> >
> > >> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
> > >> >>
> > >> >> OK. Please enter your container with running OM:
> > >> >>
> > >> >> docker exec -it CONTAINER_ID bash
> > >> >> and then check whether kurento running:
> > >> >> ps xuaw | grep kurento
> > >> >> or
> > >> >> service kurento-media-server status
> > >> >> and post the result, please.
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik 
> пише:
> > >> >> >
> > >> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> > >> >> > `docker run -i --rm --name om-server-full --expose=5443
> --expose= -p 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> > >> >> >
> > >> >> > works as expected :)
> > >> >> >
> > >> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> > >> >> >>
> > >> >> >> > Will provide you with the complete list of commands I run
> > >> >> >> Thanks, it will be useful!
> > >> >> >>
> > >> >> >> > BTW just found this thread:
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> > >> >> >> > Might be useful for nginx users
> > >> >> >>
> > >> >> >> I'll check it.
> > >> >> >> Regards,
> > >> >> >> Yarema
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > WBR
> > >> >> > Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

Great, thanks!

сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>
> Well
> I can upload my image to the bintray
> And you can try it
> Will do it tomorrow
>
> On Sat, Sep 21, 2019, 23:14 YUP  wrote:
>>
>> So something is wrong with Archlinux as a host machine and OM in
>> docker. But it is nonsense, created image should not depend from host
>> machine and om+mysql+kurento must run the same way...
>>
>> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>> >
>> > Kurento and mysql are both started right before om
>> > It is very clear from the logs
>> > And both video and recording works in om :)
>> >
>> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>> >>
>> >> OK. Please enter your container with running OM:
>> >>
>> >> docker exec -it CONTAINER_ID bash
>> >> and then check whether kurento running:
>> >> ps xuaw | grep kurento
>> >> or
>> >> service kurento-media-server status
>> >> and post the result, please.
>> >>
>> >>
>> >>
>> >>
>> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>> >> >
>> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose= 
>> >> > -p 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>> >> >
>> >> > works as expected :)
>> >> >
>> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> >> >>
>> >> >> > Will provide you with the complete list of commands I run
>> >> >> Thanks, it will be useful!
>> >> >>
>> >> >> > BTW just found this thread: 
>> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> >> >> > Might be useful for nginx users
>> >> >>
>> >> >> I'll check it.
>> >> >> Regards,
>> >> >> Yarema
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > WBR
>> >> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

Well
I can upload my image to the bintray
And you can try it
Will do it tomorrow

On Sat, Sep 21, 2019, 23:14 YUP  wrote:

> So something is wrong with Archlinux as a host machine and OM in
> docker. But it is nonsense, created image should not depend from host
> machine and om+mysql+kurento must run the same way...
>
> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
> >
> > Kurento and mysql are both started right before om
> > It is very clear from the logs
> > And both video and recording works in om :)
> >
> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
> >>
> >> OK. Please enter your container with running OM:
> >>
> >> docker exec -it CONTAINER_ID bash
> >> and then check whether kurento running:
> >> ps xuaw | grep kurento
> >> or
> >> service kurento-media-server status
> >> and post the result, please.
> >>
> >>
> >>
> >>
> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
> >> >
> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose=
> -p 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> >> >
> >> > works as expected :)
> >> >
> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> >> >>
> >> >> > Will provide you with the complete list of commands I run
> >> >> Thanks, it will be useful!
> >> >>
> >> >> > BTW just found this thread:
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> >> >> > Might be useful for nginx users
> >> >>
> >> >> I'll check it.
> >> >> Regards,
> >> >> Yarema
> >> >
> >> >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax
>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

I've just installed on another Archlinux machine and result was the
same, kurento won't start. Damn.

сб, 21 вер. 2019 о 18:13 YUP  пише:
>
> So something is wrong with Archlinux as a host machine and OM in
> docker. But it is nonsense, created image should not depend from host
> machine and om+mysql+kurento must run the same way...
>
> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
> >
> > Kurento and mysql are both started right before om
> > It is very clear from the logs
> > And both video and recording works in om :)
> >
> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
> >>
> >> OK. Please enter your container with running OM:
> >>
> >> docker exec -it CONTAINER_ID bash
> >> and then check whether kurento running:
> >> ps xuaw | grep kurento
> >> or
> >> service kurento-media-server status
> >> and post the result, please.
> >>
> >>
> >>
> >>
> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
> >> >
> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> >> > 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> >> >
> >> > works as expected :)
> >> >
> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> >> >>
> >> >> > Will provide you with the complete list of commands I run
> >> >> Thanks, it will be useful!
> >> >>
> >> >> > BTW just found this thread: 
> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> >> >> > Might be useful for nginx users
> >> >>
> >> >> I'll check it.
> >> >> Regards,
> >> >> Yarema
> >> >
> >> >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

So something is wrong with Archlinux as a host machine and OM in
docker. But it is nonsense, created image should not depend from host
machine and om+mysql+kurento must run the same way...

сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>
> Kurento and mysql are both started right before om
> It is very clear from the logs
> And both video and recording works in om :)
>
> On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>>
>> OK. Please enter your container with running OM:
>>
>> docker exec -it CONTAINER_ID bash
>> and then check whether kurento running:
>> ps xuaw | grep kurento
>> or
>> service kurento-media-server status
>> and post the result, please.
>>
>>
>>
>>
>> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>> >
>> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
>> > 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>> >
>> > works as expected :)
>> >
>> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> >>
>> >> > Will provide you with the complete list of commands I run
>> >> Thanks, it will be useful!
>> >>
>> >> > BTW just found this thread: 
>> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> >> > Might be useful for nginx users
>> >>
>> >> I'll check it.
>> >> Regards,
>> >> Yarema
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

Kurento and mysql are both started right before om
It is very clear from the logs
And both video and recording works in om :)

On Sat, Sep 21, 2019, 22:55 YUP  wrote:

> OK. Please enter your container with running OM:
>
> docker exec -it CONTAINER_ID bash
> and then check whether kurento running:
> ps xuaw | grep kurento
> or
> service kurento-media-server status
> and post the result, please.
>
>
>
>
> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
> >
> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p
> 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> >
> > works as expected :)
> >
> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> >>
> >> > Will provide you with the complete list of commands I run
> >> Thanks, it will be useful!
> >>
> >> > BTW just found this thread:
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> >> > Might be useful for nginx users
> >>
> >> I'll check it.
> >> Regards,
> >> Yarema
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

OK. Please enter your container with running OM:

docker exec -it CONTAINER_ID bash
and then check whether kurento running:
ps xuaw | grep kurento
or
service kurento-media-server status
and post the result, please.




сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>
> `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>
> works as expected :)
>
> On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>>
>> > Will provide you with the complete list of commands I run
>> Thanks, it will be useful!
>>
>> > BTW just found this thread: 
>> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> > Might be useful for nginx users
>>
>> I'll check it.
>> Regards,
>> Yarema
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

`docker build -t om-server-full --build-arg BUILD_TYPE=full .`
`docker run -i --rm --name om-server-full --expose=5443 --expose= -p
5443:5443 -p : -e OM_TYPE=full -it om-server-full`

works as expected :)

On Sat, 21 Sep 2019 at 20:37, YUP  wrote:

> > Will provide you with the complete list of commands I run
> Thanks, it will be useful!
>
> > BTW just found this thread:
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> > Might be useful for nginx users
>
> I'll check it.
> Regards,
> Yarema
>


-- 
WBR
Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

> Will provide you with the complete list of commands I run
Thanks, it will be useful!

> BTW just found this thread: 
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> Might be useful for nginx users

I'll check it.
Regards,
Yarema

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

Double-checking it right now
Will provide you with the complete list of commands I run

BTW just found this thread:
https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
Might be useful for nginx users

On Sat, 21 Sep 2019 at 14:23, YUP  wrote:

> Yes, it is latest master with om 5.0.0-M2.
>
> On Sat, Sep 21, 2019, 08:56 Maxim Solodovnik  wrote:
>
>> Are you using latest master?
>> It works for me as expected
>>
>> On Sat, Sep 21, 2019, 11:32 YUP  wrote:
>>
>>> Installing OM 5.0.0-M2 docker:
>>>
>>> $ docker build -t om-server-full --build-arg BUILD_TYPE=full .
>>> $ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
>>> -it om-server-full
>>>
>>> 
>>>
>>> DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
>>> Configurations ADDED
>>> INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
>>> user id given
>>> DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
>>> configKeyCryptClassName:
>>> org.apache.openmeetings.util.crypt.SCryptImplemen
>>> tation
>>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
>>> [pool-1-thread-1] - [KurentoClient]  Connecting native client
>>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
>>> [pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
>>> INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>> [ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
>>> Will crea
>>> te new handler too!
>>> WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>> [pool-1-thread-1] - [KurentoClient]  Trying to close a
>>> JsonRpcClientNettyWeb
>>> Socket with channel == null
>>> WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
>>> [KurentoClient]  Error sending heartbeat to server. Exception: Interru
>>> ptedException while trying to acquire lock
>>> WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
>>> [KurentoClient]  Stopping heartbeat and closing client: failure during
>>>  heartbeat mechanism
>>> WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
>>> [pool-1-thread-1] - Fail to create Kurento client, will re-try in
>>> 1 ms
>>> ..
>>>
>>> That's it. Kurento server doesn't work.
>>>
>>>
>>>
>>> сб, 21 вер. 2019 о 06:02 YUP  пише:
>>> >
>>> > Gonna try...
>>> >
>>> > сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
>>> > >
>>> > > Just have updated master at
>>> https://github.com/openmeetings/openmeetings-docker
>>> > > Tests recordings works for me as expected
>>> > >
>>> > > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik 
>>> wrote:
>>> > >>
>>> > >> 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  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 
>>> 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  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 
>>> пише:
>>> > > >
>>> > > > Why do you using KMS in docker in Ubuntu?
>>> > > >
>>> > > > On Fri, 20 Sep 2019 at 19:54, YUP  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  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread YUP

Yes, it is latest master with om 5.0.0-M2.

On Sat, Sep 21, 2019, 08:56 Maxim Solodovnik  wrote:

> Are you using latest master?
> It works for me as expected
>
> On Sat, Sep 21, 2019, 11:32 YUP  wrote:
>
>> Installing OM 5.0.0-M2 docker:
>>
>> $ docker build -t om-server-full --build-arg BUILD_TYPE=full .
>> $ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
>> -it om-server-full
>>
>> 
>>
>> DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
>> Configurations ADDED
>> INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
>> user id given
>> DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
>> configKeyCryptClassName:
>> org.apache.openmeetings.util.crypt.SCryptImplemen
>> tation
>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [pool-1-thread-1] - [KurentoClient]  Connecting native client
>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
>> INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
>> Will crea
>> te new handler too!
>> WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [pool-1-thread-1] - [KurentoClient]  Trying to close a
>> JsonRpcClientNettyWeb
>> Socket with channel == null
>> WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
>> [KurentoClient]  Error sending heartbeat to server. Exception: Interru
>> ptedException while trying to acquire lock
>> WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
>> [KurentoClient]  Stopping heartbeat and closing client: failure during
>>  heartbeat mechanism
>> WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
>> [pool-1-thread-1] - Fail to create Kurento client, will re-try in
>> 1 ms
>> ..
>>
>> That's it. Kurento server doesn't work.
>>
>>
>>
>> сб, 21 вер. 2019 о 06:02 YUP  пише:
>> >
>> > Gonna try...
>> >
>> > сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
>> > >
>> > > Just have updated master at
>> https://github.com/openmeetings/openmeetings-docker
>> > > Tests recordings works for me as expected
>> > >
>> > > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik 
>> wrote:
>> > >>
>> > >> 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  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 
>> 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  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 
>> пише:
>> > > >
>> > > > Why do you using KMS in docker in Ubuntu?
>> > > >
>> > > > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
>> > > >> >
>> > > >> > You gave me a hint. Ill check it.
>> > > >> >
>> > > >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik <
>> solomax...@gmail.com> пише:
>> >

Re: Empty Recording files in OM 5.0.0-M2

2019-09-21 Thread Maxim Solodovnik

Are you using latest master?
It works for me as expected

On Sat, Sep 21, 2019, 11:32 YUP  wrote:

> Installing OM 5.0.0-M2 docker:
>
> $ docker build -t om-server-full --build-arg BUILD_TYPE=full .
> $ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
> -it om-server-full
>
> 
>
> DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
> Configurations ADDED
> INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
> user id given
> DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
> configKeyCryptClassName:
> org.apache.openmeetings.util.crypt.SCryptImplemen
> tation
> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [pool-1-thread-1] - [KurentoClient]  Connecting native client
> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
> INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
> Will crea
> te new handler too!
> WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [pool-1-thread-1] - [KurentoClient]  Trying to close a
> JsonRpcClientNettyWeb
> Socket with channel == null
> WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
> [KurentoClient]  Error sending heartbeat to server. Exception: Interru
> ptedException while trying to acquire lock
> WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
> [KurentoClient]  Stopping heartbeat and closing client: failure during
>  heartbeat mechanism
> WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
> [pool-1-thread-1] - Fail to create Kurento client, will re-try in
> 1 ms
> ..
>
> That's it. Kurento server doesn't work.
>
>
>
> сб, 21 вер. 2019 о 06:02 YUP  пише:
> >
> > Gonna try...
> >
> > сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
> > >
> > > Just have updated master at
> https://github.com/openmeetings/openmeetings-docker
> > > Tests recordings works for me as expected
> > >
> > > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik 
> wrote:
> > >>
> > >> 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  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 
> 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  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 
> пише:
> > > >
> > > > Why do you using KMS in docker in Ubuntu?
> > > >
> > > > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
> > > >> >
> > > >> > You gave me a hint. Ill check it.
> > > >> >
> > > >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik <
> solomax...@gmail.com> пише:
> > > >> > >
> > > >> > > 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)
>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

Installing OM 5.0.0-M2 docker:

$ docker build -t om-server-full --build-arg BUILD_TYPE=full .
$ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
-it om-server-full

DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
Configurations ADDED
INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
user id given
DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
configKeyCryptClassName:
org.apache.openmeetings.util.crypt.SCryptImplemen
tation
INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
[pool-1-thread-1] - [KurentoClient]  Connecting native client
INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
[pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
Will crea
te new handler too!
WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
[pool-1-thread-1] - [KurentoClient]  Trying to close a
JsonRpcClientNettyWeb
Socket with channel == null
WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
[KurentoClient]  Error sending heartbeat to server. Exception: Interru
ptedException while trying to acquire lock
WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
[KurentoClient]  Stopping heartbeat and closing client: failure during
 heartbeat mechanism
WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
[pool-1-thread-1] - Fail to create Kurento client, will re-try in
1 ms
..

That's it. Kurento server doesn't work.

сб, 21 вер. 2019 о 06:02 YUP  пише:
>
> Gonna try...
>
> сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
> >
> > Just have updated master at 
> > https://github.com/openmeetings/openmeetings-docker
> > Tests recordings works for me as expected
> >
> > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik  wrote:
> >>
> >> 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  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  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  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  пише:
> > >
> > > Why do you using KMS in docker in Ubuntu?
> > >
> > > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
> > >> >
> > >> > You gave me a hint. Ill check it.
> > >> >
> > >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  
> > >> > пише:
> > >> > >
> > >> > > 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  wrote:
> > >> > >>
> > >> > >> nobody:nogroup
> > >> > >>
> > >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
> > >> > >>  пише:
> > >> > >> >
> > >> > >> > Can you check files have correct owner?
> > >> > >> >
> > >> > >> >

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

Gonna try...

сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
>
> Just have updated master at 
> https://github.com/openmeetings/openmeetings-docker
> Tests recordings works for me as expected
>
> On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik  wrote:
>>
>> 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  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  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  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  пише:
> >
> > Why do you using KMS in docker in Ubuntu?
> >
> > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
> >> >
> >> > You gave me a hint. Ill check it.
> >> >
> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  
> >> > пише:
> >> > >
> >> > > 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  wrote:
> >> > >>
> >> > >> nobody:nogroup
> >> > >>
> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  
> >> > >> пише:
> >> > >> >
> >> > >> > Can you check files have correct owner?
> >> > >> >
> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> >> > >> >>
> >> > >> >> That's right, they are placed in correct places, but have 0 
> >> > >> >> bytes.
> >> > >> >>
> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik 
> >> > >> >>  пише:
> >> > >> >> >
> >> > >> >> > Hello Yarema,
> >> > >> >> >
> >> > >> >> > so `webm` files are being created in correct place? but they 
> >> > >> >> > are empty?
> >> > >> >> >
> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

Just have updated master at
https://github.com/openmeetings/openmeetings-docker
Tests recordings works for me as expected

On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik  wrote:

> 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  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 
>> 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  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  пише:
 >
 > Why do you using KMS in docker in Ubuntu?
 >
 > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
 >> >
 >> > You gave me a hint. Ill check it.
 >> >
 >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik 
 пише:
 >> > >
 >> > > 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  wrote:
 >> > >>
 >> > >> nobody:nogroup
 >> > >>
 >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
 пише:
 >> > >> >
 >> > >> > Can you check files have correct owner?
 >> > >> >
 >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
 >> > >> >>
 >> > >> >> That's right, they are placed in correct places, but have 0
 bytes.
 >> > >> >>
 >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik <
 solomax...@gmail.com> пише:
 >> > >> >> >
 >> > >> >> > Hello Yarema,
 >> > >> >> >
 >> > >> >> > so `webm` files are being created in correct place? but
 they are empty?
 >> > >> >> >
 >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP 
 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
>>>
>>

-- 
WBR
Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

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  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  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  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  пише:
>>> >
>>> > Why do you using KMS in docker in Ubuntu?
>>> >
>>> > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
>>> >> >
>>> >> > You gave me a hint. Ill check it.
>>> >> >
>>> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik 
>>> пише:
>>> >> > >
>>> >> > > 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  wrote:
>>> >> > >>
>>> >> > >> nobody:nogroup
>>> >> > >>
>>> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
>>> пише:
>>> >> > >> >
>>> >> > >> > Can you check files have correct owner?
>>> >> > >> >
>>> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>>> >> > >> >>
>>> >> > >> >> That's right, they are placed in correct places, but have 0
>>> bytes.
>>> >> > >> >>
>>> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik <
>>> solomax...@gmail.com> пише:
>>> >> > >> >> >
>>> >> > >> >> > Hello Yarema,
>>> >> > >> >> >
>>> >> > >> >> > so `webm` files are being created in correct place? but
>>> they are empty?
>>> >> > >> >> >
>>> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP 
>>> 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
>>
>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

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  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  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  пише:
>> >
>> > Why do you using KMS in docker in Ubuntu?
>> >
>> > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
>> >> >
>> >> > You gave me a hint. Ill check it.
>> >> >
>> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik 
>> пише:
>> >> > >
>> >> > > 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  wrote:
>> >> > >>
>> >> > >> nobody:nogroup
>> >> > >>
>> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
>> пише:
>> >> > >> >
>> >> > >> > Can you check files have correct owner?
>> >> > >> >
>> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> >> > >> >>
>> >> > >> >> That's right, they are placed in correct places, but have 0
>> bytes.
>> >> > >> >>
>> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik <
>> solomax...@gmail.com> пише:
>> >> > >> >> >
>> >> > >> >> > Hello Yarema,
>> >> > >> >> >
>> >> > >> >> > so `webm` files are being created in correct place? but they
>> are empty?
>> >> > >> >> >
>> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP 
>> 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
>

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

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  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  пише:
> >
> > Why do you using KMS in docker in Ubuntu?
> >
> > On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
> >> >
> >> > You gave me a hint. Ill check it.
> >> >
> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik 
> пише:
> >> > >
> >> > > 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  wrote:
> >> > >>
> >> > >> nobody:nogroup
> >> > >>
> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
> пише:
> >> > >> >
> >> > >> > Can you check files have correct owner?
> >> > >> >
> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> >> > >> >>
> >> > >> >> That's right, they are placed in correct places, but have 0
> bytes.
> >> > >> >>
> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik 
> пише:
> >> > >> >> >
> >> > >> >> > Hello Yarema,
> >> > >> >> >
> >> > >> >> > so `webm` files are being created in correct place? but they
> are empty?
> >> > >> >> >
> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

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  пише:
>
> Why do you using KMS in docker in Ubuntu?
>
> On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
>> >
>> > You gave me a hint. Ill check it.
>> >
>> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
>> > >
>> > > 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  wrote:
>> > >>
>> > >> nobody:nogroup
>> > >>
>> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
>> > >> >
>> > >> > Can you check files have correct owner?
>> > >> >
>> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> > >> >>
>> > >> >> That's right, they are placed in correct places, but have 0 bytes.
>> > >> >>
>> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  
>> > >> >> пише:
>> > >> >> >
>> > >> >> > Hello Yarema,
>> > >> >> >
>> > >> >> > so `webm` files are being created in correct place? but they are 
>> > >> >> > empty?
>> > >> >> >
>> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

Why do you using KMS in docker in Ubuntu?

On Fri, 20 Sep 2019 at 19:54, YUP  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  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  пише:
> >
> > You gave me a hint. Ill check it.
> >
> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
> > >
> > > 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  wrote:
> > >>
> > >> nobody:nogroup
> > >>
> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
> пише:
> > >> >
> > >> > Can you check files have correct owner?
> > >> >
> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> > >> >>
> > >> >> That's right, they are placed in correct places, but have 0 bytes.
> > >> >>
> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik 
> пише:
> > >> >> >
> > >> >> > Hello Yarema,
> > >> >> >
> > >> >> > so `webm` files are being created in correct place? but they are
> empty?
> > >> >> >
> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

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  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  пише:
>
> You gave me a hint. Ill check it.
>
> пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
> >
> > 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  wrote:
> >>
> >> nobody:nogroup
> >>
> >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
> >> >
> >> > Can you check files have correct owner?
> >> >
> >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> >> >>
> >> >> That's right, they are placed in correct places, but have 0 bytes.
> >> >>
> >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
> >> >> >
> >> >> > Hello Yarema,
> >> >> >
> >> >> > so `webm` files are being created in correct place? but they are 
> >> >> > empty?
> >> >> >
> >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

You gave me a hint. Ill check it.

пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
>
> 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  wrote:
>>
>> nobody:nogroup
>>
>> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
>> >
>> > Can you check files have correct owner?
>> >
>> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> >>
>> >> That's right, they are placed in correct places, but have 0 bytes.
>> >>
>> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
>> >> >
>> >> > Hello Yarema,
>> >> >
>> >> > so `webm` files are being created in correct place? but they are empty?
>> >> >
>> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

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

> nobody:nogroup
>
> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
> >
> > Can you check files have correct owner?
> >
> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> >>
> >> That's right, they are placed in correct places, but have 0 bytes.
> >>
> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
> >> >
> >> > Hello Yarema,
> >> >
> >> > so `webm` files are being created in correct place? but they are
> empty?
> >> >
> >> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

Can you check files have correct owner?

On Fri, 20 Sep 2019 at 14:09, YUP  wrote:

> That's right, they are placed in correct places, but have 0 bytes.
>
> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
> >
> > Hello Yarema,
> >
> > so `webm` files are being created in correct place? but they are empty?
> >
> > On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread YUP

That's right, they are placed in correct places, but have 0 bytes.

пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
>
> Hello Yarema,
>
> so `webm` files are being created in correct place? but they are empty?
>
> On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

2019-09-20 Thread Maxim Solodovnik

Hello Yarema,

so `webm` files are being created in correct place? but they are empty?

On Fri, 20 Sep 2019 at 04:19, YUP  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

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

Re: Empty Recording files in OM 5.0.0-M2

32 matches

Site Navigation

Mail list logo

Footer information