Page 1 of 1

LogicalDoc Initial Startup fails when QuartzScheduler runs

Posted: Mon Sep 24, 2018 7:44 pm
by judeochalifu
I recently installed LogicalDoc on a new server (Linux Centos 7) but have been unable to start it.

Connection times out everytime. When I restart logicaldoc-all.service, it begins startup jobs but times out.

I tailed dms.log and found that it stops whenever it gets to this:

Code: Select all

24.09.2018 14:17:24,273 INFO   (org.quartz.core.QuartzScheduler: 305) -- Scheduler meta-data: Quartz Scheduler (v2.2.1) 'Scheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  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.

24.09.2018 14:17:24,274 INFO   (org.quartz.impl.StdSchedulerFactory:1339) -- Quartz scheduler 'Scheduler' initialized from an externally provided properties instance.
24.09.2018 14:17:24,274 INFO   (org.quartz.impl.StdSchedulerFactory:1343) -- Quartz scheduler version: 2.2.1
24.09.2018 14:17:24,277 INFO   (org.quartz.core.QuartzScheduler:2311) -- JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@8d9663d
24.09.2018 14:17:24,300 INFO   (com.logicaldoc.core.task.SchedulerFactoryBean: 645) -- Starting Quartz Scheduler now
24.09.2018 14:17:24,301 INFO   (org.quartz.core.QuartzScheduler: 575) -- Scheduler Scheduler_$_NON_CLUSTERED started.
24.09.2018 14:17:25,342 INFO   (com.logicaldoc.web.listener.ContextListener:  42) -- Cleanup past sessions of the current node (edc1c28a-9a92-4945-8e37-405a4036b680)
What could possible be the cause of this? I have tried versions 8.1 and 8.0.1 and both have the same issue.

Re: LogicalDoc Initial Startup fails when QuartzScheduler runs

Posted: Mon Oct 22, 2018 5:08 pm
by agaspa
Hi judeochalifu,
the most probable cause of your problem is that there was a problem during installation.
Because of this problem, the file (the main configuration file) has not been correctly compiled.
Probably some fields have not been valorized and then the application starts (at least in the scheduled services), but it is not possible to use it or access from the login.
The installation must be redone