[Gelöst] piVCCU läuft aber kein WEBUI für Backup

metaxa · Beitrag von **metaxa** » 24.03.2018, 11:40

Hallo!
Seit heute Nacht steht mein Haus still

- lief jetzt monatelang ohne Probleme. Dachte ich starte einmal den PI neu, dann wird wieder alles laufen. Leider nein, keine Webseite, keine Programme. Die LAN Gateways sind offenischtlich verbunden, da sie nicht blinken.

Wie kann ich ein CCU Backup OHNE webUI einspielen?
Bitte um Eure Hilfe!
LG, mxa

Pi3 mit Stretch:

Code: Alles auswählen

~ $ sudo pivccu-info
piVCCU version: 2.29.23-16
Kernel modules: Available
Raw UART dev:   Available
Board serial:   NEQ0229739
State:          RUNNING
PID:            4605
IP:             192.168.0.100
CPU use:        56.93 seconds
BlkIO use:      60.00 KiB
Link:           vethpivccu
 TX bytes:      980.65 KiB
 RX bytes:      281.07 KiB
 Total bytes:   1.23 MiB

Code: Alles auswählen

~ $ sudo pivccu-attach cat /var/log/messages
Mar 24 11:38:40 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Mar 24 11:38:40 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2017-10-11 14:29:35 CEST)
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: ifplugd 0.28 initializing.
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: Using interface eth0/4A:28:98:2B:5B:F6 with driver <veth> (version: 1.0)
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: Using detection mode: SIOCETHTOOL
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: Initialization complete, link beat detected.
Mar 24 10:38:40 homematic-ccu2 daemon.warn ifplugd(eth0)[121]: Could not open /dev/tty, cannot beep.
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Mar 24 10:38:40 homematic-ccu2 daemon.warn ifplugd(eth0)[121]: client: sysctl: error: 'net.ipv4.tcp_timestamps' is an unknown key
Mar 24 10:38:40 homematic-ccu2 daemon.warn ifplugd(eth0)[121]: client: eth0 carrier detected
Mar 24 10:38:40 homematic-ccu2 daemon.info ifplugd(eth0)[121]: Program executed successfully.
Mar 24 11:38:40 homematic-ccu2 user.debug setclock: Try to get time from pool.ntp.org
Mar 24 11:38:40 homematic-ccu2 user.debug setclock: Sat Mar 24 11:38:40 CET 2018
Mar 24 10:38:45 homematic-ccu2 auth.info sshd[203]: Server listening on 0.0.0.0 port 22.
Mar 24 10:38:45 homematic-ccu2 auth.info sshd[203]: Server listening on :: port 22.
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: write_pid /var/run/cuxd.pid [215]
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: CUx-Daemon(1.11a) on CCU(2.29.23) start PID:215
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:7634 update(-185s):Sat Mar 24 11:35:40 2018
Mar 24 11:38:45 homematic-ccu2 user.info homematic: started cux-daemon
Mar 24 10:38:45 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Mar 24 10:38:45 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: AUTOMOUNT system(mount -t nfs 192.168.0.98:/volume1/HomeMatic/piVCCU-Backup /mnt -o rw,nolock)
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: write_proxy /var/cache/cuxd_proxy.ini (215 /usr/local/addons/cuxd/ 1.11a 2.29.23 1)
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: add interface 'CUxD'
Mar 24 10:38:45 homematic-ccu2 user.info update-coprocessor: performGatewayCoproUpdate(): updating MEQ0181362
Mar 24 11:38:45 homematic-ccu2 daemon.info cuxd[215]: write 5 interfaces to /usr/local/etc/config/InterfacesList.xml
Mar 24 10:38:47 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: MEQ0181362
Mar 24 10:38:48 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: MEQ0181362
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: (MEQ0181362) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: (MEQ0181362) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Mar 24 10:38:49 homematic-ccu2 user.debug update-coprocessor: CoprocessorUpdate::startApplication():Coprocessor entered application.
Mar 24 10:38:50 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Mar 24 10:38:50 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Mar 24 10:38:50 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Mar 24 10:38:50 homematic-ccu2 user.info update-coprocessor: Version: 1.4.1
Mar 24 10:38:50 homematic-ccu2 user.info update-coprocessor: Coprocessor firmware not necessary.
Mar 24 10:38:50 homematic-ccu2 user.info update-coprocessor: performGatewayCoproUpdate(): updating KEQ1066472
Mar 24 11:38:50 homematic-ccu2 daemon.info cuxd[215]: INIT 'xmlrpc_bin://192.168.0.106:8701' 'hm-rpc.2'
Mar 24 10:38:52 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: KEQ1066472
Mar 24 10:38:52 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: KEQ1066472
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: (KEQ1066472) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: (KEQ1066472) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Mar 24 10:38:53 homematic-ccu2 user.debug update-coprocessor: CoprocessorUpdate::startApplication():Coprocessor entered application.
Mar 24 10:38:54 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Mar 24 10:38:54 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Mar 24 10:38:54 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Mar 24 10:38:54 homematic-ccu2 user.info update-coprocessor: Version: 1.4.1
Mar 24 10:38:54 homematic-ccu2 user.info update-coprocessor: Coprocessor firmware not necessary.
Mar 24 10:38:54 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Mar 24 10:38:54 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update...
Mar 24 10:38:54 homematic-ccu2 user.info update-lgw-firmware: Gateway MEQ0181362

Code: Alles auswählen

~ $ sudo pivccu-attach cat /var/log/hmserver.log
Mar 24 11:39:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Mar 24 11:39:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 18 classes to Vert.x
Mar 24 11:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 18 VertxDeployers initialized
Mar 24 11:39:22 de.eq3.cbcs.util.core.ServicePropertyHelper INFO  [vert.x-worker-thread-1] Property Network.Key not found in main config file. Alternative config file Network.Key.File not given either. Use default value...
Mar 24 11:39:22 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 24 11:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (35ec03e8-f4ba-4b44-ab07-6dfdf7e845dc)
Mar 24 11:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of KeyServerWorker succeeded (d4309902-231c-4c75-966c-e261b2d42596)
Mar 24 11:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (fda66d6a-b8d3-4d2b-a035-8125eaeba2ad)
Mar 24 11:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (8bd7c14a-f3c2-47cd-bc71-553209e51329)
Mar 24 11:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (bfc35df2-9f01-47a6-9717-0312f231ed12)
Mar 24 11:39:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (6f3d314b-4666-497d-8a6b-87fa39c8c488)
Mar 24 11:39:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (fdbe2572-0894-4a9a-9a27-c0f4323f2796)
Mar 24 11:39:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (8f145b89-16a7-4564-a5d5-a1a07389f23c)
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (1836c4e4-838b-467a-be4e-0f10c95f1b91)
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (53a34d67-d8ab-492d-866b-b069a0a2c8c7)
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of BackendCommandHandler succeeded (4458f3d6-4d9f-4d64-b60e-c6a17db51cfa)
Mar 24 11:39:24 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-9] SYSTEM: Firmware update directory is set to /etc/config/firmware
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (9d712924-d5d4-4962-a198-c3a43a3ceaa3)
Mar 24 11:39:24 de.eq3.cbcs.util.core.ServicePropertyHelper INFO  [vert.x-eventloop-thread-2] Property Network.Key not found in main config file. Alternative config file Network.Key.File not given either. Use default value...
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyBackendNotificationHandler succeeded (ce0554c2-ca36-4cb0-b295-2d2fb9e43682)
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyNotificationHandler succeeded (fc803ff8-6fd7-4c9e-a02f-4eccb492c22a)
Mar 24 11:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyAPIWorker succeeded (e8a96003-119f-4cb5-8007-779a6713f323)
Mar 24 11:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerAdapterInitialization succeeded (69b3ecd2-02b7-4eca-961a-dcba82193925)
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state: HMIP_TRX_App
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D5698CE96B to 3
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.5
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.2
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 30103552
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 30104865
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 1 link partners
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D5698CE96B initialized
Mar 24 11:39:25 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Mar 24 11:39:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (e2ec52e8-2342-4470-b8e6-9d99d00887c7)
Mar 24 11:39:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (f9533637-ec7c-4fee-86b7-41b7fd41b5e6)
Mar 24 11:39:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Mar 24 11:39:26 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Checking all devices on all accesspoints for updates
Mar 24 11:39:26 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: There are 0 APs queued with updatable devices
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default EventLoopPoolSize: 8
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 7 classes to Vert.x
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 7 VertxDeployers initialized
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendWorker succeeded (2d41d08f-f2ad-4cf7-bd65-7bdf685b9f06)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (332911e4-a8f9-400f-b738-43772eeefdf2)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (91fa0695-a31f-4daa-ac76-073917219de1)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (6055240e-b85c-4b46-ad92-3f6a0ba36033)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (cd8b9392-bc0b-4c57-b105-d35fb03606ab)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of GroupRequestWorker succeeded (0604e942-b019-4c55-94e9-601a40736737)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (52941259-7d97-42de-843d-8f43b22b5dbf)
Mar 24 11:39:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Read Configuration
Mar 24 11:39:31 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create Bidcos Dispatcher
Mar 24 11:39:32 de.eq3.ccu.server.HMServer INFO  [Thread-2] InitBidCosCache
Mar 24 11:39:34 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create groupDefinitionProvider
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHolder
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupAdministrationService
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceDispatcher
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceHandler
Mar 24 11:39:35 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing...
Mar 24 11:39:35 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Mar 24 11:39:35 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Mar 24 11:39:35 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCosGroupMemberProvider
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init groupAdministrationService
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init Virtual OS Device
Mar 24 11:39:35 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init ESHLight Bridge
Mar 24 11:39:36 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create RrdDatalogging
Mar 24 11:39:36 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create MeasurementService
Mar 24 11:39:36 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init MeasurementService
Mar 24 11:39:37 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create HTTP Server
Mar 24 11:39:37 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCos context and start handler
Mar 24 11:39:37 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create group context and start handler
Mar 24 11:39:37 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-19] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos
Mar 24 11:39:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java
Mar 24 11:39:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient HmIP-RF_java -> 3 device addresses will be added
Mar 24 11:39:38 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer done

Familienvater · Beitrag von **Familienvater** » 24.03.2018, 12:06

Hi,

auch bei Dir, entweder piVCCU updaten (und damit die Firmware auf 2.31.25 bringen), oder einfach bis morgen oder Montag warten, dann lüppt es wieder.

Der Familienvater

deimos · Beitrag von **deimos** » 24.03.2018, 12:15

Hi,

bei der alten Version gibt es leider noch keine Möglichkeit für ein Backup auf der Konsole. Es sollte aber problemlos gehen ein Update über apt einzuspielen, die Daten werden dabei übernommen. Vermutlich musst du aber nach dem Update einen Reboot vom ganzen Pi machen.

Viele Grüße
Alex

metaxa · Beitrag von **metaxa** » 24.03.2018, 12:18

Servus!
Ich glaubte das Forum nach Antworten ausführlich durchsucht zu haben, deswegen wundert mich deine Aussage jetzt total ?

Familienvater hat geschrieben:oder einfach bis morgen oder Montag warten, dann lüppt es wieder.

Kann/will leider nicht warten, der WAF fällt minütlich

Update:

Code: Alles auswählen

sudo apt update && sudo apt upgrade

in welchem Verzeichnis, direkt im root mit sudo?

LG, mxa

deimos · Beitrag von **deimos** » 24.03.2018, 12:31

Hi,

irgendwo, die Befehle liegen im Pfad.

Viele Grüße
Alex

Familienvater · Beitrag von **Familienvater** » 24.03.2018, 12:46

Hi,

metaxa hat geschrieben:Ich glaubte das Forum nach Antworten ausführlich durchsucht zu haben, deswegen wundert mich deine Aussage jetzt total ?

viewtopic.php?f=26&t=42887
viewtopic.php?f=26&t=42886
viewtopic.php?f=67&t=41421&start=60#p426758

Der Familienvater

metaxa · Beitrag von **metaxa** » 24.03.2018, 13:12

Servus Familienvater!
Oh, da habe ich offensichtlich nicht über den eigenen Tellerrand hinaus gesehen. War nur im Unterforum piVCCU unterwegs.
Danke!

Servus Alex!
Scheint alles wieder zu funktionieren - bin auf der v 2.31.25.

Lieben Dank Euch beiden!
mxa

HomeMatic-Forum / FHZ-Forum

[Gelöst] piVCCU läuft aber kein WEBUI für Backup

[Gelöst] piVCCU läuft aber kein WEBUI für Backup

Re: [Problem] piVCCU läuft aber kein WEBUI für Backup

Re: [Problem] piVCCU läuft aber kein WEBUI für Backup

Re: [Problem] piVCCU läuft aber kein WEBUI für Backup

Re: [Problem] piVCCU läuft aber kein WEBUI für Backup

Re: [Problem] piVCCU läuft aber kein WEBUI für Backup

Re: [Gelöst] piVCCU läuft aber kein WEBUI für Backup