Rough start (lots of errors) on OpenHab 2.3 Release

sipvoip · May 28, 2018, 1:51pm

Items are technically loading before the errors, but not reconized when rules start:

2018-05-28 09:30:56.919 [INFO ] [org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl                                       ] - Loading model 'lifx.items'
2018-05-28 09:31:01.409 [INFO ] [org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl                                       ] - Loading model 'mqtt-power.items'

But still see items not found:

2018-05-28 09:31:31.806 [ERROR] [org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl                             ] - Rule 'Today House Used': The name 'Power_Color' cannot be resolved to an item or type; line 32, column 15, leng
th 11
2018-05-28 09:31:31.810 [ERROR] [org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl                             ] - Rule 'Today Grid Used': The name 'Grid_wh' cannot be resolved to an item or type; line 5, column 31, length 7
2018-05-28 09:31:31.810 [ERROR] [org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl                             ] - Rule 'First Floor Heat Pump': The name 'Circuit_C06' cannot be resolved to an item or type; line 64, column 7, 
length 11
2018-05-28 09:31:31.811 [ERROR] [org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl                             ] - Rule 'Second Floor Heat Pump': The name 'Circuit_C07' cannot be resolved to an item or type; line 78, column 7,
 length 11
2018-05-28 09:31:31.963 [ERROR] [org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl                             ] - Rule 'Outside_Air_Sensor': The name 'DatatypeConverter' cannot be resolved to an item or type; line 11, column 
14, length 17

Lots of NullPointerExceptions:

2018-05-28 09:31:45.877 [WARN ] [org.eclipse.smarthome.core.internal.common.WrappedScheduledExecutorService                          ] - Scheduled runnable ended with an exception
java.lang.NullPointerException: null
	at org.openhab.binding.miio.internal.Utils.hexStringToByteArray(Utils.java:40) ~[?:?]
	at org.openhab.binding.miio.handler.MiIoBasicHandler.initializeData(MiIoBasicHandler.java:221) ~[?:?]
	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:293) [?:?]
	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:748) [?:?]

Seeing a bunch of ServletExceptions:

javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_0,0,1969850359) has been shut down

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [15:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [82:org.eclipse.jetty.security:9.3.21.v20170918]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.Server.handle(Server.java:534) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at java.lang.Thread.run(Thread.java:748) [?:?]

mstormi · May 28, 2018, 5:09pm

Try clearing the cache (again, it should do it on package upgrades but I don’t know your installation method).
Don’t keep clients (UI, habdroid) online while upgrading.
Eventually try to delay rules processing (move them away and back in when startup activity has settled) or automate that.

sipvoip · May 28, 2018, 8:39pm

I always clear /var/lib/openhab2/cache/ and /var/lib/openhab2/tmp/ before upgrades.

As far as keeping clients online, that is a hard one since I have 21 of them. I would think if clients should not talk to openHAB until it is ready then it should not bring it’s rest port up until it’s ready.

rlkoshak · May 28, 2018, 11:38pm

This looks a lot like the same thing reported here: Update to openhab 2.3 kinda broke everything

Unfortunately, I don’t think that these will be much help. Kees just messed with his items files until it started working. But all the errors you are seeing could originate from an items file not loading.