Upgrade from openhab 2.1 to 2.4: BasicUI stopped

  • Platform information:
    • Hardware: intel N2800 @ 1.86GHz
    • OS: ubuntu 16.4 LTS
    • Java Runtime Environment: “1.8.0_101” oracle
    • openHAB version: 2.4.0

Hello,

having stable and working OH 2.1 installation

tried several times to upgrade to OH 2.4

new folder for OH2.4
stopped OH2.1
deleting cache and tmp
copied items/transforms/sitemaps etc.
copied persistense rrd4j
changed rules for calendar: .zonedDateTime.toInstant.toEpochMilli

without rules no problem : everything running stable: 3 sitemaps and the BasicUI and PaperUI

adding some or all rules:

strange exceptions and [ERROR] in openhab.log
resulting in final line “BasicUI stopped”

What i’m doing completly wrong ?

adding only one rules file and disabling the “startup system” rules working also. However, it’s impossible to run OH2.4 for more than 60 sec.

Why is the rule engine so critical and not catching problems without full stop?

I found for all problems separetly posts here in forum…

Best regards,
Peter

openhab2.4.log (371.9 KB)


file conf/services/addons.cfg:

binding = http1,exec1,astro,hue,mqtt1
ui = basic,paper
transformation = map,jsonpath,javascript,regex
legacy = true

many issues:

getState() execption. copied persistent data from OH2.1. Data are drawn well in Graph Diagramm

2019-01-30 17:59:41.549 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2019-01-30 17:59:52.513 [INFO ] [penhab.io.transport.mqtt.MqttService] - Stopping broker connection 'tux'
2019-01-30 17:59:52.545 [INFO ] [ding.astro.internal.job.JobScheduler] - Deleting astro job: Season
2019-01-30 17:59:52.551 [INFO ] [ding.astro.internal.job.JobScheduler] - Deleting astro job: DailyJob
2019-01-30 17:59:52.838 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI
2019-01-30 17:59:53.738 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule 'Se
t Default Values solaris': cannot invoke method public org.eclipse.smarthome.core.types.State org.eclipse.smarthome.cor
e.items.GenericItem.getState() on null
2019-01-30 17:59:53.741 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
        at org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl.lambda$1(RuleEngineImpl.java:318) ~[
?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.
java:180) ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:29
3) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
        at java.lang.Thread.run(Thread.java:745) [?:?]
2019-01-30 17:59:53.944 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2019-01-30 17:59:54.015 [ERROR] [.smarthome.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.Ex
ecutionException: java.nio.channels.AsynchronousCloseException

a very normal item does not exist by surprise anymore:

2019-01-30 21:43:31.811 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Send telegram Solaris BSK ': The name 's
olarisBSK' cannot be resolved to an item or type; line 42, column 8, length 10

“logInfo()” by surprise not there:

2019-01-31 22:34:17.752 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'WZ_daemmerung_sonne': The name 'logInfo'
 cannot be resolved to an item or type; line 138, column 9, length 41

other

2019-02-15 22:29:33.248 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service
 on port 5007
2019-02-15 22:29:50.872 [INFO ] [egram.internal.TelegramActionService] - Bot n3a_smarthome loaded from config file
2019-02-15 22:29:50.945 [ERROR] [org.eclipse.smarthome.io.rest.sse   ] - FrameworkEvent ERROR - org.eclipse.smarthome.i
o.rest.sse
org.osgi.framework.BundleException: Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bun
dle org.eclipse.smarthome.io.rest.sse.
        at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:800) ~[?:?]

some more:

2019-02-22 22:28:53.943 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2019-02-22 22:28:54.044 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2019-02-22 22:28:55.455 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule 'Se
t Default Values solaris': cannot invoke method public org.eclipse.smarthome.core.types.State org.eclipse.smarthome.cor
e.items.GenericItem.getState() on null
2019-02-22 22:28:55.460 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule 'Se
t Default Values': null
2019-02-22 22:28:55.556 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
        at org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl.lambda$1(RuleEngineImpl.java:318) ~[
?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]

OFF by surprise not exist:

2019-02-22 22:49:11.043 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'WZ_daemmerung_sonne': The name 'OFF' can
not be resolved to an item or type; line 143, column 42, length 3

The have been massive changes to openHAB since 2.1, it will be hard work to upgrade and skip 2 major releases.
Please start reading all the breaking changes at the bottom of the release notes:



You need to upgrade your java version to the latest java8, there have been a lot of security updates.

What does that mean? Are you running a manual installation?

There was almost no syntax checking in your old 2.1 release, this has significantly changed: if you have a minor bug in your rules, it could have worked with 2.1, but it does not with newer releases.

This may not be a problem at all as the rule using that item may have been loaded before the item was initialized.

I would strongly recommend to use Visual Studio Code with the openHAB plugin to verify your rules syntax:

1 Like

Hello SiHui,

thank for the broad answer and hints

updated JRE
installed VS Code
[ no syntax check using SMB folder \\openhabpi\openhab24\conf only Y: e.g. - caused by the issue


found out that is was not fixed in 0.4.1

had to use drive letter (X:)
]
reworked 9 issues
add !== null before using .state

–> looks fine and running now :+1:

THANKS

1 Like