Yeah but when I go to http://<my-ip-address>:5080/openmeetings I get an
ERR_CONNECTION_TIMED_OUT message.


On Fri, Jul 20, 2018 at 4:11 AM, Maxim Solodovnik <[email protected]>
wrote:

> According to this output OM is started and ready to use
> On Fri, Jul 20, 2018 at 2:54 PM Alex Nyamweya <[email protected]>
> wrote:
> >
> > So I installed a new control panel on my server (ISPmanager) and now I
> can't connect to openmeetings. Here is the last bit of the output when I
> run the script /etc/init.d/red5-2 start.
> >
> > ############################################################
> ####################
> >         #                              Openmeetings is up
>               #
> >         #                      4.0.4 f1f4246 2018-05-23T02:52:39Z
>               #
> >         #                               and ready to use
>                #
> >         ############################################################
> ####################
> >
> > [INFO] [Loader:/openmeetings] org.quartz.impl.StdSchedulerFactory -
> Using default implementation for ThreadExecutor
> > [INFO] [Loader:/openmeetings] org.quartz.core.SchedulerSignalerImpl -
> Initialized Scheduler Signaller of type: class org.quartz.core.
> SchedulerSignalerImpl
> > [INFO] [Loader:/openmeetings] org.quartz.core.QuartzScheduler - Quartz
> Scheduler v.2.3.0 created.
> > [INFO] [Loader:/openmeetings] org.quartz.simpl.RAMJobStore - RAMJobStore
> initialized.
> > [INFO] [Loader:/openmeetings] org.quartz.core.QuartzScheduler -
> Scheduler meta-data: Quartz Scheduler (v2.3.0) 'org.springframework.
> scheduling.quartz.SchedulerFactoryBean#0' with instanceId 'NON_CLUSTERED'
> >   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
> >   NOT STARTED.
> >   Currently in standby mode.
> >   Number of jobs executed: 0
> >   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
> threads.
> >   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
> support persistence. and is not clustered.
> >
> > [INFO] [Loader:/openmeetings] org.quartz.impl.StdSchedulerFactory -
> Quartz scheduler 
> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
> initialized from an externally provided properties instance.
> > [INFO] [Loader:/openmeetings] org.quartz.impl.StdSchedulerFactory -
> Quartz scheduler version: 2.3.0
> > [INFO] [Loader:/openmeetings] org.quartz.core.QuartzScheduler -
> JobFactory set to: org.springframework.scheduling.quartz.
> AdaptableJobFactory@4d788a85
> > [INFO] [Loader:/openmeetings] 
> > org.springframework.context.support.DefaultLifecycleProcessor
> - Starting beans in phase 2147483647
> > [INFO] [Loader:/openmeetings] org.quartz.core.QuartzScheduler -
> Scheduler org.springframework.scheduling.quartz.
> SchedulerFactoryBean#0_$_NON_CLUSTERED started.
> > [INFO] [Loader:/openmeetings] 
> > org.springframework.context.support.DefaultLifecycleProcessor
> - Starting beans in phase 2147483647
> > DEBUG 07-20 03:44:33.918 o.a.o.s.q.s.ReminderJob:92 [Bean#0_Worker-7] -
> Rss disabled by Admin
> >
>
>
> --
> WBR
> Maxim aka solomax
>

Reply via email to