Script throws exception on openHAB startup, sometimes

[5iver (Scott Rushworth)]

@wessjan

As with the other posters the log is flooded with the Java exception, which causes the system so busy, that the initialization will not complete.

Could you post your log with an example of these errors? Are you possibly experiencing some of the issues in this topic?

2.5 issues after upgrade

This post is meant to summarize the most often encountered problems to appear after you upgraded your system to 2.5 (or 2.5.x, actually). I’ll update/extend it over time. Let me know if you feel there’s substantial stuff missing (issues) or insufficient (explanations how to fix). ** Anyone: ** ** Please check these out first before posting about your problem. ** Assumptions This post assumes you ran 2.4 before your upgrade. If you upgraded from some earlier version or some non-release versio…

[wessjan (Jan Wessels)]

Hi Scott,
the update from 2.4 to 2.5 had not produced the issue, it started on one of the minor updates within 2.5. I think it was 2.5.2 to 2.5.3 but I’m not sure.

I’ve attached the complete openhab.log beginning with the startup after the update from 2.5.4-1 to 2.5.5-1 until it run without errors. I’ve only masked my coordinates in the Location settings. (it’s a tarball, but have to have a known extension to allow the upload. Please remove .txt from the filename to allow proper processing) openhab.log.tgz.txt (261.5 KB)

*Update: Clearing the cache only slowed down startup, but hadn’t helped to avoid the Java exeptions.

regards Jan

[rossko57]

@wessjan

Clearing the cache only slowed down startup, but hadn’t helped to avoid the Java exeptions.

Yes, that’s an action that would be expected to make it worse (and is performed anyway as part of an upgrade)
Reportedly, it can two or three restarts to properly rebuild the cache, so see what’s left after that.

[5iver (Scott Rushworth)]

Your log looks to have rules loading before the Items are ready. I suggest scrapping the clunky old rules DSL and using scripted automation with Jython and the helper libraries, where you will not have this issue. If you want to stay with the rules DSL, then you should setup a way to delay the rules from loading.

Delay Rule loading after Startup in OH2?

Unfortunately, this still seems to be an issue… …where rules get loaded before everything gets initialized. There is no such configuration as in OH1 to delay the loading. Here is a related topic and the solution I had used: Since then, I have modified the script (you’ll need to create the prestart directory): #!/bin/sh mv `\ls -1 /opt/openhab2/conf/rules/*.rules | grep -v Startup.rules` /opt/openhab2/conf/rules/prestart echo echo Launching the openHAB runtime... DIRNAME=`dirname "$0"` exe…

Cleaning up the startup process / renaming rules (windows possible)

I’ve run in some issues with the current startup process. Everything is starting at once which leads to several exceptions, errors and other problems. In my case the most annoying problem is the Homematic-Channel not found-problem. According to my opinion, a reason is the triggering of rules during startup which leads to timing problems and other race conditions which then lead to further problems after startup. I often read about moving or renaming the rules and copying back after startup, so…

[wessjan (Jan Wessels)]

@5iver

I suggest scrapping the clunky old rules DSL and using scripted automation with Jython and the helper libraries

I don’t stick to the rules, but I’ve never used Jython. Is there any documentation how to substitue the behavior of a rule in a Jython script? And how will this avoid the main issues I currently have with the pubholiday.script, which is parsed before the items are available?

[5iver (Scott Rushworth)]

The link I provided has links to more instruction. Post if you run into trouble converting. The rules DSL runs on the old rule engine, which has been removed in OH 3.0. The new rule engine does not have the same issue.