Hey *, I have a strange behavior with my openHAB installation. About 45 minutes after startup all scheduled roles suddenly stop working. I already enabled debug logging on org.eclipse.smarthome.model and org.quartz.core but there’s no useful information to find. I use the official Docker Image (…

[image] sdda: I’ve already done that. They simply don’t trigger anymore. (ref rule logs) The general idea is to check that every preceding call of a rule has an exit. We know you don’t get triggers, but this is looking for rules that hang up before the point of disaster, consuming threads. I…

Sorry, I forgot to mention that I know that article and I don’t have a single thread::sleep in these rules and there are rarely any timers at all. Whenever possible I use the expire binding. All other rules are still working. Only the scheduled ones suddenly stop.

As you’ll know from the long thread, cron-triggered rules run using a thread from a different pool to regular rules [image] sdda: All other rules are still working. So that’s a strong hint it’s a scheduled “something” at work. Various bindings use the same scheduler, so we should not rule t…

how many cron triggered rules do you run? How often do they trigger? Give us some use case ideas here… what are you doing (with cron triggered rules) Are they triggering every few moments or at some specific time of the day? Final question: are these rules that have always worked up until now or ar…

[image] rossko57: As a crude diagnostic, you could add a logInfo() to the start and exit of each of your cron rules, just to see if any hang up. I’ve already done that. They simply don’t trigger anymore. [image] Andrew_Rowe: how many cron triggered rules do you run? 9 [image] Andr…

First of all, thanks for the detailed reply! Much appreciated! I didn’t even notice that it is still the V1 Telegram Binding. I will debug all rules and see if I can find the culprit. Thanks a lot for the first time, I will get back to you :+1:

I think I have found the error! var int myRuleStarts = 0 rule "AirPurifier pull Data" when Time cron "0 0/5 * * * ?" then myRuleStarts = myRuleStarts +1 if (myRuleStarts >1) { logInfo("AirPurifier pull Data", "WARNING - multiple starts of my rule " + myRuleStarts.toString) } e…

Bit mysterious. I’m not surprised there is an exec involved, but you seem to have a correct timeout and no reason to hang up. Thinks: some other process gobbling up schedule threads could stop the timeout working? Surely not - if there were no threads we could not start the rule in the first place…

If you can verify with a simple rule like the above that the timeout is indeed being ignored please file an issue on openHAB-core (I think that’s where executeCommandLine lives). That would definitely be a bug that needs to be fixed. Though I suspect a fix won’t occur until OH 3. In the mean time, …

I will try to debug this when I’m back home :+1:

openHAB Community

Cron scheduled rules suddenly stop working

Setup, Configuration and Use Scripts & Rules

rlkoshak (Rich Koshak) August 25, 2020, 7:52pm 2

Start here: (OH 1.x and OH 2.x Rules DSL only] Why have my Rules stopped running? Why Thread::sleep is a bad idea