You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2017/11/29 06:07:34 UTC
Re: about openmeetings server start problem
Hello,
please do not write personal emails, write to the user@ list
http://openmeetings.apache.org/mail-lists.html (you need to subscribe first)
According to your question: you need to create startup script for OM,
please check installation guides:
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
And/or search through mailing list archives:
http://openmeetings.markmail.org/
On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
> hi, Mr. Maxim Solodovnik
>
> I have installed the openmeetings and worked well,but when I reboot my
> server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
> came up.
> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so that I
> can connect to the openmeetings server, why red5 wouldn't automatically
> start?
> 2.When I can connect to the server , I always waited so long time about 30
> minutes or sometimes it came up the message
> ------------------------------------------------------------
> ----------------------------------------
> *OpenMeetings - Loading ...*
> The server is not yet completely initialized. Please try again in a couple
> of seconds.
> If this message persists for several minutes contact your
> Sys-Administration.
> If that message stays forever you should check the logs located in
>
> openmeetings_install_dir/log
>
> folder, probably your database user/pwd/host is wrong!
> ------------------------------------------------------------
> ---------------------
> after 5 minutes I reconnect again , it can work well but it bothers me,
> every time when I restart my server. Therefore I want to know how to
> startup openmeetings manually like this log , it seems like my server start
> so slow I need to know how the Starting up context: openmeetings trigger.
>
> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up context:
> openmeetings
> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
> partition table arrangement...
> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
> enabled=true, running=false]
> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
> ############################################################
> ####################
> # Openmeetings is up
> #
> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
> 2017-10-30T13:43:35Z #
> # and ready to use
> #
> ############################################################
> ####################
>
>
>
>
--
WBR
Maxim aka solomax
Re: about openmeetings server start problem
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks a lot for sharing this!
Every day learn something new :)) (c)
On Wed, Nov 29, 2017 at 7:49 PM, Fang-Yuan Kuo <ku...@gmail.com> wrote:
> I found the solution for startup so long, I google about java secure
> random this is my solution:
>
> https://stackoverflow.com/questions/40383430/tomcat-
> takes-too-much-time-to-start-java-securerandom/40603084#40603084
>
> The article point out that there is not enough entropy for generate random
> number so we can use tool to solve this problem.
>
> https://www.digitalocean.com/community/tutorials/how-to-
> setup-additional-entropy-for-cloud-servers-using-haveged
>
> # apt-get install haveged
>
> #edit the configuration file located in /etc/default/haveged, ensuring the
> following options are set (usually already the default options):
>
> DAEMON_ARGS="-w 1024"
>
> # update-rc.d haveged defaults
>
> Now whenever I reboot , I just wait less than 1 minute.
>
> 2017-11-29 20:20 GMT+08:00 Fang-Yuan Kuo <ku...@gmail.com>:
>
>> 1. Thanks for help autostart the red5, it worked.
>> 2. I deployed another VM for OM with 4vCPU and 15GB RAM, first time
>> reboot, I wait 1 minute, second reboot I wait 10 minutes, third reboot more
>> than 5 minutes... that's so weird.
>> you are right, I found this log, SecureRandom sometimes takes a lot
>> of time. Is there anyway to fix that?
>> 2017-11-29 12:10:11,757 [0.0.0.0-startStop-1] INFO
>> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
>> detected on classpath
>> 2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN
>> o.a.c.util.SessionIdGeneratorBase - Creation of SecureRandom instance
>> for session ID generation using [SHA1PRNG] took [399,242] milliseconds.
>>
>> 2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN o.a.c.util.SessionIdGeneratorBase - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [399,242] milliseconds.
>>
>>
>> 2017-11-29 17:15 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>
>>> It is not enough to copy script to /etc/init.d
>>> You have to "register" it the system: `sudo update-rc.d
>>> _your_script_name_ defaults` this will add it to "autostart" on certain
>>> levels
>>>
>>> According to the long start:
>>> In case red5 has started and wasn't crashed OM will start.
>>> On our demo server OM starts in ~30second
>>> On my test server OM starts much longer sometimes, and as far as I can
>>> tell this happens because of long initialization of Java SecureRandom
>>>
>>> I would recommend to test on more powerful server in case if such test
>>> is not too expensive ....
>>>
>>> On Wed, Nov 29, 2017 at 4:03 PM, Fang-Yuan Kuo <ku...@gmail.com>
>>> wrote:
>>>
>>>> I build OM in the Google Cloud Platform ( 1vCPU 3.75RAM) OS is Ubuntu
>>>> 16.04
>>>> OK, let me clear the situation again. As first I follow the guide
>>>> install OM very well, the OM startup too.
>>>> When I reboot server, I can't connect the OM server, that means the
>>>> red5 didn't open the port, I have copied the red5-ubdeb2 in /etc/init.d/. I
>>>> don't know why red5 didn't autostart.
>>>> Next I type "sudo /etc/init.d/red5-ubdeb2 start", now the connection
>>>> established, but the openmeetings.log didn't show anything for starting the
>>>> OM.
>>>> Is it possible that my HW is not powerful enough? Does OM need a long
>>>> time(about 30min) to start?
>>>>
>>>> Here is part of my red5.log while I type "sudo /etc/init.d/red5-ubdeb2
>>>> start" in the meantime the openmeetings.log doesn't create anything.
>>>> .........omitted........
>>>> 2017-11-29 16:58:25,265 [main] INFO org.red5.server.Context - Setting
>>>> parent bean factory as core
>>>> 2017-11-29 16:58:25,417 [main] INFO org.red5.server.tomcat.TomcatLoader
>>>> - Loading Tomcat
>>>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>>>> - Server root: /opt/red540
>>>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>>>> - Config root: /opt/red540/conf
>>>> 2017-11-29 16:58:25,500 [main] INFO org.red5.server.tomcat.TomcatLoader
>>>> - Application root: /opt/red540/webapps
>>>> 2017-11-29 16:58:25,737 [main] INFO org.red5.server.tomcat.TomcatLoader
>>>> - Starting Tomcat servlet engine
>>>> 2017-11-29 16:58:25,964 [main] INFO o.a.c.core.AprLifecycleListener -
>>>> The APR based Apache Tomcat Native library which allows optimal performance
>>>> in production environments was not found on the java.library.path:
>>>> [/opt/red540/lib/native]
>>>> 2017-11-29 16:58:25,977 [main] INFO o.a.coyote.http11.Http11NioProtocol
>>>> - Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
>>>> 2017-11-29 16:58:25,997 [main] INFO o.a.tomcat.util.net.NioSelectorPool
>>>> - Using a shared selector for servlet write/read
>>>> 2017-11-29 16:58:26,020 [main] INFO o.a.catalina.core.StandardService
>>>> - Starting service [Tomcat]
>>>> 2017-11-29 16:58:26,022 [main] INFO o.a.catalina.core.StandardEngine
>>>> - Starting Servlet Engine: Apache Tomcat/8.5.23
>>>> 2017-11-29 16:58:26,158 [0.0.0.0-startStop-1] INFO
>>>> o.a.catalina.startup.ContextConfig - No global web.xml found
>>>> 2017-11-29 16:58:26,267 [0.0.0.0-startStop-1] INFO
>>>> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
>>>> detected on classpath
>>>>
>>>> 2017-11-29 16:30 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>>
>>>>> OM is build on top of red5
>>>>> so if red5 has started OM will also start
>>>>>
>>>>> what is you HW? CPU/RAM?
>>>>>
>>>>> On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I have checked the installation guides,as far as I concerned, the
>>>>>> "red5ubdeb2" is the script to startup the OM server, I have copied it to
>>>>>> the /etc/init.d/ according to the guides.
>>>>>> Things all changed once I reboot my server, I still need to wait long
>>>>>> to connect my OM server. Is the "red5ubdeb2" is just startup the red5 not
>>>>>> the OM? How to trigger the OM startup? Also I have checked mysql service it
>>>>>> worked well.
>>>>>>
>>>>>> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> please do not write personal emails, write to the user@ list
>>>>>>> http://openmeetings.apache.org/mail-lists.html (you need to
>>>>>>> subscribe first)
>>>>>>>
>>>>>>> According to your question: you need to create startup script for
>>>>>>> OM, please check installation guides: https://cwiki.apache.o
>>>>>>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>>>>>>> OpenMeetings+and+Tools
>>>>>>> And/or search through mailing list archives: http://openmeetings.
>>>>>>> markmail.org/
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>>>>>>
>>>>>>>> hi, Mr. Maxim Solodovnik
>>>>>>>>
>>>>>>>> I have installed the openmeetings and worked well,but when I reboot
>>>>>>>> my server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>>>>>>> came up.
>>>>>>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so
>>>>>>>> that I can connect to the openmeetings server, why red5 wouldn't
>>>>>>>> automatically start?
>>>>>>>> 2.When I can connect to the server , I always waited so long time
>>>>>>>> about 30 minutes or sometimes it came up the message
>>>>>>>> ------------------------------------------------------------
>>>>>>>> ----------------------------------------
>>>>>>>> *OpenMeetings - Loading ...*
>>>>>>>> The server is not yet completely initialized. Please try again in a
>>>>>>>> couple of seconds.
>>>>>>>> If this message persists for several minutes contact your
>>>>>>>> Sys-Administration.
>>>>>>>> If that message stays forever you should check the logs located in
>>>>>>>>
>>>>>>>> openmeetings_install_dir/log
>>>>>>>>
>>>>>>>> folder, probably your database user/pwd/host is wrong!
>>>>>>>> ------------------------------------------------------------
>>>>>>>> ---------------------
>>>>>>>> after 5 minutes I reconnect again , it can work well but it bothers
>>>>>>>> me, every time when I restart my server. Therefore I want to know how to
>>>>>>>> startup openmeetings manually like this log , it seems like my server start
>>>>>>>> so slow I need to know how the Starting up context: openmeetings
>>>>>>>> trigger.
>>>>>>>>
>>>>>>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>>>>>>> context: openmeetings
>>>>>>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>>>>>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>>>>>>> partition table arrangement...
>>>>>>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>>>>>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>>>>>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>>>>>>> enabled=true, running=false]
>>>>>>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>>>>>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>>>>>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>>>>>>> ##############################
>>>>>>>> ##################################################
>>>>>>>> # Openmeetings is up
>>>>>>>> #
>>>>>>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>>>>>>> 2017-10-30T13:43:35Z #
>>>>>>>> # and ready to use
>>>>>>>> #
>>>>>>>> ##############################
>>>>>>>> ##################################################
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> WBR
>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>
--
WBR
Maxim aka solomax
Re: about openmeetings server start problem
Posted by Fang-Yuan Kuo <ku...@gmail.com>.
I found the solution for startup so long, I google about java secure random
this is my solution:
https://stackoverflow.com/questions/40383430/tomcat-takes-too-much-time-to-start-java-securerandom/40603084#40603084
The article point out that there is not enough entropy for generate random
number so we can use tool to solve this problem.
https://www.digitalocean.com/community/tutorials/how-to-setup-additional-entropy-for-cloud-servers-using-haveged
# apt-get install haveged
#edit the configuration file located in /etc/default/haveged, ensuring the
following options are set (usually already the default options):
DAEMON_ARGS="-w 1024"
# update-rc.d haveged defaults
Now whenever I reboot , I just wait less than 1 minute.
2017-11-29 20:20 GMT+08:00 Fang-Yuan Kuo <ku...@gmail.com>:
> 1. Thanks for help autostart the red5, it worked.
> 2. I deployed another VM for OM with 4vCPU and 15GB RAM, first time
> reboot, I wait 1 minute, second reboot I wait 10 minutes, third reboot more
> than 5 minutes... that's so weird.
> you are right, I found this log, SecureRandom sometimes takes a lot of
> time. Is there anyway to fix that?
> 2017-11-29 12:10:11,757 [0.0.0.0-startStop-1] INFO
> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
> detected on classpath
> 2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN o.a.c.util.SessionIdGeneratorBase
> - Creation of SecureRandom instance for session ID generation using
> [SHA1PRNG] took [399,242] milliseconds.
>
> 2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN o.a.c.util.SessionIdGeneratorBase - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [399,242] milliseconds.
>
>
> 2017-11-29 17:15 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>
>> It is not enough to copy script to /etc/init.d
>> You have to "register" it the system: `sudo update-rc.d
>> _your_script_name_ defaults` this will add it to "autostart" on certain
>> levels
>>
>> According to the long start:
>> In case red5 has started and wasn't crashed OM will start.
>> On our demo server OM starts in ~30second
>> On my test server OM starts much longer sometimes, and as far as I can
>> tell this happens because of long initialization of Java SecureRandom
>>
>> I would recommend to test on more powerful server in case if such test is
>> not too expensive ....
>>
>> On Wed, Nov 29, 2017 at 4:03 PM, Fang-Yuan Kuo <ku...@gmail.com>
>> wrote:
>>
>>> I build OM in the Google Cloud Platform ( 1vCPU 3.75RAM) OS is Ubuntu
>>> 16.04
>>> OK, let me clear the situation again. As first I follow the guide
>>> install OM very well, the OM startup too.
>>> When I reboot server, I can't connect the OM server, that means the red5
>>> didn't open the port, I have copied the red5-ubdeb2 in /etc/init.d/. I
>>> don't know why red5 didn't autostart.
>>> Next I type "sudo /etc/init.d/red5-ubdeb2 start", now the connection
>>> established, but the openmeetings.log didn't show anything for starting the
>>> OM.
>>> Is it possible that my HW is not powerful enough? Does OM need a long
>>> time(about 30min) to start?
>>>
>>> Here is part of my red5.log while I type "sudo /etc/init.d/red5-ubdeb2
>>> start" in the meantime the openmeetings.log doesn't create anything.
>>> .........omitted........
>>> 2017-11-29 16:58:25,265 [main] INFO org.red5.server.Context - Setting
>>> parent bean factory as core
>>> 2017-11-29 16:58:25,417 [main] INFO org.red5.server.tomcat.TomcatLoader
>>> - Loading Tomcat
>>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>>> - Server root: /opt/red540
>>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>>> - Config root: /opt/red540/conf
>>> 2017-11-29 16:58:25,500 [main] INFO org.red5.server.tomcat.TomcatLoader
>>> - Application root: /opt/red540/webapps
>>> 2017-11-29 16:58:25,737 [main] INFO org.red5.server.tomcat.TomcatLoader
>>> - Starting Tomcat servlet engine
>>> 2017-11-29 16:58:25,964 [main] INFO o.a.c.core.AprLifecycleListener -
>>> The APR based Apache Tomcat Native library which allows optimal performance
>>> in production environments was not found on the java.library.path:
>>> [/opt/red540/lib/native]
>>> 2017-11-29 16:58:25,977 [main] INFO o.a.coyote.http11.Http11NioProtocol
>>> - Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
>>> 2017-11-29 16:58:25,997 [main] INFO o.a.tomcat.util.net.NioSelectorPool
>>> - Using a shared selector for servlet write/read
>>> 2017-11-29 16:58:26,020 [main] INFO o.a.catalina.core.StandardService
>>> - Starting service [Tomcat]
>>> 2017-11-29 16:58:26,022 [main] INFO o.a.catalina.core.StandardEngine -
>>> Starting Servlet Engine: Apache Tomcat/8.5.23
>>> 2017-11-29 16:58:26,158 [0.0.0.0-startStop-1] INFO
>>> o.a.catalina.startup.ContextConfig - No global web.xml found
>>> 2017-11-29 16:58:26,267 [0.0.0.0-startStop-1] INFO
>>> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
>>> detected on classpath
>>>
>>> 2017-11-29 16:30 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>
>>>> OM is build on top of red5
>>>> so if red5 has started OM will also start
>>>>
>>>> what is you HW? CPU/RAM?
>>>>
>>>> On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com>
>>>> wrote:
>>>>
>>>>> I have checked the installation guides,as far as I concerned, the
>>>>> "red5ubdeb2" is the script to startup the OM server, I have copied it to
>>>>> the /etc/init.d/ according to the guides.
>>>>> Things all changed once I reboot my server, I still need to wait long
>>>>> to connect my OM server. Is the "red5ubdeb2" is just startup the red5 not
>>>>> the OM? How to trigger the OM startup? Also I have checked mysql service it
>>>>> worked well.
>>>>>
>>>>> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> please do not write personal emails, write to the user@ list
>>>>>> http://openmeetings.apache.org/mail-lists.html (you need to
>>>>>> subscribe first)
>>>>>>
>>>>>> According to your question: you need to create startup script for OM,
>>>>>> please check installation guides: https://cwiki.apache.o
>>>>>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>>>>>> OpenMeetings+and+Tools
>>>>>> And/or search through mailing list archives: http://openmeetings.
>>>>>> markmail.org/
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>>>>>
>>>>>>> hi, Mr. Maxim Solodovnik
>>>>>>>
>>>>>>> I have installed the openmeetings and worked well,but when I reboot
>>>>>>> my server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>>>>>> came up.
>>>>>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so
>>>>>>> that I can connect to the openmeetings server, why red5 wouldn't
>>>>>>> automatically start?
>>>>>>> 2.When I can connect to the server , I always waited so long time
>>>>>>> about 30 minutes or sometimes it came up the message
>>>>>>> ------------------------------------------------------------
>>>>>>> ----------------------------------------
>>>>>>> *OpenMeetings - Loading ...*
>>>>>>> The server is not yet completely initialized. Please try again in a
>>>>>>> couple of seconds.
>>>>>>> If this message persists for several minutes contact your
>>>>>>> Sys-Administration.
>>>>>>> If that message stays forever you should check the logs located in
>>>>>>>
>>>>>>> openmeetings_install_dir/log
>>>>>>>
>>>>>>> folder, probably your database user/pwd/host is wrong!
>>>>>>> ------------------------------------------------------------
>>>>>>> ---------------------
>>>>>>> after 5 minutes I reconnect again , it can work well but it bothers
>>>>>>> me, every time when I restart my server. Therefore I want to know how to
>>>>>>> startup openmeetings manually like this log , it seems like my server start
>>>>>>> so slow I need to know how the Starting up context: openmeetings
>>>>>>> trigger.
>>>>>>>
>>>>>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>>>>>> context: openmeetings
>>>>>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>>>>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>>>>>> partition table arrangement...
>>>>>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>>>>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>>>>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>>>>>> enabled=true, running=false]
>>>>>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>>>>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>>>>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>>>>>> ############################################################
>>>>>>> ####################
>>>>>>> # Openmeetings is up
>>>>>>> #
>>>>>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>>>>>> 2017-10-30T13:43:35Z #
>>>>>>> # and ready to use
>>>>>>> #
>>>>>>> ############################################################
>>>>>>> ####################
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
Re: about openmeetings server start problem
Posted by Fang-Yuan Kuo <ku...@gmail.com>.
1. Thanks for help autostart the red5, it worked.
2. I deployed another VM for OM with 4vCPU and 15GB RAM, first time reboot,
I wait 1 minute, second reboot I wait 10 minutes, third reboot more than 5
minutes... that's so weird.
you are right, I found this log, SecureRandom sometimes takes a lot of
time. Is there anyway to fix that?
2017-11-29 12:10:11,757 [0.0.0.0-startStop-1] INFO
o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
detected on classpath
2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN
o.a.c.util.SessionIdGeneratorBase - Creation of SecureRandom instance for
session ID generation using [SHA1PRNG] took [399,242] milliseconds.
2017-11-29 12:16:51,046 [0.0.0.0-startStop-1] WARN
o.a.c.util.SessionIdGeneratorBase - Creation of SecureRandom instance
for session ID generation using [SHA1PRNG] took [399,242]
milliseconds.
2017-11-29 17:15 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
> It is not enough to copy script to /etc/init.d
> You have to "register" it the system: `sudo update-rc.d
> _your_script_name_ defaults` this will add it to "autostart" on certain
> levels
>
> According to the long start:
> In case red5 has started and wasn't crashed OM will start.
> On our demo server OM starts in ~30second
> On my test server OM starts much longer sometimes, and as far as I can
> tell this happens because of long initialization of Java SecureRandom
>
> I would recommend to test on more powerful server in case if such test is
> not too expensive ....
>
> On Wed, Nov 29, 2017 at 4:03 PM, Fang-Yuan Kuo <ku...@gmail.com>
> wrote:
>
>> I build OM in the Google Cloud Platform ( 1vCPU 3.75RAM) OS is Ubuntu
>> 16.04
>> OK, let me clear the situation again. As first I follow the guide install
>> OM very well, the OM startup too.
>> When I reboot server, I can't connect the OM server, that means the red5
>> didn't open the port, I have copied the red5-ubdeb2 in /etc/init.d/. I
>> don't know why red5 didn't autostart.
>> Next I type "sudo /etc/init.d/red5-ubdeb2 start", now the connection
>> established, but the openmeetings.log didn't show anything for starting the
>> OM.
>> Is it possible that my HW is not powerful enough? Does OM need a long
>> time(about 30min) to start?
>>
>> Here is part of my red5.log while I type "sudo /etc/init.d/red5-ubdeb2
>> start" in the meantime the openmeetings.log doesn't create anything.
>> .........omitted........
>> 2017-11-29 16:58:25,265 [main] INFO org.red5.server.Context - Setting
>> parent bean factory as core
>> 2017-11-29 16:58:25,417 [main] INFO org.red5.server.tomcat.TomcatLoader
>> - Loading Tomcat
>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>> - Server root: /opt/red540
>> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
>> - Config root: /opt/red540/conf
>> 2017-11-29 16:58:25,500 [main] INFO org.red5.server.tomcat.TomcatLoader
>> - Application root: /opt/red540/webapps
>> 2017-11-29 16:58:25,737 [main] INFO org.red5.server.tomcat.TomcatLoader
>> - Starting Tomcat servlet engine
>> 2017-11-29 16:58:25,964 [main] INFO o.a.c.core.AprLifecycleListener -
>> The APR based Apache Tomcat Native library which allows optimal performance
>> in production environments was not found on the java.library.path:
>> [/opt/red540/lib/native]
>> 2017-11-29 16:58:25,977 [main] INFO o.a.coyote.http11.Http11NioProtocol
>> - Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
>> 2017-11-29 16:58:25,997 [main] INFO o.a.tomcat.util.net.NioSelectorPool
>> - Using a shared selector for servlet write/read
>> 2017-11-29 16:58:26,020 [main] INFO o.a.catalina.core.StandardService -
>> Starting service [Tomcat]
>> 2017-11-29 16:58:26,022 [main] INFO o.a.catalina.core.StandardEngine -
>> Starting Servlet Engine: Apache Tomcat/8.5.23
>> 2017-11-29 16:58:26,158 [0.0.0.0-startStop-1] INFO
>> o.a.catalina.startup.ContextConfig - No global web.xml found
>> 2017-11-29 16:58:26,267 [0.0.0.0-startStop-1] INFO
>> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
>> detected on classpath
>>
>> 2017-11-29 16:30 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>
>>> OM is build on top of red5
>>> so if red5 has started OM will also start
>>>
>>> what is you HW? CPU/RAM?
>>>
>>> On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com>
>>> wrote:
>>>
>>>> I have checked the installation guides,as far as I concerned, the
>>>> "red5ubdeb2" is the script to startup the OM server, I have copied it to
>>>> the /etc/init.d/ according to the guides.
>>>> Things all changed once I reboot my server, I still need to wait long
>>>> to connect my OM server. Is the "red5ubdeb2" is just startup the red5 not
>>>> the OM? How to trigger the OM startup? Also I have checked mysql service it
>>>> worked well.
>>>>
>>>> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>>
>>>>> Hello,
>>>>>
>>>>> please do not write personal emails, write to the user@ list
>>>>> http://openmeetings.apache.org/mail-lists.html (you need to subscribe
>>>>> first)
>>>>>
>>>>> According to your question: you need to create startup script for OM,
>>>>> please check installation guides: https://cwiki.apache.o
>>>>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>>>>> OpenMeetings+and+Tools
>>>>> And/or search through mailing list archives: http://openmeetings.
>>>>> markmail.org/
>>>>>
>>>>>
>>>>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>>>>
>>>>>> hi, Mr. Maxim Solodovnik
>>>>>>
>>>>>> I have installed the openmeetings and worked well,but when I reboot
>>>>>> my server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>>>>> came up.
>>>>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so
>>>>>> that I can connect to the openmeetings server, why red5 wouldn't
>>>>>> automatically start?
>>>>>> 2.When I can connect to the server , I always waited so long time
>>>>>> about 30 minutes or sometimes it came up the message
>>>>>> ------------------------------------------------------------
>>>>>> ----------------------------------------
>>>>>> *OpenMeetings - Loading ...*
>>>>>> The server is not yet completely initialized. Please try again in a
>>>>>> couple of seconds.
>>>>>> If this message persists for several minutes contact your
>>>>>> Sys-Administration.
>>>>>> If that message stays forever you should check the logs located in
>>>>>>
>>>>>> openmeetings_install_dir/log
>>>>>>
>>>>>> folder, probably your database user/pwd/host is wrong!
>>>>>> ------------------------------------------------------------
>>>>>> ---------------------
>>>>>> after 5 minutes I reconnect again , it can work well but it bothers
>>>>>> me, every time when I restart my server. Therefore I want to know how to
>>>>>> startup openmeetings manually like this log , it seems like my server start
>>>>>> so slow I need to know how the Starting up context: openmeetings
>>>>>> trigger.
>>>>>>
>>>>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>>>>> context: openmeetings
>>>>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>>>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>>>>> partition table arrangement...
>>>>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>>>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>>>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>>>>> enabled=true, running=false]
>>>>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>>>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>>>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>>>>> ############################################################
>>>>>> ####################
>>>>>> # Openmeetings is up
>>>>>> #
>>>>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>>>>> 2017-10-30T13:43:35Z #
>>>>>> # and ready to use
>>>>>> #
>>>>>> ############################################################
>>>>>> ####################
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
Re: about openmeetings server start problem
Posted by Maxim Solodovnik <so...@gmail.com>.
It is not enough to copy script to /etc/init.d
You have to "register" it the system: `sudo update-rc.d _your_script_name_
defaults` this will add it to "autostart" on certain levels
According to the long start:
In case red5 has started and wasn't crashed OM will start.
On our demo server OM starts in ~30second
On my test server OM starts much longer sometimes, and as far as I can tell
this happens because of long initialization of Java SecureRandom
I would recommend to test on more powerful server in case if such test is
not too expensive ....
On Wed, Nov 29, 2017 at 4:03 PM, Fang-Yuan Kuo <ku...@gmail.com> wrote:
> I build OM in the Google Cloud Platform ( 1vCPU 3.75RAM) OS is Ubuntu 16.04
> OK, let me clear the situation again. As first I follow the guide install
> OM very well, the OM startup too.
> When I reboot server, I can't connect the OM server, that means the red5
> didn't open the port, I have copied the red5-ubdeb2 in /etc/init.d/. I
> don't know why red5 didn't autostart.
> Next I type "sudo /etc/init.d/red5-ubdeb2 start", now the connection
> established, but the openmeetings.log didn't show anything for starting the
> OM.
> Is it possible that my HW is not powerful enough? Does OM need a long
> time(about 30min) to start?
>
> Here is part of my red5.log while I type "sudo /etc/init.d/red5-ubdeb2
> start" in the meantime the openmeetings.log doesn't create anything.
> .........omitted........
> 2017-11-29 16:58:25,265 [main] INFO org.red5.server.Context - Setting
> parent bean factory as core
> 2017-11-29 16:58:25,417 [main] INFO org.red5.server.tomcat.TomcatLoader
> - Loading Tomcat
> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
> - Server root: /opt/red540
> 2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader
> - Config root: /opt/red540/conf
> 2017-11-29 16:58:25,500 [main] INFO org.red5.server.tomcat.TomcatLoader
> - Application root: /opt/red540/webapps
> 2017-11-29 16:58:25,737 [main] INFO org.red5.server.tomcat.TomcatLoader
> - Starting Tomcat servlet engine
> 2017-11-29 16:58:25,964 [main] INFO o.a.c.core.AprLifecycleListener -
> The APR based Apache Tomcat Native library which allows optimal performance
> in production environments was not found on the java.library.path:
> [/opt/red540/lib/native]
> 2017-11-29 16:58:25,977 [main] INFO o.a.coyote.http11.Http11NioProtocol
> - Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
> 2017-11-29 16:58:25,997 [main] INFO o.a.tomcat.util.net.NioSelectorPool
> - Using a shared selector for servlet write/read
> 2017-11-29 16:58:26,020 [main] INFO o.a.catalina.core.StandardService -
> Starting service [Tomcat]
> 2017-11-29 16:58:26,022 [main] INFO o.a.catalina.core.StandardEngine -
> Starting Servlet Engine: Apache Tomcat/8.5.23
> 2017-11-29 16:58:26,158 [0.0.0.0-startStop-1] INFO o.a.catalina.startup.ContextConfig
> - No global web.xml found
> 2017-11-29 16:58:26,267 [0.0.0.0-startStop-1] INFO
> o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
> detected on classpath
>
> 2017-11-29 16:30 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>
>> OM is build on top of red5
>> so if red5 has started OM will also start
>>
>> what is you HW? CPU/RAM?
>>
>> On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com>
>> wrote:
>>
>>> I have checked the installation guides,as far as I concerned, the
>>> "red5ubdeb2" is the script to startup the OM server, I have copied it to
>>> the /etc/init.d/ according to the guides.
>>> Things all changed once I reboot my server, I still need to wait long to
>>> connect my OM server. Is the "red5ubdeb2" is just startup the red5 not the
>>> OM? How to trigger the OM startup? Also I have checked mysql service it
>>> worked well.
>>>
>>> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>>
>>>> Hello,
>>>>
>>>> please do not write personal emails, write to the user@ list
>>>> http://openmeetings.apache.org/mail-lists.html (you need to subscribe
>>>> first)
>>>>
>>>> According to your question: you need to create startup script for OM,
>>>> please check installation guides: https://cwiki.apache.o
>>>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>>>> OpenMeetings+and+Tools
>>>> And/or search through mailing list archives: http://openmeetings.
>>>> markmail.org/
>>>>
>>>>
>>>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>>>
>>>>> hi, Mr. Maxim Solodovnik
>>>>>
>>>>> I have installed the openmeetings and worked well,but when I reboot my
>>>>> server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>>>> came up.
>>>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so that
>>>>> I can connect to the openmeetings server, why red5 wouldn't automatically
>>>>> start?
>>>>> 2.When I can connect to the server , I always waited so long time
>>>>> about 30 minutes or sometimes it came up the message
>>>>> ------------------------------------------------------------
>>>>> ----------------------------------------
>>>>> *OpenMeetings - Loading ...*
>>>>> The server is not yet completely initialized. Please try again in a
>>>>> couple of seconds.
>>>>> If this message persists for several minutes contact your
>>>>> Sys-Administration.
>>>>> If that message stays forever you should check the logs located in
>>>>>
>>>>> openmeetings_install_dir/log
>>>>>
>>>>> folder, probably your database user/pwd/host is wrong!
>>>>> ------------------------------------------------------------
>>>>> ---------------------
>>>>> after 5 minutes I reconnect again , it can work well but it bothers
>>>>> me, every time when I restart my server. Therefore I want to know how to
>>>>> startup openmeetings manually like this log , it seems like my server start
>>>>> so slow I need to know how the Starting up context: openmeetings
>>>>> trigger.
>>>>>
>>>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>>>> context: openmeetings
>>>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>>>> partition table arrangement...
>>>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>>>> enabled=true, running=false]
>>>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>>>> ############################################################
>>>>> ####################
>>>>> # Openmeetings is up
>>>>> #
>>>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>>>> 2017-10-30T13:43:35Z #
>>>>> # and ready to use
>>>>> #
>>>>> ############################################################
>>>>> ####################
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
--
WBR
Maxim aka solomax
Re: about openmeetings server start problem
Posted by Fang-Yuan Kuo <ku...@gmail.com>.
I build OM in the Google Cloud Platform ( 1vCPU 3.75RAM) OS is Ubuntu 16.04
OK, let me clear the situation again. As first I follow the guide install
OM very well, the OM startup too.
When I reboot server, I can't connect the OM server, that means the red5
didn't open the port, I have copied the red5-ubdeb2 in /etc/init.d/. I
don't know why red5 didn't autostart.
Next I type "sudo /etc/init.d/red5-ubdeb2 start", now the connection
established, but the openmeetings.log didn't show anything for starting the
OM.
Is it possible that my HW is not powerful enough? Does OM need a long
time(about 30min) to start?
Here is part of my red5.log while I type "sudo /etc/init.d/red5-ubdeb2
start" in the meantime the openmeetings.log doesn't create anything.
.........omitted........
2017-11-29 16:58:25,265 [main] INFO org.red5.server.Context - Setting
parent bean factory as core
2017-11-29 16:58:25,417 [main] INFO org.red5.server.tomcat.TomcatLoader -
Loading Tomcat
2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader -
Server root: /opt/red540
2017-11-29 16:58:25,419 [main] INFO org.red5.server.tomcat.TomcatLoader -
Config root: /opt/red540/conf
2017-11-29 16:58:25,500 [main] INFO org.red5.server.tomcat.TomcatLoader -
Application root: /opt/red540/webapps
2017-11-29 16:58:25,737 [main] INFO org.red5.server.tomcat.TomcatLoader -
Starting Tomcat servlet engine
2017-11-29 16:58:25,964 [main] INFO o.a.c.core.AprLifecycleListener - The
APR based Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path:
[/opt/red540/lib/native]
2017-11-29 16:58:25,977 [main] INFO o.a.coyote.http11.Http11NioProtocol -
Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
2017-11-29 16:58:25,997 [main] INFO o.a.tomcat.util.net.NioSelectorPool -
Using a shared selector for servlet write/read
2017-11-29 16:58:26,020 [main] INFO o.a.catalina.core.StandardService -
Starting service [Tomcat]
2017-11-29 16:58:26,022 [main] INFO o.a.catalina.core.StandardEngine -
Starting Servlet Engine: Apache Tomcat/8.5.23
2017-11-29 16:58:26,158 [0.0.0.0-startStop-1] INFO
o.a.catalina.startup.ContextConfig - No global web.xml found
2017-11-29 16:58:26,267 [0.0.0.0-startStop-1] INFO
o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types
detected on classpath
2017-11-29 16:30 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
> OM is build on top of red5
> so if red5 has started OM will also start
>
> what is you HW? CPU/RAM?
>
> On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com>
> wrote:
>
>> I have checked the installation guides,as far as I concerned, the
>> "red5ubdeb2" is the script to startup the OM server, I have copied it to
>> the /etc/init.d/ according to the guides.
>> Things all changed once I reboot my server, I still need to wait long to
>> connect my OM server. Is the "red5ubdeb2" is just startup the red5 not the
>> OM? How to trigger the OM startup? Also I have checked mysql service it
>> worked well.
>>
>> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>>
>>> Hello,
>>>
>>> please do not write personal emails, write to the user@ list
>>> http://openmeetings.apache.org/mail-lists.html (you need to subscribe
>>> first)
>>>
>>> According to your question: you need to create startup script for OM,
>>> please check installation guides: https://cwiki.apache.o
>>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>>> OpenMeetings+and+Tools
>>> And/or search through mailing list archives: http://openmeetings.
>>> markmail.org/
>>>
>>>
>>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>>
>>>> hi, Mr. Maxim Solodovnik
>>>>
>>>> I have installed the openmeetings and worked well,but when I reboot my
>>>> server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>>> came up.
>>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so that
>>>> I can connect to the openmeetings server, why red5 wouldn't automatically
>>>> start?
>>>> 2.When I can connect to the server , I always waited so long time about
>>>> 30 minutes or sometimes it came up the message
>>>> ------------------------------------------------------------
>>>> ----------------------------------------
>>>> *OpenMeetings - Loading ...*
>>>> The server is not yet completely initialized. Please try again in a
>>>> couple of seconds.
>>>> If this message persists for several minutes contact your
>>>> Sys-Administration.
>>>> If that message stays forever you should check the logs located in
>>>>
>>>> openmeetings_install_dir/log
>>>>
>>>> folder, probably your database user/pwd/host is wrong!
>>>> ------------------------------------------------------------
>>>> ---------------------
>>>> after 5 minutes I reconnect again , it can work well but it bothers me,
>>>> every time when I restart my server. Therefore I want to know how to
>>>> startup openmeetings manually like this log , it seems like my server start
>>>> so slow I need to know how the Starting up context: openmeetings
>>>> trigger.
>>>>
>>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>>> context: openmeetings
>>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>>> partition table arrangement...
>>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>>> enabled=true, running=false]
>>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>>> ############################################################
>>>> ####################
>>>> # Openmeetings is up
>>>> #
>>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>>> 2017-10-30T13:43:35Z #
>>>> # and ready to use
>>>> #
>>>> ############################################################
>>>> ####################
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
Re: about openmeetings server start problem
Posted by Maxim Solodovnik <so...@gmail.com>.
OM is build on top of red5
so if red5 has started OM will also start
what is you HW? CPU/RAM?
On Wed, Nov 29, 2017 at 3:00 PM, Fang-Yuan Kuo <ku...@gmail.com> wrote:
> I have checked the installation guides,as far as I concerned, the
> "red5ubdeb2" is the script to startup the OM server, I have copied it to
> the /etc/init.d/ according to the guides.
> Things all changed once I reboot my server, I still need to wait long to
> connect my OM server. Is the "red5ubdeb2" is just startup the red5 not the
> OM? How to trigger the OM startup? Also I have checked mysql service it
> worked well.
>
> 2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
>
>> Hello,
>>
>> please do not write personal emails, write to the user@ list
>> http://openmeetings.apache.org/mail-lists.html (you need to subscribe
>> first)
>>
>> According to your question: you need to create startup script for OM,
>> please check installation guides: https://cwiki.apache.o
>> rg/confluence/display/OPENMEETINGS/Tutorials+for+installing+
>> OpenMeetings+and+Tools
>> And/or search through mailing list archives: http://openmeetings.
>> markmail.org/
>>
>>
>> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>>
>>> hi, Mr. Maxim Solodovnik
>>>
>>> I have installed the openmeetings and worked well,but when I reboot my
>>> server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>>> came up.
>>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so that I
>>> can connect to the openmeetings server, why red5 wouldn't automatically
>>> start?
>>> 2.When I can connect to the server , I always waited so long time about
>>> 30 minutes or sometimes it came up the message
>>> ------------------------------------------------------------
>>> ----------------------------------------
>>> *OpenMeetings - Loading ...*
>>> The server is not yet completely initialized. Please try again in a
>>> couple of seconds.
>>> If this message persists for several minutes contact your
>>> Sys-Administration.
>>> If that message stays forever you should check the logs located in
>>>
>>> openmeetings_install_dir/log
>>>
>>> folder, probably your database user/pwd/host is wrong!
>>> ------------------------------------------------------------
>>> ---------------------
>>> after 5 minutes I reconnect again , it can work well but it bothers me,
>>> every time when I restart my server. Therefore I want to know how to
>>> startup openmeetings manually like this log , it seems like my server start
>>> so slow I need to know how the Starting up context: openmeetings
>>> trigger.
>>>
>>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up
>>> context: openmeetings
>>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>>> partition table arrangement...
>>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>>> enabled=true, running=false]
>>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>>> ############################################################
>>> ####################
>>> # Openmeetings is up
>>> #
>>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>>> 2017-10-30T13:43:35Z #
>>> # and ready to use
>>> #
>>> ############################################################
>>> ####################
>>>
>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
--
WBR
Maxim aka solomax
Re: about openmeetings server start problem
Posted by Fang-Yuan Kuo <ku...@gmail.com>.
I have checked the installation guides,as far as I concerned, the
"red5ubdeb2" is the script to startup the OM server, I have copied it to
the /etc/init.d/ according to the guides.
Things all changed once I reboot my server, I still need to wait long to
connect my OM server. Is the "red5ubdeb2" is just startup the red5 not the
OM? How to trigger the OM startup? Also I have checked mysql service it
worked well.
2017-11-29 14:07 GMT+08:00 Maxim Solodovnik <so...@gmail.com>:
> Hello,
>
> please do not write personal emails, write to the user@ list
> http://openmeetings.apache.org/mail-lists.html (you need to subscribe
> first)
>
> According to your question: you need to create startup script for OM,
> please check installation guides: https://cwiki.apache.
> org/confluence/display/OPENMEETINGS/Tutorials+for+
> installing+OpenMeetings+and+Tools
> And/or search through mailing list archives: http://openmeetings.
> markmail.org/
>
>
> On Wed, Nov 29, 2017 at 10:49 AM, 郭芳元 <ku...@gmail.com> wrote:
>
>> hi, Mr. Maxim Solodovnik
>>
>> I have installed the openmeetings and worked well,but when I reboot my
>> server(Ubuntu 16.04 in Google Cloud platform vm) there are two problems
>> came up.
>> 1. I need to restart the "/etc/init.d/red5-ubdeb2 start" again so that I
>> can connect to the openmeetings server, why red5 wouldn't automatically
>> start?
>> 2.When I can connect to the server , I always waited so long time about
>> 30 minutes or sometimes it came up the message
>> ------------------------------------------------------------
>> ----------------------------------------
>> *OpenMeetings - Loading ...*
>> The server is not yet completely initialized. Please try again in a
>> couple of seconds.
>> If this message persists for several minutes contact your
>> Sys-Administration.
>> If that message stays forever you should check the logs located in
>>
>> openmeetings_install_dir/log
>>
>> folder, probably your database user/pwd/host is wrong!
>> ------------------------------------------------------------
>> ---------------------
>> after 5 minutes I reconnect again , it can work well but it bothers me,
>> every time when I restart my server. Therefore I want to know how to
>> startup openmeetings manually like this log , it seems like my server start
>> so slow I need to know how the Starting up context: openmeetings trigger.
>>
>> INFO 11-29 11:27:04.128 ROOT:81 [0.0-startStop-1] - Starting up context:
>> openmeetings
>> INFO 11-29 11:27:14.581 c.h.i.p.i.PartitionStateManager:49
>> [.0-5080-exec-10] - [10.140.0.3]:5701 [dev] [3.8.6] Initializing cluster
>> partition table arrangement...
>> DEBUG 11-29 11:27:17.559 o.a.o.c.r.ScopeApplicationAdapter:343
>> [r:/openmeetings] - start: Scope [name=openmeetings, path=/default,
>> type=APPLICATION, autoStart=true, creationTime=1511926036405, depth=1,
>> enabled=true, running=false]
>> DEBUG 11-29 11:27:17.630 o.a.o.c.r.ScopeApplicationAdapter:124
>> [r:/openmeetings] - webAppPath : /opt/red540/webapps/openmeetings
>> DEBUG 11-29 11:27:19.985 o.a.o.u.Version:82 [r:/openmeetings] -
>> ############################################################
>> ####################
>> # Openmeetings is up
>> #
>> # 4.0.0 23b20a3cfa3fa7a47003e56665597da5963aa631
>> 2017-10-30T13:43:35Z #
>> # and ready to use
>> #
>> ############################################################
>> ####################
>>
>>
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>