Cisco Bug: CSCvs97249 - Monitoring service can fail to initialize scheduler service
May 31, 2020
- Cisco Elastic Services Controller
Known Affected Releases
Symptom: The ESC monitor service can fail to startup its scheduler service. When this condition latches there is a complete loss of monitoring service on the impacted ESC instance. The following log signature in ESC mona.log indicates this condition has been latched: 2020-02-07 20:37:53.925 [main] Quartz scheduler version: 2.3.1 2020-02-07 20:37:53.926 [main] Scheduler QuartzScheduler_$_NON_CLUSTERED started. 2020-02-07 20:37:53.926 [main] Quartz scheduler initialized!!! 2020-02-07 20:37:53.926 [main] Scheduler Engine Initialized 2020-02-07 20:37:53.975 [http-nio-127.0.0.1-8090-exec-1] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2020-02-07 20:37:53.975 [http-nio-127.0.0.1-8090-exec-1] Quartz Scheduler v.2.3.1 created. 2020-02-07 20:37:53.975 [http-nio-127.0.0.1-8090-exec-1] RAMJobStore initialized. 2020-02-07 20:37:53.975 [http-nio-127.0.0.1-8090-exec-1] Scheduler meta-data: Quartz Scheduler (v2.3.1) 'QuartzScheduler' 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 100 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. Conditions: Unknown. No field reports; only observed in internal testing.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases