[SOLVED] Plenty java errors in log file

Yes, it is installed, and uninstalled and reinstalled.
At that moment I see the items getting online

2019-02-06 20:43:21.212 [hingStatusInfoChangedEvent] - 'exec:command:homeeasy' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2019-02-06 20:43:21.216 [hingStatusInfoChangedEvent] - 'exec:command:homeeasy' changed from INITIALIZING to ONLINE

You are right about the rule, I need to rewrite it (pretty stupid of me :wink: and done while writing this reply)

I guess i_home_easy_run.state isn’t getting to OFF, since the exec is failing or hanging. I should try to fix that with a time-out indeed.
That would solve the issues with the rest of the system, but indeed, not with the exec binding.

I do see the trigger in the events log. i_home_easy_arg contains the arguments for the shell script.

2019-02-06 21:24:06.196 [ome.event.ItemCommandEvent] - Item 'i_bovenbed_trigger' received command 50
2019-02-06 21:24:06.204 [vent.ItemStateChangedEvent] - i_bovenbed_trigger changed from 100 to 50
2019-02-06 21:24:09.097 [ome.event.ItemCommandEvent] - Item 'i_home_easy_arg' received command 2660 dimmer 50
2019-02-06 21:24:09.103 [nt.ItemStatePredictedEvent] - i_home_easy_arg predicted to become 2660 dimmer 50
2019-02-06 21:24:09.110 [vent.ItemStateChangedEvent] - i_home_easy_arg changed from 2660 dimmer on to 2660 dimmer 50

I don’t see any specific entries in openhab.log about the exec binding.

Review Log4j2 Sample Config and put the Exec binding into debug or trace logging. Maybe we can see something there.

Or you can log into the karaf console and temporarily set logging to debug there.

ok, this is nuts.
I removed the while loop, and that did the trick.

Strange, as this was in place for a few months and working.

Well, like I said and elaborated on in the link above, long running Rules are a really bad idea. Before you were probably getting lucky with the timing and avoided problems. But since the update the timing has changed just enough that problems occur.

I would not have thought that the Exec binding would get stuck because of the long running Thread but I suppose it does.