[OH 2.4.0 M6] Testing Results

If you want help, you mustn’t be so hesitant in giving information upfront.

What’s your HW ? If it’s a Pi or other low-mem ARM SBC then yes.
It’s using a lot more memory than 32bit JVM which you don’t have, this can result in all different kinds of problems. Either way, move to 32bit JVM. No point in using any 64bit one with openHAB.

1 Like

Hi Markus. Sorry for the missing information. I am using a Intel Nuc, i3, 8Gb ram with Ubuntu 16.04 Lts 64 bit.
Okay, better i use the 32bit version?

Found it in the documentation. Always use the 32bit version. :blush:
Greetings,
Markus

Since this version I find these WARNING-Messages in the log file:

2018-11-25 17:04:05.868 [INFO ] [vice.internal.HttpServiceFactoryImpl] - Binding bundle: [org.eclipse.smarthome.ui_0.10.0.oh240M6 [148]] to http service
2018-11-25 17:04:05.993 [INFO ] [rg.ops4j.pax.web.utils.ClassPathUtil] - Ignoring bundle scan for /META-INF/services javax.servlet.ServletContainerInitializer.
2018-11-25 17:04:06.121 [INFO ] [ce.jetty.internal.HttpServiceContext] - registering context DefaultHttpContext [bundle=org.eclipse.smarthome.ui_0.10.0.oh240M6 [148], contextID=custom], with context-name: 
2018-11-25 17:04:06.209 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.eclipse.smarthome.ui_0.10.0.oh240M6 [148], contextID=custom]}
2018-11-25 17:04:06.639 [INFO ] [rg.ops4j.pax.web.utils.ClassPathUtil] - Ignoring bundle scan for /META-INF/services javax.servlet.ServletContainerInitializer.
2018-11-25 17:04:06.795 [INFO ] [ce.jetty.internal.HttpServiceContext] - registering context DefaultHttpContext [bundle=org.eclipse.smarthome.ui_0.10.0.oh240M6 [148], contextID=default], with context-name: 
2018-11-25 17:04:07.043 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.eclipse.smarthome.ui_0.10.0.oh240M6 [148], contextID=default]}
2018-11-25 17:04:08.103 [INFO ] [vice.internal.HttpServiceFactoryImpl] - Binding bundle: [org.eclipse.smarthome.ui.icon_0.10.0.oh240M6 [149]] to http service
2018-11-25 17:04:08.249 [INFO ] [rg.ops4j.pax.web.utils.ClassPathUtil] - Ignoring bundle scan for /META-INF/services javax.servlet.ServletContainerInitializer.
2018-11-25 17:04:08.341 [INFO ] [ce.jetty.internal.HttpServiceContext] - registering context DefaultHttpContext [bundle=org.eclipse.smarthome.ui.icon_0.10.0.oh240M6 [149], contextID=default], with context-name: 
2018-11-25 17:04:08.290 [WARN ] [org.eclipse.jetty.server.HttpChannel] - /rest/sitemaps/default/0502
javax.servlet.ServletException: javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_1,2,33220692) has been shut down

	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:88) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.Server.handle(Server.java:531) ~[84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) [84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) [84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:291) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ssl.SslConnection$3.succeeded(SslConnection.java:151) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_1,2,33220692) has been shut down

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489) ~[?:?]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) ~[?:?]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[?:?]
	... 18 more
Caused by: org.glassfish.hk2.api.MultiException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_1,2,33220692) has been shut down

	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:106) ~[?:?]
	at org.jvnet.hk2.internal.FactoryCreator.dispose(FactoryCreator.java:173) ~[?:?]
	at org.jvnet.hk2.internal.SystemDescriptor.dispose(SystemDescriptor.java:526) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.remove(RequestScope.java:532) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.release(RequestScope.java:549) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319) ~[?:?]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) ~[?:?]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) ~[?:?]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) ~[?:?]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) ~[?:?]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[?:?]
	... 18 more
Caused by: java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_1,2,33220692) has been shut down
	at org.jvnet.hk2.internal.ServiceLocatorImpl.checkState(ServiceLocatorImpl.java:2288) ~[?:?]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandleImpl(ServiceLocatorImpl.java:629) ~[?:?]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:622) ~[?:?]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:640) ~[?:?]
	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:103) ~[?:?]
	at org.jvnet.hk2.internal.FactoryCreator.dispose(FactoryCreator.java:173) ~[?:?]
	at org.jvnet.hk2.internal.SystemDescriptor.dispose(SystemDescriptor.java:526) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.remove(RequestScope.java:532) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.release(RequestScope.java:549) ~[?:?]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319) ~[?:?]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) ~[?:?]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) ~[?:?]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) ~[?:?]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) ~[?:?]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) ~[?:?]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) ~[?:?]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) ~[?:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) ~[?:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) ~[?:?]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[?:?]
	... 18 more
2018-11-25 17:04:08.803 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.eclipse.smarthome.ui.icon_0.10.0.oh240M6 [149], contextID=default]}
2018-11-25 17:04:09.435 [INFO ] [vice.internal.HttpServiceFactoryImpl] - Binding bundle: [org.openhab.ui.dashboard_2.4.0.M6 [183]] to http service
2018-11-25 17:04:09.555 [INFO ] [rg.ops4j.pax.web.utils.ClassPathUtil] - Ignoring bundle scan for /META-INF/services javax.servlet.ServletContainerInitializer.
2018-11-25 17:04:09.660 [INFO ] [ce.jetty.internal.HttpServiceContext] - registering context DefaultHttpContext [bundle=org.openhab.ui.dashboard_2.4.0.M6 [183], contextID=default], with context-name: 
2018-11-25 17:04:09.743 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.openhab.ui.dashboard_2.4.0.M6 [183], contextID=default]}

Also this warning is new for me:

2018-11-25 10:57:58.280 [WARN ] [org.eclipse.jetty.server.HttpChannel] - /start/favicon.ico
javax.servlet.ServletException: java.nio.channels.ClosedChannelException
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:88) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.Server.handle(Server.java:531) ~[84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) [84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) [84:org.eclipse.jetty.server:9.4.11.v20180605]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:291) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ssl.SslConnection$3.succeeded(SslConnection.java:151) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) [75:org.eclipse.jetty.io:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) [87:org.eclipse.jetty.util:9.4.11.v20180605]
	at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.nio.channels.ClosedChannelException
	at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427) ~[?:?]
	at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:507) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:257) ~[?:?]
	at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:341) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:874) ~[?:?]
	... 3 more

I’ve noticed my logs are full of these errors now. It’s as if sending OFF/ON to a dimmer item isn’t working nicely for logging. I’ve been away from home but just logged in to check some things for my wife and noticed them.

I have a lot of Lifx bulbs and a rule for each which sends ON/OFF to a switch item (that’s bound to the brightness channel) when it’s status goes ONLINE/OFFLINE.

Item

Switch	vLight_LivingTV1    	"Living TV Light 1"     	<switch>		(gLights_LivingTV, gLights, gLights_Num)		{ channel="lifx:whitelight:livingtv1:brightness" }

Rule

rule "Turn on/off Living TV Light 1"
	when 
		Thing "lifx:whitelight:livingtv1" changed
	then
		var status = ThingAction.getThingStatusInfo("lifx:whitelight:livingtv1").getStatus()
		
		if (status.toString() == 'OFFLINE')
		{
			//logError("Debug", "Attempting to turn off light")
			postUpdate(vLight_LivingTV1, OFF)			
		}
		else {
			vLight_LivingTV1.sendCommand(ON)
		}
end	

Error

2018-11-26 08:19:14.763 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.IllegalArgumentException: Value must be between 0 and 100
	at org.eclipse.smarthome.core.library.types.PercentType.validateValue(PercentType.java:58) ~[?:?]
	at org.eclipse.smarthome.core.library.types.PercentType.<init>(PercentType.java:53) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.util.LifxMessageUtil.kelvinToPercentType(LifxMessageUtil.java:98) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.handler.LifxLightHandler$CurrentLightState.updateColorChannels(LifxLightHandler.java:173) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.handler.LifxLightHandler$CurrentLightState.setColors(LifxLightHandler.java:146) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.LifxLightState.setColor(LifxLightState.java:119) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.LifxLightCurrentStateUpdater.handleLightStatus(LifxLightCurrentStateUpdater.java:176) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.LifxLightCurrentStateUpdater.handleResponsePacket(LifxLightCurrentStateUpdater.java:150) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.LifxLightCommunicationHandler.lambda$3(LifxLightCommunicationHandler.java:243) ~[?:?]
	at java.util.concurrent.CopyOnWriteArrayList.forEach(CopyOnWriteArrayList.java:891) ~[?:?]
	at org.eclipse.smarthome.binding.lifx.internal.LifxLightCommunicationHandler.lambda$2(LifxLightCommunicationHandler.java:243) ~[?:?]
	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:293) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

Before M6 I was on 2.3 stable and there were no errors. I’ll need to check when I’m home tonight/tomorrow whether the warnings in the log are just warnings and I can ignore them.

This one is an old one and I experience it also when:
stop OH2
start it immediately (within less than 5 seconds)
If I leave the service down for 10-15 secs and start it up again: this warn does not appear any more.
I don’t know what is causing it. Some say open browsers trying to reconnect to the Web UIs (so you need to let them timeout and then start the service)

this could also be related to open browsers… not sure… I don’t remember seeing this one before

To All coming from openHAB 2.3.0 to openHAB 2.4.0 Milestone 6:

Remember the breaking changes that 2.4 brings and deal with them (easy to handle):

Listing important changes for version 2.4.0:
  Warning:  Astro Binding: The 'kilometer' and 'miles' channels have been replaced by a new 'distance' channel
  Warning:  Jeelink Binding: The 'currentWatt' and 'maxWatt' channels have been replaced with 'currentPower' and 'maxPower' channels
  Warning:  WeatherUnderground Binding: A bridge has been added on top of the current things, you need to add a bridge containing your api-key.
  Warning:  ZWave Binding: Major changes have been merged to support features such as security. All things must be deleted and re-added. Refer to https://community.openhab.org/t/zwave-binding-updates/51080 for further information.
  Warning:  Synop Binding is now using UoM. 'wind-speed-ms' and 'wind-speed-knots' channels have been replaced by a single 'wind-speed' channel.

Who can help me with this question please: Add openHAB Milestone build # to dashboard footer · Issue #437 · openhab/openhab-core · GitHub

Which LIFX lights are you using? It’s probably caused by ESH PR #6499 which makes the binding aware of light specific color temperature ranges.

I have a range of Lifx lights. Colour, whites, and mini’s. The only rules I have running on them is the postUpdate of OFF/ON when the status changes. The Switch items are all bound only to the brightness channel, not temperature if that makes any difference.

I haven’t seen it with my range of LIFX lights @pahansen. :roll_eyes:

The binding receives the color temperature values with the light state updates so it will process these regardless of the channel being linked.

Maybe your lights still have some old values outside the valid range?

Can you test this org.eclipse.smarthome.binding.lifx-0.10.0-SNAPSHOT.jar?
It will just use 0/100 as min/max which should hopefully fix it (see these code changes).

@wborn That fixes the warnings it seems. None are present in the logs in any case. The rule continues to fire and logInfo as expected. :+1:

Thanks for testing the changes @pahansen! I’ve created a PR to get them merged:

Hi All,

Do you have an issue with astro?
For me sometime missing some event, here the sun set:

2018-11-27 11:04:00.004 [vent.ChannelTriggeredEvent] - astro:moon:local:set#event triggered END
2018-11-27 17:11:00.004 [vent.ChannelTriggeredEvent] - astro:sun:local:astroDusk#event triggered START
2018-11-27 17:11:00.009 [vent.ChannelTriggeredEvent] - astro:sun:local:nauticDusk#event triggered END
2018-11-27 17:48:00.006 [vent.ChannelTriggeredEvent] - astro:sun:local:astroDusk#event triggered END
2018-11-27 17:48:00.015 [vent.ChannelTriggeredEvent] - astro:sun:local:eveningNight#event triggered START
2018-11-27 17:48:00.019 [vent.ChannelTriggeredEvent] - astro:sun:local:night#event triggered START

That should happend at 15:55

O.

edit: I don’t have this… I can see astro:sun:local:set#event (Start & End)

2018-11-27 16:37:00.005 [vent.ChannelTriggeredEvent] - astro:sun:local:set#event triggered START
2018-11-27 16:41:00.000 [vent.ChannelTriggeredEvent] - astro:sun:local:set#event triggered END
2018-11-27 16:41:00.001 [vent.ChannelTriggeredEvent] - astro:sun:local:civilDusk#event triggered START
2018-11-27 17:13:00.002 [vent.ChannelTriggeredEvent] - astro:sun:local:nauticDusk#event triggered START
2018-11-27 17:13:00.003 [vent.ChannelTriggeredEvent] - astro:sun:local:civilDusk#event triggered END
2018-11-27 17:49:00.001 [vent.ChannelTriggeredEvent] - astro:sun:local:astroDusk#event triggered START
2018-11-27 17:49:00.001 [vent.ChannelTriggeredEvent] - astro:sun:local:nauticDusk#event triggered END
2018-11-27 18:24:00.001 [vent.ChannelTriggeredEvent] - astro:sun:local:night#event triggered START
2018-11-27 18:24:00.001 [vent.ChannelTriggeredEvent] - astro:sun:local:astroDusk#event triggered END
2018-11-27 18:24:00.002 [vent.ChannelTriggeredEvent] - astro:sun:local:eveningNight#event triggered START

maybe related: [Astro] Sometimes the event doesn’t get scheduled for all of the Astro Things · Issue #6107 · eclipse-archived/smarthome · GitHub ?

Thanks, than come the reinstall the binding :slight_smile:

For me, on M6 openHab process freezes regurarly.
I can’t say much about it, it randomly stops (there is no event in the log about it). When it stops I can’t even connect to the RPi on SSH. After a few minutes (30-40 minutes) the service is restarted by itself and it loads openHab again. Systemctl says it’s exited and the exit code is 1 (Failure).
Anyone knows how can I debug this?

only logs can show us what is happening. where are they? :slight_smile:

Which log can be useful? :slight_smile: openhab.log outputs nothing right before when it stops, events.log shows regular item updates/commands, nothing unexpected there.

is there anything? useful in:

journalctl -n 100 -u openhab2

also: what is your java -version ?

Nothing special. Now it is running since 07:45, so it should be if the logs started at 06:33


-- Logs begin at Wed 2018-11-28 06:33:26 CET, end at Wed 2018-11-28 08:53:20 CET. --
Nov 28 06:58:01 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.
Nov 28 07:23:14 openHABianPi systemd[1]: Stopping openHAB 2 - empowering the smart home...
Nov 28 07:25:14 openHABianPi systemd[1]: Stopped openHAB 2 - empowering the smart home.
Nov 28 07:45:25 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.

Java version:

openjdk version "1.8.0_152"
OpenJDK Runtime Environment (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 1.8.0_152-b76)
OpenJDK Client VM (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 25.152-b76, mixed mode, Evaluation)