Re: Development move to 5.0
Hello Maxim, I could not find your script for OM 5.0.0 in other threads,but 've been able to modify the one i had and now it is possiblerestart without problems. The script was not for me, but for the community of OpenMeetings throughthe installation tutorials. Thank you in any way. Alvaro . El vie, 25-01-2019 a las 18:30 +0100, Alvaro escribió: > So, could you please appoint me to the threadwhere is the script? > Thanks > . > El vie, 25-01-2019 a las 23:23 +0700, Maxim Solodovnik escribió: > > my script also performs restart :) (according to my tests :))) > > On Fri, 25 Jan 2019 at 22:47, Alvaro wrote: > > > Ok. My question is a script about "restart", becausewhen i > > > restart OM 5.0.0 with the scripts that i havebecome trebol about > > > the system (java?) and no restart. > > > > > > .. > > > > > > El vie, 25-01-2019 a las 22:29 +0700, Maxim Solodovnik escribió: > > > > Hello Alvaro I just have posted start/stop script to other > > > > thread > > > > On Wed, 23 Jan 2019 at 23:26, Alvaro > > > > wrote: > > > > > Maxim have you a script to run Tomcat-OM-5.0.0? > > > > > . > > > > > El mié, 23-01-2019 a las 17:22 +0100, Alvaro escribió: > > > > > > Ok, thanks. > > > > > > Am testing OM 5.0.0 - 2695 > > > > > > Will test demo (om-next) too. > > > > > > Alvaro > > > > > > . > > > > > > > > > > > > El mié, 23-01-2019 a las 23:05 +0700, Maxim Solodovnik > > > > > > escribió: > > > > > > > Actually the idea was to > > > > > > > 1) to do more testing on more powerful demo (om-next) > > > > > > > 2) release 5.0.0-M1 == pre-production version, so users > > > > > > > can test Milestone1 (and not just snapshot) > > > > > > > iterate M2, M3 etc. > > > > > > > X) release 5.0.0 > > > > > > > > > > > > > > 4.0.x will be released as well > > > > > > > This is the only version for IE users (and it seems for > > > > > > > Edge users also ) > > > > > > > So it will be maintained > > > > > > > > > > > > > > > > > > > > > On Wed, 23 Jan 2019 at 21:50, Alvaro > > > > > > > wrote: > > > > > > > > Am not sure if i understand the question. > > > > > > > > Go from OM 4.0.7 to OM 5.0 release?If is so, i don't > > > > > > > > find right to do it when you, Maxim,said that OM 5.0 > > > > > > > > have not yet all features ok. > > > > > > > > We have one more year with Adobe flash on. Sois time to > > > > > > > > put ready OM 5.0.Offer to the users a unfinished > > > > > > > > release, withoutnecessity, would be not very serious. > > > > > > > > It is time to make it rightly. > > > > > > > > Some users, me also, can test OM 5.0 and makejira abou > > > > > > > > it with issues found. > > > > > > > > Patience, yet is time. > > > > > > > > Alvaro > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > El mié, 23-01-2019 a las 09:40 +0700, Maxim Solodovnik > > > > > > > > escribió: > > > > > > > > > Hello Aaron, > > > > > > > > > I'm currently working on screen-sharing/recording > > > > > > > > > support > > > > > > > > > And trying to address all corner cases: media server > > > > > > > > > up/down, some network problems etc. > > > > > > > > > > > > > > > > > > You, and all users, can help by reporting issues with > > > > > > > > > current version (functionality/usability/performance) > > > > > > > > > I can replace "next" version with 5.0.0 and made > > > > > > > > > updates regular (this machine has more CPU/RAM etc.) > > > > > > > > > > > > > > > > > > Another huge area is documentation > > > > > > > > > > > > > > > > > > 5.0.0-M1 can be released without all features > > > > > > > > > > > > > > > > > > currently unimplemented: > > > > > > > > > 1) screen-sharing/recording - in progress, must be > > > > > > > > > done before release > > > > > > > > > 2) external video in the room > > > > > > > > > 3) SIP/Asterisk integration > > > > > > > > > > > > > > > > > > WDYT? > > > > > > > > > On Wed, 23 Jan 2019 at 02:16, Aaron Hepp > > > > > > > > gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > With Adobe announcing their > > > > > > > > > > ending support for flash in 2020 and most > > > > > > > > > > major browsers (expect > > > > > > > > > > Firefox) starting to block and require > > > > > > > > > > acceptance to run flash > > > > > > > > > > each time a page is loaded with it; was > > > > > > > > > > wondering if there was a > > > > > > > > > > cut off date for advancements in Version 4 > > > > > > > > > > and the migration to > > > > > > > > > > version 5? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I played around with version 5 and there > > > > > > > > > > seems to be a few bugs > > > > > > > > > > but understandable since it was not the > > > > > > > > >
Fwd: Re: OM5 config and SSL
Isn't this the script ?
Forwarded Message
Subject:Re: OM5 config and SSL
Date: Fri, 25 Jan 2019 22:29:18 +0700
From: Maxim Solodovnik
Reply-To: user@openmeetings.apache.org
To: Openmeetings user-list
Just have performed additional checks on clean VM (Ubuntu 16)
Below script seems to work as expected
#!/bin/bash
### BEGIN INIT INFO
# Provides: OpenMeetings
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop OpenMeetings server
### END INIT INFO
DESC="OpenMeetings server"
NAME=openmeetings
OM_HOME=/opt/red5 ##todo
PATH=/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
export CATALINA_PID=/var/run/${NAME}.pid
start() {
cd ${OM_HOME}
touch ${CATALINA_PID}
chown nobody ${CATALINA_PID}
# HOME is required for jodConverter
#/usr/bin/sudo -u nobody HOME=${OM_HOME}/temp
CATALINA_PID=${CATALINA_PID=} ${OM_HOME}/bin/startup.sh
/usr/bin/sudo -u nobody CATALINA_PID=${CATALINA_PID}
${OM_HOME}/bin/startup.sh
}
stop() {
# TPID=$(ps aux | grep tomcat | awk 'NR==1{print $2}') # -- might be useful
TPID=$(cat ${CATALINA_PID})
kill -9 ${TPID}
}
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
start
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
stop
echo "."
;;
restart|force-reload)
echo -n "Restarting $DESC: $NAME"
stop
sleep 5
start
echo "."
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
On Fri, 18 Jan 2019 at 21:32, Maxim Solodovnik > wrote:
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 mailto:aaron.h...@gmail.com>> 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
--
WBR
Maxim aka solomax
Re: Re: OM5 config and SSL
Yep :)
this script works for me :)
All improvements are appreciated :)
On Tue, 29 Jan 2019 at 20:56, Daniel Baker
wrote:
> Isn't this the script ?
>
>
> Forwarded Message
> Subject: Re: OM5 config and SSL
> Date: Fri, 25 Jan 2019 22:29:18 +0700
> From: Maxim Solodovnik
> Reply-To: user@openmeetings.apache.org
> To: Openmeetings user-list
>
>
> Just have performed additional checks on clean VM (Ubuntu 16)
> Below script seems to work as expected
>
>
> #!/bin/bash
>
> ### BEGIN INIT INFO
> # Provides: OpenMeetings
> # Required-Start: $network
> # Required-Stop: $network
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> # Short-Description: Start/Stop OpenMeetings server
> ### END INIT INFO
>
> DESC="OpenMeetings server"
> NAME=openmeetings
> OM_HOME=/opt/red5 ##todo
> PATH=/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> export CATALINA_PID=/var/run/${NAME}.pid
>
> start() {
> cd ${OM_HOME}
> touch ${CATALINA_PID}
> chown nobody ${CATALINA_PID}
> # HOME is required for jodConverter
> #/usr/bin/sudo -u nobody HOME=${OM_HOME}/temp
> CATALINA_PID=${CATALINA_PID=} ${OM_HOME}/bin/startup.sh
> /usr/bin/sudo -u nobody CATALINA_PID=${CATALINA_PID}
> ${OM_HOME}/bin/startup.sh
> }
>
> stop() {
> # TPID=$(ps aux | grep tomcat | awk 'NR==1{print $2}') # -- might be useful
> TPID=$(cat ${CATALINA_PID})
> kill -9 ${TPID}
> }
>
> case "$1" in
> start)
> echo -n "Starting $DESC: $NAME"
> start
> echo "."
> ;;
> stop)
> echo -n "Stopping $DESC: $NAME"
> stop
> echo "."
> ;;
>
> restart|force-reload)
> echo -n "Restarting $DESC: $NAME"
> stop
> sleep 5
> start
> echo "."
> ;;
>
> *)
> echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
> exit 1
> ;;
>
> esac
>
>
> On Fri, 18 Jan 2019 at 21:32, Maxim Solodovnik
> wrote:
>
>> 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
>>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Development move to 5.0
Sorry for keeping silence Alvaro :( Glad everything is OK :) On Tue, 29 Jan 2019 at 20:15, Alvaro wrote: > Hello Maxim, > > I could not find your script for OM 5.0.0 in other threads, > but 've been able to modify the one i had and now it is possible > restart without problems. > > The script was not for me, but for the community of OpenMeetings through > the installation tutorials. > > Thank you in any way. > > Alvaro > > > . > > > > > El vie, 25-01-2019 a las 18:30 +0100, Alvaro escribió: > > > So, could you please appoint me to the thread > where is the script? > > Thanks > > . > > El vie, 25-01-2019 a las 23:23 +0700, Maxim Solodovnik escribió: > > my script also performs restart :) > (according to my tests :))) > > On Fri, 25 Jan 2019 at 22:47, Alvaro wrote: > > Ok. My question is a script about "restart", because > when i restart OM 5.0.0 with the scripts that i have > become trebol about the system (java?) and no restart. > > > .. > > > El vie, 25-01-2019 a las 22:29 +0700, Maxim Solodovnik escribió: > > Hello Alvaro I just have posted start/stop script to other thread > > On Wed, 23 Jan 2019 at 23:26, Alvaro wrote: > > Maxim have you a script to run Tomcat-OM-5.0.0? > > . > > El mié, 23-01-2019 a las 17:22 +0100, Alvaro escribió: > > Ok, thanks. > > Am testing OM 5.0.0 - 2695 > > Will test demo (om-next) too. > > Alvaro > > . > > > El mié, 23-01-2019 a las 23:05 +0700, Maxim Solodovnik escribió: > > Actually the idea was to > > 1) to do more testing on more powerful demo (om-next) > 2) release 5.0.0-M1 == pre-production version, so users can test > Milestone1 (and not just snapshot) > iterate M2, M3 etc. > X) release 5.0.0 > > 4.0.x will be released as well > This is the only version for IE users (and it seems for Edge users also > ) > So it will be maintained > > > On Wed, 23 Jan 2019 at 21:50, Alvaro wrote: > > > Am not sure if i understand the question. > > Go from OM 4.0.7 to OM 5.0 release? > If is so, i don't find right to do it when you, Maxim, > said that OM 5.0 have not yet all features ok. > > We have one more year with Adobe flash on. So > is time to put ready OM 5.0. > Offer to the users a unfinished release, without > necessity, would be not very serious. > > It is time to make it rightly. > > Some users, me also, can test OM 5.0 and make > jira abou it with issues found. > > Patience, yet is time. > > Alvaro > > > > > El mié, 23-01-2019 a las 09:40 +0700, Maxim Solodovnik escribió: > > Hello Aaron, > > I'm currently working on screen-sharing/recording support > And trying to address all corner cases: media server up/down, some network > problems etc. > > You, and all users, can help by reporting issues with current version > (functionality/usability/performance) > I can replace "next" version with 5.0.0 and made updates regular (this > machine has more CPU/RAM etc.) > > Another huge area is documentation > > 5.0.0-M1 can be released without all features > > currently unimplemented: > 1) screen-sharing/recording - in progress, must be done before release > 2) external video in the room > 3) SIP/Asterisk integration > > WDYT? > > On Wed, 23 Jan 2019 at 02:16, Aaron Hepp wrote: > > With Adobe announcing their ending support for flash in 2020 and most > major browsers (expect Firefox) starting to block and require acceptance to > run flash each time a page is loaded with it; was wondering if there was a > cut off date for advancements in Version 4 and the migration to version 5? > > I played around with version 5 and there seems to be a few bugs but > understandable since it was not the main development platform. > > > > -- > WBR > Maxim aka solomax > > > > > -- > WBR > Maxim aka solomax > > > > > -- > WBR > Maxim aka solomax > > > > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
