Unsubscribtion

[dhanashree.kulkarni]

Hello,

 

I want to unsubscribe myself from this user mailing list and do not wish to
receive any further updates about the same. Thank you.

 

Best Regards,

Dhanashree Kulkarni

 

brown-iposs GmbH

Friedrich-Breuer-Straße 120

53225 Bonn

Germany

 

Fon   +49 (0) 228 299 799 80

Fax   +49 (0) 228 299 799 84

 
mailto:birgit.bachm...@brown-iposs.eu

  www.brown-iposs.eu

  www.facebook.com/browniposs

  www.facebook.com/wimap4g

 

Directors: Dr. Bernd Schröder, Karsten Schmeling

Trade register: 14385, Country court Bonn

VAT-ID: DE814670174

 

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

 

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

 

Re: Unsubscribtion

[Maxim Solodovnik]

Please visit "Unsubscribe" link from user@ list here
https://openmeetings.apache.org/mailing-lists.html

On Fri, 18 Jan 2019 at 17:51,  wrote:

> Hello,
>
>
>
> I want to unsubscribe myself from this user mailing list and do not wish
> to receive any further updates about the same. Thank you.
>
>
>
> Best Regards,
>
> Dhanashree Kulkarni
>
>
>
> brown-iposs GmbH
>
> Friedrich-Breuer-Straße 120
>
> 53225 Bonn
>
> Germany
>
>
>
> Fon   +49 (0) 228 299 799 80
>
> Fax   +49 (0) 228 299 799 84
>
> mailto:birgit.bachm...@brown-iposs.eu 
>
> www.brown-iposs.eu
>
> www.facebook.com/browniposs
>
> www.facebook.com/wimap4g
>
>
>
> Directors: Dr. Bernd Schröder, Karsten Schmeling
>
> Trade register: 14385, Country court Bonn
>
> VAT-ID: DE814670174
>
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>
>
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
>
>


-- 
WBR
Maxim aka solomax

OM5 config and SSL

[Aaron Hepp]

downloaded and unzipped the latest nightly build for OM5 (#2690).  cd to 
/opt/om5/bin and ran sh startup.sh.  Service started up and nmap showed 
port 5080 and 8009 listening.  Redirection worked to port 5443.  Issue I 
was having with the cert not working was failed to change the password 
for the keystore file in server.xml.  Once that changed no longer had 
the bad cert error.  I was able to change the default ports in 
server.xml and listening and redirection worked fine.


Question are you supposed to start and stop using the startup.sh and 
shutdown.sh files in om5/bin?  startup works fine and gets it running, 
but when running shutdown it stops listening on the ports, but leaves 
java process running in the background.  If you run startup again it 
creates a second java process (see attached), and each time you shutdown 
and start it creates a new.

Re: Possible Memory Leak

[Maxim Solodovnik]

weird enough this issue was not reproducible on my local machine
(Chrome+Chromium)
Will do some tests

On Fri, 18 Jan 2019 at 08:20, Maxim Solodovnik  wrote:

> Thanks for the video
> Will try to reproduce this issue today (it also might be caused by red5
> update )
>
> Could you please start another thread regarding OM5 configuration
>
> On Fri, 18 Jan 2019 at 00:45, Aaron Hepp  wrote:
>
>> Here is logging out of the demo room and logging right back in.
>>
>> http://recordit.co/YtGlxUzNai
>>
>>
>> On 1/17/19 12:09 PM, Maxim Solodovnik wrote:
>>
>> You have to be root to run tomcat on port 443
>> Other than that there should be no issues, just invalid certificate (at
>> least if you will access it using localhost)
>> Will try to perform run on port 443 tomorrow
>>
>> On Thu, Jan 17, 2019, 23:52 Aaron Hepp >
>>> It would be pure Tomcat.  I was playing around with it over the
>>> weekend.  I got it to load on 5443 but it never accepted the cert, when I
>>> changed it to 443 I don't think it ever opened up the port.
>>> I thought I had changed the settings it was looking for on the location
>>> of the PEM files.
>>>
>>> On 1/17/19 11:46 AM, Maxim Solodovnik wrote:
>>>
>>> Sure :)
>>> I'll help you to set everything, hope this will help to create
>>> documentation ;)
>>>
>>> Are you interested in pure tomcat based config or do you have frontend
>>> Apache?
>>>
>>> Actually all have to do is to set up https on tomcat :)
>>> Packaged version of om works as expected on port 5443 by default
>>>
>>> So you can check https without any additional steps
>>>
>>> On Thu, Jan 17, 2019, 23:33 Aaron Hepp >>
 I will test those in a little bit.  Currently in the VPS I run the
 delay is now over a minute from the person broadcasts to when the guests
 hear it.  The memory on the VPS has only gone up about 300MB since people
 started coming in @ 8:30am EST (so about 2 hours of running).

 I have an active stream going in both 4.0.7 and the 4.0.8snap  will
 watch them to see if they all start having the same delay affect.

 Oddly the screen sharing which uses the same port (1935) does not
 experience the delay.  So this may possible be leading to a flash issue and
 not an OM issue.

 I was going to start testing version 5 since that does away with flash,
 but noticed the different file structure in there for getting https to
 work.  Do you have a quick how to on setting up version 5 on 443?

 On 1/17/19 10:28 AM, Maxim Solodovnik wrote:

 Thanks Aaron,

 both 4.0.7 and 4.0.8 are available for testing
 I would appreciate if you can check both versions :)

 On Thu, 17 Jan 2019 at 19:37, Aaron Hepp  wrote:

> On the demo (4.0.8 rb66ef46) there is only about a 5-7 second delay
> from the talking till it is broadcasted (this would be expected depending
> on where the servers are located and the speed of its connection).
> Currently about the same delay I have on a fresh restart of the OM service
> on my VPS.  I will keep both open all day and see if the delay changes 
> any.
>
> On 1/16/19 11:01 PM, Maxim Solodovnik wrote:
>
> Hello Aaron,
>
> According to `top` our two OM instances consuming not very much memory
> on demo:
>  1186 nobody20   0 6716968 1.421g  23308 S  20.9  6.0   1116:35
> java
> 25008 nobody20   0 6647688 752492  26656 S   1.0  3.0  97:29.05
> java
>
> 4.0.7 consuming 1.4G (was started right after release, more than 2
> weeks ago), will additionally check audio delay
>
> java options used differs:
>
> 4.0.7:
> export JAVA_OPTS="-Xrs -Xms4G -Xmx4G -Xss1M -XX:PermSize=192m
> -XX:MaxPermSize=512m -XX:+CMSClassUnloadingEnabled -XX:NewSize=256m
> -XX:SurvivorRatio=16 -XX:MinHeapFreeRatio=20
> -XX:+ExplicitGCInvokesConcurrent -XX:+UseConcMarkSweepGC
> -Djava.net.preferIPv4Stack=true -Xverify:none"
>
> 4.0.8
> export JAVA_OPTS="-Xrs -Xms4G -Xmx4G -Xss1M
> -XX:+CMSClassUnloadingEnabled -XX:NewSize=256m -XX:SurvivorRatio=16
> -XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
> -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none"
>
> 4.0.8 options looks better to me.
>
> Could you also check demo?
> I'll update "next" with most recent build (with most recent wicket)
>
> On Thu, 17 Jan 2019 at 10:12, Maxim Solodovnik 
> wrote:
>
>> Hello Aaron,
>>
>> I'm afraid this might be caused by this
>> https://issues.apache.org/jira/browse/WICKET-6629 issue
>> I'll try to double-check on our demo server, and maybe speed up next
>> releases of both wicket and openmeetings
>>
>> Thanks for the report
>>
>> On Thu, 17 Jan 2019 at 07:16, Aaron Hepp 
>> wrote:
>>
>>> Looks like this has started with 4.0.7, but will need to look into
>>> further.  On Sunday I restarted my VPS (Ub

Re: OM5 config and SSL

[Maxim Solodovnik]

Hello Aaron,

I'm glad port issue was resolved.
According to startup/shutdown these scripts are bundled with Tomcat and
should work
I'm planning to investigate what is wrong, since it affects demo server
(I'm using Ubuntu and something like this should work [1])
Unfortunately my time is very limited these days :(

What I already have tried:
1) use catalina.sh to start Tomcat, provide valid CATALINA_PID
2) use `kill -9 `
for some reason this is not working right now (was working as expected)
and this method will not work on non-debian distros and other OSes
Additional investigation is required

[1] https://linuxize.com/post/how-to-install-tomcat-9-on-ubuntu-18-04/

On Fri, 18 Jan 2019 at 19:15, Aaron Hepp  wrote:

> downloaded and unzipped the latest nightly build for OM5 (#2690).  cd to
> /opt/om5/bin and ran sh startup.sh.  Service started up and nmap showed
> port 5080 and 8009 listening.  Redirection worked to port 5443.  Issue I
> was having with the cert not working was failed to change the password for
> the keystore file in server.xml.  Once that changed no longer had the bad
> cert error.  I was able to change the default ports in server.xml and
> listening and redirection worked fine.
>
> Question are you supposed to start and stop using the startup.sh and
> shutdown.sh files in om5/bin?  startup works fine and gets it running, but
> when running shutdown it stops listening on the ports, but leaves java
> process running in the background.  If you run startup again it creates a
> second java process (see attached), and each time you shutdown and start it
> creates a new.
>
>

-- 
WBR
Maxim aka solomax

Re: Possible Memory Leak

[Aaron Hepp]

I would not spend too much time on it.  It is looking like it is Flash 
related and not on the OM side.


On 1/18/19 9:35 AM, Maxim Solodovnik wrote:
weird enough this issue was not reproducible on my local machine 
(Chrome+Chromium)

Will do some tests

On Fri, 18 Jan 2019 at 08:20, Maxim Solodovnik > wrote:


Thanks for the video
Will try to reproduce this issue today (it also might be caused by
red5 update )

Could you please start another thread regarding OM5 configuration

On Fri, 18 Jan 2019 at 00:45, Aaron Hepp mailto:aaron.h...@gmail.com>> wrote:

Here is logging out of the demo room and logging right back in.

http://recordit.co/YtGlxUzNai


On 1/17/19 12:09 PM, Maxim Solodovnik wrote:

You have to be root to run tomcat on port 443
Other than that there should be no issues, just invalid
certificate (at least if you will access it using localhost)
Will try to perform run on port 443 tomorrow

On Thu, Jan 17, 2019, 23:52 Aaron Hepp mailto:aaron.h...@gmail.com> wrote:

It would be pure Tomcat.  I was playing around with it
over the weekend.  I got it to load on 5443 but it never
accepted the cert, when I changed it to 443 I don't think
it ever opened up the port.
I thought I had changed the settings it was looking for
on the location of the PEM files.

On 1/17/19 11:46 AM, Maxim Solodovnik wrote:

Sure :)
I'll help you to set everything, hope this will help to
create documentation ;)

Are you interested in pure tomcat based config or do you
have frontend Apache?

Actually all have to do is to set up https on tomcat :)
Packaged version of om works as expected on port 5443 by
default

So you can check https without any additional steps

On Thu, Jan 17, 2019, 23:33 Aaron Hepp
mailto:aaron.h...@gmail.com> wrote:

I will test those in a little bit.  Currently in the
VPS I run the delay is now over a minute from the
person broadcasts to when the guests hear it.  The
memory on the VPS has only gone up about 300MB since
people started coming in @ 8:30am EST (so about 2
hours of running).

I have an active stream going in both 4.0.7 and the
4.0.8snap  will watch them to see if they all start
having the same delay affect.

Oddly the screen sharing which uses the same port
(1935) does not experience the delay.  So this may
possible be leading to a flash issue and not an OM
issue.

I was going to start testing version 5 since that
does away with flash, but noticed the different file
structure in there for getting https to work.  Do
you have a quick how to on setting up version 5 on 443?

On 1/17/19 10:28 AM, Maxim Solodovnik wrote:

Thanks Aaron,

both 4.0.7 and 4.0.8 are available for testing
I would appreciate if you can check both versions :)

On Thu, 17 Jan 2019 at 19:37, Aaron Hepp
mailto:aaron.h...@gmail.com>> wrote:

On the demo (4.0.8 rb66ef46) there is only
about a 5-7 second delay from the talking till
it is broadcasted (this would be expected
depending on where the servers are located and
the speed of its connection).  Currently about
the same delay I have on a fresh restart of the
OM service on my VPS.  I will keep both open
all day and see if the delay changes any.

On 1/16/19 11:01 PM, Maxim Solodovnik wrote:

Hello Aaron,

According to `top` our two OM instances
consuming not very much memory on demo:
 1186 nobody 20   0 6716968 1.421g  23308 S
20.9  6.0   1116:35 java
25008 nobody 20   0 6647688 752492  26656 S
 1.0  3.0  97:29.05 java

4.0.7 consuming 1.4G (was started right after
release, more than 2 weeks ago), will
additionally check audio delay

java options used differs:

4.0.7:
export JAVA_OPTS="-Xrs -Xms4G -Xmx4G -Xss1M
-XX:PermSize=192m -XX:MaxPermSize=512m
-XX:+CMSClassUnloadingEnabled -XX:NewSize=256m
-XX:SurvivorRatio=16 -XX:MinHeapFreeRatio=20
-XX:+ExplicitGCInvokesConcurrent