PiVCCU 3.41.11-17 WEB-IF nicht erreichbar

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Antworten
wendy2702
Beiträge: 463
Registriert: 05.03.2014, 19:31
Hat sich bedankt: 1 Mal
Danksagung erhalten: 1 Mal

PiVCCU 3.41.11-17 WEB-IF nicht erreichbar

Beitrag von wendy2702 » 05.03.2019, 18:29

Hi,

ich habe heute das Problem das ich nicht mehr auf das WEB-IF der CCU 3 komme. Ich habe in ioBroker schon Rega/RPC Adapter deaktiviert.

PiVCCU neu gestartet, PI neu gestartet... keine Änderung.

Hier mal ein paar logs:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/hmserver.log
Mar 5 18:11:59 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Mar 5 18:11:59 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Mar 5 18:11:59 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Mar 5 18:12:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default
Mar 5 18:12:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default
Mar 5 18:12:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default
Mar 5 18:12:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default
Mar 5 18:12:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Mar 5 18:12:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 21 classes to Vert.x
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 21 VertxDeployers initialized
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (e88bed4f-8965-46fb-88aa-6472aca47b64)
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of CheckDeviceExistHandler succeeded (efa48f2f-188e-406d-9c2d-71ba6dab8fd2)
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (af3780e4-cb1c-448a-9a4a-959c955bebae)
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of TransactionSubsystemHandler succeeded (7a480745-033e-4ad9-b67a-d563a36765ae)
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (3a0a378e-b51b-417a-ad71-4526d2f1b6e2)
Mar 5 18:12:05 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Mar 5 18:12:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of KeyServerWorker succeeded (f441dadf-d05e-4a1c-8275-b0ba6effc72a)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KryoPersistenceWorker succeeded (86628fd4-2a90-4bb6-8245-4ed467c47365)
Mar 5 18:12:06 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: DeviceLiveUpdateSubsystem started
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (7b7502ad-d313-4d7c-9c25-8b7cfb5fd966)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (673f3367-fef5-4a30-bb83-97f98f30ab9f)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerPersistentDataLoader succeeded (26652b5a-5043-495f-b861-5d4433b72e0e)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (5db3848b-d822-492a-8496-8d189e2fea8a)
Mar 5 18:12:06 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/config/firmware
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of FirmwareLoaderFileSystem succeeded (3490f22c-1778-475d-bef9-f0b553c4bf98)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (88aa8040-794d-4406-b3c6-dd1e0a68f407)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyNotificationHandler succeeded (fa2f4b7d-1f95-464b-86c7-c315cef55044)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of IncomingHMIPFrameHandler succeeded (935185cd-b543-497d-aa35-ee00199fd69c)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (fe359e2b-9e57-4357-88c9-055b03de48c8)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBackendNotificationHandler succeeded (7f24c47f-fa23-41e3-b13c-9386e50f91f6)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (4635785d-05f4-4fb1-a401-64e7ab37af42)
Mar 5 18:12:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerAdapterInitialization succeeded (6a3859a2-a577-4793-bb6f-09291b239cac)
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11899696...
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A992F7B6 to 3
Mar 5 18:12:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version...
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 3.4.8
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.34.0
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 250622464
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 250636625
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A992F7B6 initialized
Mar 5 18:12:07 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Mar 5 18:12:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyInitializion succeeded (a206b2e3-4b97-4b98-88a5-114d6dfea419)
Mar 5 18:12:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (70d33d7d-7b65-4b1c-a70a-6b9937722f82)
Mar 5 18:12:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all accesspoints for updates
Mar 5 18:12:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices
Mar 5 18:12:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Mar 5 18:12:09 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Mar 5 18:12:09 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Mar 5 18:12:09 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000
Mar 5 18:12:09 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Mar 5 18:12:09 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (c81562f4-a7ef-4e0b-8950-9e121d141109)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (df5e3eb6-c5ed-4725-b7cf-09ec3ba18177)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (4e191fc8-238e-441d-8bd8-dd380aa80675)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (3993d778-c43b-4cd3-8e95-fba63d326781)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (86e7161b-41cf-4567-94ad-e67f890f6e58)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (9e042a01-f85d-4eb9-9dc1-d48813e9bf9a)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DiagramRequestWorker succeeded (0d2eaa56-c7df-4f1f-b6b1-248fa40597f2)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (61ec7da1-a4f8-4b67-9d24-a9438098ed02)
Mar 5 18:12:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (f6b17b08-90d7-40ff-b412-484245dc459d)
Mar 5 18:12:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (f32f6cc6-b660-4cf0-81f0-4154167c72e1)
Mar 5 18:12:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Mar 5 18:12:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292
Mar 5 18:12:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration
Mar 5 18:12:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher
Mar 5 18:12:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache
Mar 5 18:12:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler
Mar 5 18:12:12 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing...
Mar 5 18:12:12 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Mar 5 18:12:12 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Mar 5 18:12:12 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device
Mar 5 18:12:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler
Mar 5 18:12:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler
Mar 5 18:12:13 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Mar 5 18:12:13 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished
Mar 5 18:12:13 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: HmIP-RF_java
Mar 5 18:12:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done
Mar 5 18:12:26 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Mar 5 18:12:26 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] Added InterfaceId: 1236
Mar 5 18:12:26 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Mar 5 18:12:26 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-11] updateDevicesForClient -> 9 device addresses will be added
Mar 5 18:12:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Mar 5 18:12:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished
Mar 5 18:12:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: 15833
Mar 5 18:12:36 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-11] set ready config of HU-Hue iris 1
Mar 5 18:12:36 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-11] set ready config of HU-Extended co
Mar 5 18:12:36 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-11] set ready config of HU-Hue white l
pi@raspberrypi:~ $

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.41.11-17
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  RPI-RF-MOD
HMIP Hardware:  RPI-RF-MOD
Board serial:   58A992F7B6
Radio MAC:      unknown
SGTIN:          3014F711A0001F58A992F7B6
State:          RUNNING
PID:            678
IP:             192.168.178.8
CPU use:        29.98 seconds
BlkIO use:      52.05 MiB
Link:           vethpivccu
 TX bytes:      305.30 KiB
 RX bytes:      864.93 KiB
 Total bytes:   1.14 MiB

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/messages
Mar  5 18:11:20 piVCCU syslog.info syslogd started: BusyBox v1.28.4
Mar  5 18:11:20 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Mar  5 18:11:22 piVCCU syslog.info syslogd exiting
Mar  5 18:11:22 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4
Mar  5 18:11:22 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Mar  5 18:11:22 ccu3-webui daemon.err udhcpc[164]: started, v1.28.4
Mar  5 18:11:22 ccu3-webui daemon.err udhcpc[164]: sending discover
Mar  5 18:11:22 ccu3-webui daemon.err udhcpc[164]: sending select for 192.168.178.8
Mar  5 18:11:22 ccu3-webui daemon.err udhcpc[164]: lease of 192.168.178.8 obtained, lease time 2147483
Mar  5 18:11:23 ccu3-webui user.info firewall: iptables v1.6.2: invalid port/service `310000' specified Try `iptables -h' or 'iptables --help' for more information.
Mar  5 18:11:23 ccu3-webui user.info firewall: ip6tables v1.6.2: invalid port/service `310000' specified Try `ip6tables -h' or 'ip6tables --help' for more information.
Mar  5 18:11:23 ccu3-webui user.info firewall: configuration set
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: ifplugd 0.28 initializing.
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: Using interface eth0/4A:FC:0A:66:54:CC with driver <veth> (version: 1.0)
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: Using detection mode: SIOCETHTOOL
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: Initialization complete, link beat detected.
Mar  5 18:11:23 ccu3-webui daemon.warn ifplugd(eth0)[267]: Could not open /dev/tty, cannot beep.
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Mar  5 18:11:23 ccu3-webui daemon.warn ifplugd(eth0)[267]: client: ifup: interface eth0 already configured
Mar  5 18:11:23 ccu3-webui daemon.info ifplugd(eth0)[267]: Program executed successfully.
Mar  5 18:11:29 ccu3-webui daemon.notice ntpdate[275]: step time server 192.168.178.1 offset -0.000435 sec
Mar  5 18:11:29 ccu3-webui daemon.notice ntpd[276]: ntpd 4.2.8p11@1.3728-o Mon Nov 12 09:31:16 UTC 2018 (1): Starting
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[276]: Command line: /usr/sbin/ntpd -g 192.168.178.1
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: proto: precision = 0.468 usec (-21)
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listen and drop on 0 v6wildcard [::]:123
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listen normally on 2 lo 127.0.0.1:123
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listen normally on 3 eth0 192.168.178.8:123
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listen normally on 4 lo [::1]:123
Mar  5 18:11:29 ccu3-webui daemon.info ntpd[278]: Listening on routing socket on fd #21 for interface updates
Mar  5 18:11:29 ccu3-webui daemon.err xinetd[297]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Mar  5 18:11:29 ccu3-webui daemon.crit xinetd[297]: 297 {init_services} no services. Exiting...
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write_pid /var/run/cuxd.pid [331]
Mar  5 18:11:29 ccu3-webui user.info homematic: started cux-daemon
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: CUx-Daemon(2.1.0) on CCU(3.41.11) start PID:331
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:591 update(-4199s):Tue Mar  5 17:01:30 2019
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: 1 device-paramset(s) loaded ok!
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write_proxy /var/cache/cuxd_proxy.ini (331 /usr/local/addons/cuxd/ 2.1.0 3.41.11 0)
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: add interface 'CUxD'
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write interface(1) 'BidCos-RF' to /usr/local/etc/config/InterfacesList.xml
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write interface(2) 'VirtualDevices' to /usr/local/etc/config/InterfacesList.xml
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write interface(3) 'HmIP-RF' to /usr/local/etc/config/InterfacesList.xml
Mar  5 18:11:29 ccu3-webui daemon.info cuxd[331]: write interface(4) 'CUxD' to /usr/local/etc/config/InterfacesList.xml
Mar  5 18:11:30 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Mar  5 18:11:30 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Mar  5 18:11:30 ccu3-webui user.info update-coprocessor: performGatewayCoproUpdate(): updating CCU2GW0001
Mar  5 18:11:32 ccu3-webui user.err update-coprocessor: Could not find gateway by unicast with ip 192.168.178.13. Trying search by serial number.
Mar  5 18:11:40 ccu3-webui user.err update-coprocessor: Could not find Lan Gateway using ip and serial number
Mar  5 18:11:40 ccu3-webui user.err update-coprocessor: UnifiedLanCommController::connect(): Unable to connect.
Mar  5 18:11:40 ccu3-webui user.err update-coprocessor: Could not connect to Lan Gateway ip: 192.168.178.13.
Mar  5 18:11:40 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Mar  5 18:11:40 ccu3-webui user.info update-lgw-firmware: LAN Gateway Firmware Update...
Mar  5 18:11:40 ccu3-webui user.info update-lgw-firmware: Gateway CCU2GW0001
Mar  5 18:11:42 ccu3-webui user.err update-lgw-firmware: Could not find gateway by unicast with ip 192.168.178.13. Trying search by serial number.
Mar  5 18:11:50 ccu3-webui user.err update-lgw-firmware: Could not find Lan Gateway using ip and serial number
Mar  5 18:11:50 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Mar  5 18:11:50 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Mar  5 18:11:50 ccu3-webui daemon.info snmpd[395]: Created directory: /var/lib/snmp
Mar  5 18:11:50 ccu3-webui daemon.info snmpd[395]: Created directory: /var/lib/snmp/cert_indexes
Mar  5 18:11:50 ccu3-webui daemon.info snmpd[395]: Created directory: /var/lib/snmp/mib_indexes
Mar  5 18:11:50 ccu3-webui daemon.info snmpd[395]: Turning on AgentX master support.
Mar  5 18:11:50 ccu3-webui daemon.err snmpd[395]: /etc/config/snmp/snmpd.conf: line 19: Error: Included file '/etc/config/snmp/snmpd-ccu3.conf' not found.
Mar  5 18:11:50 ccu3-webui daemon.info snmpd[397]: NET-SNMP version 5.7.3
Mar  5 18:11:50 ccu3-webui user.info kernel: [   43.971713] eq3loop: created slave mmd_hmip
Mar  5 18:11:50 ccu3-webui user.info kernel: [   43.972407] eq3loop: created slave mmd_bidcos
Mar  5 18:11:52 ccu3-webui user.info kernel: [   46.056993] eq3loop: eq3loop_open_slave() mmd_bidcos
Mar  5 18:12:06 ccu3-webui user.info kernel: [   60.498735] eq3loop: eq3loop_close_slave() mmd_hmip
Mar  5 18:12:06 ccu3-webui user.info kernel: [   60.502090] eq3loop: eq3loop_close_slave() mmd_hmip
Mar  5 18:12:06 ccu3-webui user.info kernel: [   60.512331] eq3loop: eq3loop_open_slave() mmd_hmip
Mar  5 18:12:06 ccu3-webui user.notice kernel: [   60.514897] eq3loop: eq3loop_ioctl_slave() mmd_hmip: unhandled ioctl 0x545D
Mar  5 18:12:11 ccu3-webui daemon.warn cuxd[331]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
Mar  5 18:12:13 ccu3-webui daemon.warn cuxd[331]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
Mar  5 18:12:29 ccu3-webui user.debug script: [ALCHY ALLINScript START]
Mar  5 18:12:29 ccu3-webui user.debug script: [ALCHY ALLINScript Abbruch BLOCK]
Mar  5 18:12:36 ccu3-webui daemon.info cuxd[331]: INIT 'xmlrpc_bin://127.0.0.1:31999' '1805'
Mar  5 18:12:36 ccu3-webui local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Mar  5 18:12:36 ccu3-webui local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=HM_VirtualInterface [iseRTHss.cpp:163]
Mar  5 18:12:36 ccu3-webui local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Mar  5 18:12:36 ccu3-webui local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=HVL [iseRTHss.cpp:163]
Mar  5 18:12:36 ccu3-webui user.warn rfd: XmlRpc transport failed (first try), retrying...
pi@raspberrypi:~ $

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/lighttpd-error.log
2019-03-05 18:26:12: (server.c.1430) server started (lighttpd/1.4.50)
2019-03-05 18:34:29: (server.c.2023) server stopped by UID = 0 PID = 306
2019-03-05 18:34:40: (server.c.1430) server started (lighttpd/1.4.50)
pi@raspberrypi:~ $

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-attach ps aux
PID   USER     TIME  COMMAND
    1 root      0:00 init
   85 root      0:00 /bin/hss_led -l 6
  129 dbus      0:00 dbus-daemon --system
  160 root      0:00 /sbin/syslogd -n -m 0
  162 root      0:00 /sbin/klogd -n
  180 root      0:00 /sbin/udhcpc -b -t 100 -T 3 -S -x hostname:ccu3-webui -i eth0 -F ccu3-webui -V eQ3-CCU3 -s /bin/dhcp.script -p /var/run/udhcpc_eth0.pid
  267 root      0:00 /usr/sbin/ifplugd -i eth0 -fI -u0 -d10
  278 root      0:00 /usr/sbin/ntpd -g 192.168.178.1
  300 root      0:00 /bin/eq3configd
  313 root      0:00 /bin/ssdpd
  331 root      0:00 /usr/local/addons/cuxd/cuxd
  398 root      0:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -c /etc/config/snmp/snmpd.conf -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  410 root      0:00 /bin/multimacd -f /etc/multimacd.conf -l 4
  437 root      0:02 /bin/rfd -f /etc/config/rfd.conf -l 4
  463 root      0:20 java -Xmx128m -Dos.arch=arm -Dlog4j.configuration=file:///etc/config/log4j.xml -Dfile.encoding=ISO-8859-1 -Dgnu.io.rxtx.SerialPorts=/dev/mmd_hmip -jar /opt/HMServer/HMIPServer.jar /et
  476 root      0:00 tail -f /var/log/hmserver.log
  576 root      0:03 /bin/ReGaHss.community -f /etc/rega.conf -l 2
  591 root      0:00 /usr/sbin/crond -f -l 9
  914 root      0:00 /usr/sbin/lighttpd-angel -f /etc/lighttpd/lighttpd.conf -D
  915 root      0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
  960 root      0:00 ps aux
pi@raspberrypi:~ $
Jemand eine Idee was ich noch machen kann?

Danke und Gruß
piVCCU3/iobroker mit einigen Aktoren, Sensoren, Empfängern und Sendern.

wendy2702
Beiträge: 463
Registriert: 05.03.2014, 19:31
Hat sich bedankt: 1 Mal
Danksagung erhalten: 1 Mal

Re: PiVCCU 3.41.11-17 WEB-IF nicht erreichbar

Beitrag von wendy2702 » 05.03.2019, 18:48

OK.

Nach ca. 25 minuten nach dem letzten Reboot geht die Webseite wieder.

:shock:
piVCCU3/iobroker mit einigen Aktoren, Sensoren, Empfängern und Sendern.

nex
Beiträge: 10
Registriert: 01.03.2019, 17:53
Hat sich bedankt: 3 Mal

Re: PiVCCU 3.41.11-17 WEB-IF nicht erreichbar

Beitrag von nex » 09.03.2019, 13:49

Das Problem hatte ich auch schon nach einem reboot ohne so recht zu wissen wo es her kommt. Ich hatte nach ein bisschen stöbern hier im Forum aber das hier von Alex gefunden:

Code: Alles auswählen

sudo pivccu-attach /etc/init.d/S50lighttpd stop
sudo pivccu-attach /etc/init.d/S50lighttpd start
Damit wird der Webserver neu gestartet, für den fall das du das Problem nochmal haben solltest..

Antworten

Zurück zu „piVCCU“