Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[WARN] Scheduled Rule execution skipped

See original GitHub issue

2017-10-14 01:02:14,980 WARN [Quartz_Scheduler_Worker-6] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 01:36:14,009 WARN [Quartz_Scheduler_Worker-5] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 03:00:14,009 WARN [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 04:16:14,008 WARN [Quartz_Scheduler_Worker-5] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 04:50:14,063 WARN [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 06:09:14,010 WARN [Quartz_Scheduler_Worker-3] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 07:27:14,397 WARN [Quartz_Scheduler_Worker-6] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 09:14:15,128 WARN [Quartz_Scheduler_Worker-3] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 09:32:14,007 WARN [Quartz_Scheduler_Worker-8] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 09:48:14,010 WARN [Quartz_Scheduler_Worker-4] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 10:33:14,008 WARN [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 11:03:14,008 WARN [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 12:00:14,008 WARN [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 12:25:14,007 WARN [Quartz_Scheduler_Worker-2] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 12:48:14,010 WARN [Quartz_Scheduler_Worker-1] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 13:03:14,008 WARN [Quartz_Scheduler_Worker-10] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 13:11:14,014 WARN [Quartz_Scheduler_Worker-1] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
2017-10-14 13:52:14,407 WARN [Quartz_Scheduler_Worker-8] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms

Is this something I have to worry about? Does this mean that the engine was totally not responding and missing any incoming messages?

As you can see that happens alway on second 14 Maybe some overloaded regular task?

This somehow reminds me of https://github.com/mycontroller-org/mycontroller/issues/253 where the task to clean up the resource log was the problem. I have it already lowered to 15 minutes and got ~1300 messages in total in the resource log.

Just to be clear … during this time the web-interface is NOT responsive …

@jkandasa You have any idea about this as this is currently a big concern

Issue Analytics

State:
Created 6 years ago
Comments:24 (9 by maintainers)

Top GitHub Comments

1reaction

cimba007commented, Oct 25, 2017

Everything fine for now … I will have to gather some data again (7days) and compare performance in regards the version without index.

0reactions

jkandasacommented, Feb 23, 2018

@cimba007 If you see this issue kindly reopen.

Top Results From Across the Web

Reason For alert : schedule execution skipped previous ...

Reason For alert : schedule execution skipped previous execution has not ended (Resource Search Index Updater) ? ... Kindly anyone advice why this ......

elaws - WARN Advisor - U.S. Department of Labor

WARN allows voluntary payments of wages and benefits to be offset against any damages that might be awarded. If, however, a payment is...

Troubleshooting CloudWatch Events - AWS Documentation

Your scheduled rule will be triggered within that minute but not on the precise 0th second. My rule matches IAM API calls but...

Alert Processing Explained - Support and Troubleshooting

An alert is opened whenever an event is not ignored or its threshold is exceeded by an event rule, and de-duplication does not...

Guidance on Conditional Suspension of California WARN Act ...

The Executive Order does not suspend the California WARN Act in its entirety, nor does it suspend the law for all covered employers....