Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

HMIPServer is constantly restarted

See original GitHub issue

Describe the bug HMIPServer is constantly restarted . The alarm messages show that the HMIPServer is restarted about once every minute. None of the HomematicIP devices can be controlled via the central since they do not show in the WebUI any more. In the hmserver.log an exception is logged during restart of the HMIPServer (full log see at the bottom):

Apr 28 11:28:44 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler ERROR [vert.x-worker-thread-4] Unable to fetch information for initialization of VirtualRemoteControl 
java.lang.NullPointerException
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:793)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:784)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:135)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:110)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:68)
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	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)

To Reproduce I do not know how to reproduce this. On my system the problem seems permanent since yesterday. Restarting the raspberry-pi does not change anything.

Expected behavior HMIPServer should not restart constantly and Homematic IP devices can be controlled via the central.

System information (please complete the following information):

  • Version 3.45.5.20190330
  • Hardware: RaspberryPi3

Additional context Log output of hmserver.log:

> Apr 28 11:28:45 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-2] SYSTEM: connector open 
> Apr 28 11:28:45 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Checking all devices on all accesspoints for updates 
> Apr 28 11:28:45 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 1 APs queued with updatable devices (RF) 
> Apr 28 11:28:45 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
> Apr 28 11:28:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (cef2f07d-a6e0-419f-aeb9-aa456588dc28) 
> Apr 28 11:28:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
> Apr 28 11:28:46 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (4610a042-b61c-4ca2-88df-0503a7abd3ac) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (a869be18-b217-449e-917e-a89e4e209674) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of EnergyPriceRequestWorker succeeded (5fbd06b9-dce4-4595-ae78-882d54f96f45) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (459c5efb-56ac-4c77-8fde-8ebcbfa68995) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (f9fa9673-e8a5-49f3-b5e3-5049ba33e0ee) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of StorageRequestWorker succeeded (8be5f4dc-b986-4aef-b9fa-1d4a4666ddfc) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (a3453624-7550-4d95-84ac-8ba8b4fcfb3c) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (95c2acb0-09a7-4b35-8626-ffa3068c109c) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (e53c4fcb-e7b5-4750-9e99-72449127bb38) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (c76bf488-f86a-495d-9170-e6a48374d1ed) 
> Apr 28 11:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
> Apr 28 11:28:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
> Apr 28 11:28:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] AP 3014F711A061A7D70992B8D0: OTAU Handler 447cca82-c488-42eb-b081-b2258ca8a839 continues for device(s) [3014F711A0001118A994F0E9] 
> Apr 28 11:29:13 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
> Apr 28 11:29:13 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
> Apr 28 11:29:13 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (4f106515-774a-4c9d-bf1b-ad6d7c6b6248) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of TransactionSubsystemHandler succeeded (8b156004-9fd7-4147-8ebd-980d186ab38c) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of HMIPTRXWriterWorker succeeded (5bdede56-6035-41a4-b876-ab3d0946fe13) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointElectroCardioGram succeeded (ee91e0b6-80e9-4d62-b64c-71e45cca799d) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (abbe4265-e443-4a8f-b823-2c1acae13ca6) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointKeyServerWorker succeeded (2d10a9b1-67bf-4f1a-abd7-e779a179b3f1) 
> Apr 28 11:29:19 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (41198673-abbd-4a06-9cb8-4d799f8c3e3e) 
> Apr 28 11:29:19 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (c61e0cae-581a-4043-88da-346e89ede5d7) 
> Apr 28 11:29:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of RouterKeyServerWorker succeeded (ed39ab8a-b530-432d-897c-de2e1c656779) 
> Apr 28 11:29:20 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started 
> Apr 28 11:29:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (e4c1b748-bb7a-4b91-9683-cb4ba0f54f54) 
> Apr 28 11:29:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CheckDeviceExistHandler succeeded (ab7be0d5-7ef1-46d8-9e5c-3e28d2134472) 
> Apr 28 11:29:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (83384de4-0a3a-42f9-b9b6-0f481278f6c7) 
> Apr 28 11:29:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (2ffa03ee-096f-477e-b196-ba834cccea97) 
> Apr 28 11:29:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (c148953f-b2ff-4329-9c20-d85d0466be1b) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of RemoteCommAdapterInitialization succeeded (dad34a3c-0a95-41af-9be7-b0ca1623477a) 
> Apr 28 11:29:22 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointAuthorisationHandler succeeded (d3fbc369-1549-426c-83a4-37b507c2f6ac) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointMessageDispatcher succeeded (f370ba91-f196-4a48-931e-4c989f4cd942) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of WebSocketManager succeeded (fdead227-ec1f-423c-99e5-500b76b5699e) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (287f806b-7395-4860-8c1f-343eed4bcab9) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (d62fbaab-af49-4af9-82ba-057de218f013) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointWatchdog succeeded (cc86d728-a204-431b-acac-7a654c42bef8) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointCommDevice succeeded (c51d561a-4f44-49a4-b557-fa4693b58908) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (af31a1e4-0849-40a9-97d5-2b3845aa19f2) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (bf3fe888-75af-4f2b-bce6-bfba3491d574) 
> Apr 28 11:29:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerAdapterInitialization succeeded (e6663d94-8da8-4132-bd5a-8d78eaa85af6) 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12507385... 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D70992B8D0 to 3 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
> Apr 28 11:29:22 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 58.5 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 535807757 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 535807884 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 26 link partners 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D70992B8D0 initialized 
> Apr 28 11:29:23 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RemoteCommAdapterFinalization succeeded (d2d55971-c64b-4860-8b6a-971e1d3cd98f) 
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (6c49664f-71ed-413e-88b2-1b12c46131b4) 
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (1cff865c-14ca-43e4-a059-cabb28ecc2d2) 
> Apr 28 11:29:24 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-0] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.178.24 
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyNotificationHandler succeeded (95afba3a-df51-4041-bd30-3fdd5c7d1043) 
> Apr 28 11:29:24 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler ERROR [vert.x-worker-thread-1] Unable to fetch information for initialization of VirtualRemoteControl 
> java.lang.NullPointerException
> 	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:793)
> 	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:784)
> 	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:135)
> 	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:110)
> 	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:68)
> 	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
> 	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
> 	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
> 	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
> 	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)
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (74cc1297-fbb8-4a86-a88d-b21da52ed12c) 
> Apr 28 11:29:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: Checking all devices on all accesspoints for updates 
> Apr 28 11:29:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: There are 1 APs queued with updatable devices (RF) 
> Apr 28 11:29:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
> Apr 28 11:29:24 de.eq3.cbcs.lib.lanrouting.LanRoutingWorker INFO  [vert.x-worker-thread-0] AP 3014F711A061A7D70992B8D0: Could not initialize routing of access point, version is 2.8.6 
> Apr 28 11:29:24 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-3] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.178.24) 
> Apr 28 11:29:24 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-1] UDP Routing multi cast established on network interface eth0 : 192.168.178.24 
> Apr 28 11:29:24 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-6] SYSTEM: Started Access Point WebSocket server with port 9293 
> Apr 28 11:29:24 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-6] SYSTEM: connector open 
> Apr 28 11:29:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LanRoutingWorker succeeded (f4aaff72-d223-4a81-ae9c-9a2ce37f68ca) 
> Apr 28 11:29:25 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (fff7c7b0-5ec9-4256-b423-6da25ee97710) 
> Apr 28 11:29:25 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
> Apr 28 11:29:25 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
> Apr 28 11:29:28 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
> Apr 28 11:29:28 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
> Apr 28 11:29:28 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
> Apr 28 11:29:28 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (5f173199-f5b2-41ff-9923-435df6cb160b) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (3f5c268e-5214-4782-9234-699c9fa6f432) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of EnergyPriceRequestWorker succeeded (cf57dae9-1701-43f8-a938-4a4327c2ad97) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (b85ddf50-4129-4225-8cfa-487a8874cce3) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of StorageRequestWorker succeeded (318ccbdc-e532-4ac0-99d4-36178696fbae) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (382ba683-7141-4893-adb1-e583cde7bd4e) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupRequestWorker succeeded (c5c30860-aea0-4434-bb2b-74df62062696) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (d07eaaf1-750f-4eb2-b426-fbacc99cb426) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (6c5ec2ca-b1f4-4a03-90be-52bf4af00329) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (8568a238-f052-4156-ab93-5c78d5d9c28c) 
> Apr 28 11:29:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
> Apr 28 11:29:29 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
> Apr 28 11:29:29 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
> Apr 28 11:29:29 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
> Apr 28 11:29:30 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
> Apr 28 11:29:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] AP 3014F711A061A7D70992B8D0: OTAU Handler bba3ad07-5c49-4b81-be79-0e574f4487f2 continues for device(s) [3014F711A0001118A994F0E9] 
> 
>

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:26 (12 by maintainers)

github_iconTop GitHub Comments

3reactions
jens-mauscommented, May 1, 2019

Deshalb reaktiviere ich dieses Ticket mal und flagge es als upstream issue.

0reactions
LeonVoscommented, Nov 8, 2019

HMIPServer restarted. Ik got the same error Ad of 04:45 thuis morning

Read more comments on GitHub >

github_iconTop Results From Across the Web

Homematic Binding: not all devices read from CCU
I yesterday faced this issue for a Homematic (not IP) device. Not sure, if more items where affected. It's a rain sensor, so...
Read more >
Homematic reconnect does not work - Third party integrations
Hi, I just started using Homematic IP components in HA. ... And the host connector always has the flag to skip the initialization...
Read more >
Nodemon keeps restarting server - Stack Overflow
JSON file is under the watch of nodemon, and you're constantly writing to it, your server will restart in an infinite loop thus...
Read more >
3.61.7.20220226 released - RaspberryMatic
This fixes issues where the setup routine incorrectly started ... optimized the multimacd , rfd and HMIPServer startup files to error out ...
Read more >
jens-maus/RaspberryMatic 3.61.7.20220226 on GitHub
This fixes issues where the setup routine incorrectly started ... optimized the multimacd , rfd and HMIPServer startup files to error out ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

Nur optional: alphabetische Favoriten-Sortierung

Next page

passwd segmentation fault