search

alexreinert / piVCCU

piVCCU is a project to install the original Homematic CCU3 firmware inside a virtualized container (lxc) on ARM based single board computers.
Apache License 2.0
306 stars 65 forks source link

reset piVCCU3 after power loss and play back backup #134

Closed fah closed 5 years ago

fah commented 5 years ago

Hallo Alex,

ich hatte einen Stromausfall. Dabei ist der Wirtsrechner anscheinend unbeschadet geblieben. Das vccu3 image meldet sich noch aber der Web server und die Service Endpunkte reagieren nicht mehr.

 $ 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:   58A9A12345
Radio MAC:      unknown
SGTIN:          3014F711A0001F58A9A12345
State:          RUNNING
PID:            690
IP:             192.168.123.123
CPU use:        52.60 seconds
BlkIO use:      46.20 MiB
Link:           vethpivccu
 TX bytes:      104.99 KiB
 RX bytes:      5.50 MiB
 Total bytes:   5.60 MiB

Meine Idee wäre

  1. Ein Backup mit deinem Script zu erzeugen. (erledigt)
  2. Das defekte vccu3 image zu ersetzen. (keine Ahnung wie das geht)
  3. Das Backup zurück zu spielen. (keine Ahnung wie das geht)

Was denkst Du?

Danke, Frank

alexreinert commented 5 years ago

Ich würde das System erstmal sauber runterfahren und ein Image der SD Karte machen sicher ist sicher. Dann nach dem Hochfahren 5 Minuten warten und dann schauen, warum die CCU nicht hochkommt:

sudo pivccu-attach cat /var/log/messages
sudo pivccu-attach cat /var/log/hmserver.log
fah commented 5 years ago

Sorry, musste Arbeiten.

$ sudo pivccu-attach cat /var/log/messages
Feb 17 16:37:55 piVCCU syslog.info syslogd started: BusyBox v1.28.4
Feb 17 16:37:55 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Feb 17 16:37:57 piVCCU syslog.info syslogd exiting
Feb 17 16:37:57 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4
Feb 17 16:37:57 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Feb 17 16:37:57 ccu3-webui daemon.err udhcpc[164]: started, v1.28.4
Feb 17 16:37:57 ccu3-webui daemon.err udhcpc[164]: sending discover
Feb 17 16:37:57 ccu3-webui daemon.err udhcpc[164]: sending select for 192.168.123.123
Feb 17 16:37:57 ccu3-webui daemon.err udhcpc[164]: lease of 192.168.123.123 obtained, lease time 2147483
Feb 17 16:37:58 ccu3-webui user.info kernel: [   19.127739] nf_conntrack version 0.5.0 (15360 buckets, 61440 max)
Feb 17 16:37:58 ccu3-webui user.info firewall: has ip6 1
Feb 17 16:37:59 ccu3-webui user.info firewall: configuration set
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: ifplugd 0.28 initializing.
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: Using interface eth0/AA:71:A0:FA:50:FF with driver <veth> (version: 1.0)
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: Using detection mode: SIOCETHTOOL
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: Initialization complete, link beat detected.
Feb 17 16:38:00 ccu3-webui daemon.warn ifplugd(eth0)[275]: Could not open /dev/tty, cannot beep.
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Feb 17 16:38:00 ccu3-webui daemon.warn ifplugd(eth0)[275]: client: ifup: interface eth0 already configured
Feb 17 16:38:00 ccu3-webui daemon.info ifplugd(eth0)[275]: Program executed successfully.
Feb 17 16:38:10 ccu3-webui daemon.notice ntpdate[283]: step time server 213.172.105.106 offset -0.426764 sec
Feb 17 16:38:10 ccu3-webui daemon.notice ntpd[284]: ntpd 4.2.8p11@1.3728-o Mon Nov 12 09:31:16 UTC 2018 (1): Starting
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[284]: Command line: /usr/sbin/ntpd -g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: proto: precision = 0.469 usec (-21)
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listen and drop on 0 v6wildcard [::]:123
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listen normally on 2 lo 127.0.0.1:123
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listen normally on 3 eth0 192.168.123.123:123
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listen normally on 4 lo [::1]:123
Feb 17 16:38:10 ccu3-webui daemon.info ntpd[286]: Listening on routing socket on fd #21 for interface updates
Feb 17 16:38:10 ccu3-webui daemon.err xinetd[305]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Feb 17 16:38:10 ccu3-webui daemon.crit xinetd[305]: 305 {init_services} no services. Exiting...
Feb 17 16:38:10 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Feb 17 16:38:10 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Feb 17 16:38:10 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Feb 17 16:38:10 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Feb 17 16:38:10 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Feb 17 16:38:10 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Feb 17 16:38:10 ccu3-webui user.warn kernel: [   31.786216] ICMPv6: process `snmpd' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.retrans_time - use net.ipv6.neigh.lo.retrans_time_ms instead
Feb 17 16:38:10 ccu3-webui daemon.info snmpd[360]: Created directory: /var/lib/snmp
Feb 17 16:38:10 ccu3-webui daemon.info snmpd[360]: Created directory: /var/lib/snmp/cert_indexes
Feb 17 16:38:10 ccu3-webui daemon.info snmpd[360]: Created directory: /var/lib/snmp/mib_indexes
Feb 17 16:38:10 ccu3-webui daemon.info snmpd[360]: Turning on AgentX master support.
Feb 17 16:38:10 ccu3-webui daemon.err snmpd[360]: /etc/config/snmp/snmpd.conf: line 20: Error: Included file '/etc/config/snmp/snmpd-ccu3.conf' not found.
Feb 17 16:38:10 ccu3-webui daemon.info snmpd[362]: NET-SNMP version 5.7.3
Feb 17 16:38:10 ccu3-webui user.info kernel: [   31.958307] eq3loop: created slave mmd_bidcos
Feb 17 16:38:13 ccu3-webui user.info kernel: [   34.146309] eq3loop: eq3loop_open_slave() mmd_bidcos
Feb 17 16:38:27 ccu3-webui user.info kernel: [   48.986155] eq3loop: eq3loop_open_slave() mmd_hmip
Feb 17 16:38:27 ccu3-webui user.info kernel: [   48.990481] eq3loop: eq3loop_close_slave() mmd_hmip
Feb 17 16:38:27 ccu3-webui user.info kernel: [   49.002073] eq3loop: eq3loop_open_slave() mmd_hmip
Feb 17 16:38:27 ccu3-webui user.notice kernel: [   49.004838] eq3loop: eq3loop_ioctl_slave() mmd_hmip: unhandled ioctl 0x545D
pi@hm-rpi:~ $ sudo pivccu-attach cat /var/log/hmserver.log
Feb 17 16:38:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Feb 17 16:38:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Feb 17 16:38:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Feb 17 16:38:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default 
Feb 17 16:38:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default 
Feb 17 16:38:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default 
Feb 17 16:38:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default 
Feb 17 16:38:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 21 classes to Vert.x 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 21 VertxDeployers initialized 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HMIPTRXWriterWorker succeeded (8252a724-6d07-4efe-97be-5075451498de) 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (3698f859-6166-4e56-ad5f-2de9f4493f0f) 
Feb 17 16:38:26 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (d5b2e9cf-a92a-4316-92be-8a0f07f730e9) 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (b1615f6e-2af1-4637-98dc-e672cde27b4b) 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CheckDeviceExistHandler succeeded (78eae689-7e74-456c-928e-8c053e2be447) 
Feb 17 16:38:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of KeyServerWorker succeeded (59bd7ff8-867a-4060-86a4-effbdca022cd) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of KryoPersistenceWorker succeeded (6e4c87f5-00dc-497e-8e98-343ca777c6c7) 
Feb 17 16:38:27 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: DeviceLiveUpdateSubsystem started 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of TransactionSubsystemHandler succeeded (c5d6af59-885e-4ad5-9e5b-d7b908115a94) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerPersistentDataLoader succeeded (08a6973b-d5f9-4d1b-a118-99879108cba6) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (5a1ac913-206e-4120-b23f-ecfd42192f6b) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (a071e5fc-e0d4-44f6-b0f0-9fac74d270c8) 
Feb 17 16:38:27 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-3] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of FirmwareLoaderFileSystem succeeded (c7ce2ab9-ac01-4a24-95a5-6f4320681f6f) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of IncomingHMIPFrameHandler succeeded (02d7392c-da13-42d1-b0ee-15050c948abf) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of BackendCommandHandler succeeded (fe120f95-08e7-468f-a07e-56a4ac32814d) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (9caba5d7-2e75-426d-9b88-0fc6cd3f7a81) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyNotificationHandler succeeded (44ff4282-f7ac-44cf-bbdd-b7dd74b7fa7d) 
Feb 17 16:38:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (f0369eb7-8823-49db-82e0-bbf4b60abd93) 
Feb 17 16:38:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerAdapterInitialization succeeded (a1dbfe31-b46e-410a-a685-d4f27dfcd248) 
Feb 17 16:38:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (c589eeef-5c72-4c6c-b3f6-dc01f5dedefb) 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12482224... 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A9A12345 to 3 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 3.4.8 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.34.0 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 4302848 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 4306769 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A9A12345 initialized 
Feb 17 16:38:28 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Feb 17 16:38:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyInitializion succeeded (2e236412-de5c-4fce-8f28-c7710cb269ce) 
Feb 17 16:38:29 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-2] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Feb 17 16:38:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (3c5ea59d-2ced-41c2-beb4-409874ccf032) 
Feb 17 16:38:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Checking all devices on all accesspoints for updates 
Feb 17 16:38:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: There are 0 APs queued with updatable devices 
Feb 17 16:38:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Feb 17 16:38:30 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Feb 17 16:38:30 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Feb 17 16:38:30 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Feb 17 16:38:30 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Feb 17 16:38:30 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendWorker succeeded (4f789ed5-fb1b-4614-b070-ffbe2e8ab3fd) 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (2bfeb356-ca28-46d7-a285-cd17b505b611) 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CouplingRequestWorker succeeded (cabe3990-eb41-4981-b4af-730070feabae) 
Feb 17 16:38:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of EnergyPriceRequestWorker succeeded (9944bbdf-8148-45a6-b40b-eeee6f426682) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of StorageRequestWorker succeeded (749457ec-d1b7-493b-8f8d-a297741afc4d) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (8614bca8-514e-40ce-afe9-5d5f480dd132) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (c0b1b16b-c66f-49cc-a9d3-a04a894eed46) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupRequestWorker succeeded (21c342b1-440f-4517-a64a-12bbaefe4197) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (f526cf65-c171-49c1-8f97-08b8f46da366) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (aedfb795-a330-4cbf-9176-791fbf57b042) 
Feb 17 16:38:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Feb 17 16:38:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Feb 17 16:38:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Feb 17 16:38:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Feb 17 16:38:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Feb 17 16:38:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Feb 17 16:38:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Feb 17 16:38:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Feb 17 16:38:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Feb 17 16:38:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Feb 17 16:38:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Feb 17 16:38:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Feb 17 16:38:34 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos 
Feb 17 16:38:34 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished 
Feb 17 16:38:34 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: HmIP-RF_java 
Feb 17 16:38:34 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-0] updateDevicesForClient HmIP-RF_java -> 12 device addresses will be added 
Feb 17 16:38:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Feb 17 16:38:44 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Feb 17 16:38:44 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] Added InterfaceId: 1008 
Feb 17 16:38:44 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Feb 17 16:38:54 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 
Feb 17 16:38:54 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Feb 17 16:38:54 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: 1009 
Feb 17 16:43:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Feb 17 16:43:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
....
Feb 18 08:03:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Feb 18 08:03:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Feb 18 08:03:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Feb 18 08:06:15 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-4] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:39292: Broken pipe (Write failed) 
Feb 18 08:06:15 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-4] Retrying request to {}->http://127.0.0.1:39292 
Feb 18 08:08:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Feb 18 08:08:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Feb 18 08:08:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
...
alexreinert commented 5 years ago

Da taucht jetzt erstmal kein Fehler auf.

Die Idee, die CCU neu zu installieren, könnte man aber au jeden Fall mal probueren:

sudo apt install --reinstall pivccu3

Dabei wird kein Werksreset gemacht, die Einstellungen bleiben also erhalten.

fah commented 5 years ago

Suuuuper! Alles wieder heile! :-) Vielen Dank!