Hm-rpc-Adapter stoppt rfd auf pivCCU2 nach BackItUp-Backup

Familienvater

Moin,

mein Handy hat mich die halbe Nacht "vollgelabbert", weil mir Homeputer CL Pushovers gesendet hat, weil Homeputer CL keine Events mehr bekommen hat. Ich hatte aber keine Lust aufzustehen, und habe deshalb erst heute morgen nachgeschaut, was los ist.

Zuerst das extern aufgezeichnete Syslog der CCU angeschaut, und nach rfd gefiltert, um 02:02:14 war der letzte Eintrag, ein Plattform-Init von hm-rpc.0. Also bei meinem ioBroker geschaut, der Adapter für HM war gelb, und der für HmIP auch (der für wired war grün), beide auf Pause gestellt, auf einmal flutscht es im Log und es geht weiter, als ob nichts gewesen wäre. Zig reconnects von meinem eigenen Logger, der keine PING-PONG-Antworten bekommen hat, und deswegen wohl alle x-Minuten einen Reconnect versucht hat, gepufferte Meldungen der letzten Stunden usw.

Im nach "rfd" gefilterten Syslog sieht das so aus:

Nov 11 02:02:13 ccu2 rfd: Event: NEQ0117515:2.CURRENT=120.000000
Nov 11 02:02:13 ccu2 rfd: Event: NEQ0117515:2.VOLTAGE=240.400000
Nov 11 02:02:13 ccu2 rfd: Event: NEQ0117515:2.FREQUENCY=49.980000
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:13  rfd: last message repeated 2 times
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:13 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Nov 11 02:02:14 ccu2 rfd: PlatformInit()
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support event
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support deleteDevices
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support listDevices
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support newDevices
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support system.listMethods
Nov 11 02:02:14 ccu2 rfd: hm-rpc.0 support system.multicall
Nov 11 09:25:37 ccu2 rfd: XmlRpc transport error calling listDevices({"hm-rpc.0"}) on binary://192.168.1.223:2001/RPC2:
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","JEQ0000162:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","JEQ0034152:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","JEQ0651409:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","JEQ0654661:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","KEQ0121890:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","KEQ1005927:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: ServiceEvent {"hm-rpc.0","MEQ0343941:0","UNREACH",true}
Nov 11 09:25:37 ccu2 rfd: Event: KEQ0508861:0.UNREACH=true
Nov 11 09:25:37 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Nov 11 09:25:37 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Nov 11 09:25:37 ccu2 rfd: Event: KEQ0508861:0.STICKY_UNREACH=true
Nov 11 09:25:37 ccu2 rfd: Event: NEQ0878689:0.UNREACH=true
Nov 11 09:25:37 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 2 events
Nov 11 09:25:37 ccu2 rfd: Event: NEQ0878689:0.STICKY_UNREACH=true
Nov 11 09:25:37 ccu2 rfd: Event: MEQ0007483:0.UNREACH=true
Nov 11 09:25:37 ccu2 rfd: XmlRpc transport failed (first try), retrying...
Nov 11 09:25:37 ccu2 rfd: Event: MEQ0007483:0.STICKY_UNREACH=true
Nov 11 09:25:37 ccu2 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events

Man erkennt unschwer, das zwischen 02:02:14 und 09:25:37 NICHTS vom rfd kam. Als erste Konsequenz habe ich jetzt den rfd- und auch den wired-Adapter auf XMLRPC umgestellt (auch im Hinblick auf ein Update irgendwann auf eine >=3.41.x Firmware), in der Hoffnung, das ioBroker damit den rfd nicht mehr "anhalten" kann. Ich glaube, das ganze könnte mir vor einigen Wochen schonmal mit dem wired-Daemon passiert sein, da ging auf einmal wired nicht mehr in HPCL, da habe ich das ganze aber als Fehler von HPCL abgetan.

Um 2 Uhr läuft täglich das "Standard-Backup" von BackItUp

Da ich nicht wirklich weiß, wieviel Vor-/Nachlauf vom ioBroker-Log sinnvoll ist, einfach mal zuviel davon:

2018-11-11 00:08:26.429 - info: web.0 ==>Connected system.user.admin from 192.168.1.138
2018-11-11 00:08:29.698 - info: web.0 <==Disconnect system.user.admin from 192.168.1.138 vis.0
2018-11-11 00:52:50.898 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:52:51.158 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:52:51.459 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:52:51.705 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:53:07.612 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:53:07.839 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:53:08.117 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:53:08.329 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 00:59:32.315 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 868554f3f3f749498a0a04a2d3030150
2018-11-11 00:59:32.543 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 868554f3f3f749498a0a04a2d3030150
2018-11-11 00:59:33.027 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 868554f3f3f749498a0a04a2d3030150
2018-11-11 00:59:33.059 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 868554f3f3f749498a0a04a2d3030150
2018-11-11 01:41:03.567 - info: host.vmiobroker Delete log file iobroker.2018-11-04.log
2018-11-11 01:52:57.690 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 01:52:58.086 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 01:52:58.473 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 01:52:58.701 - warn: alexa2.0 Please Restart Adapter. Non-Existing Device was returned: 05d76f7dd6ac433d85c69907d6d9744a
2018-11-11 02:00:41.584 - warn: web.0 Reconnection to DB.
2018-11-11 02:00:42.172 - warn: alexa2.0 Reconnection to DB.
2018-11-11 02:00:42.246 - warn: cloud.0 Reconnection to DB.
2018-11-11 02:00:42.606 - warn: cloud.0 Reconnection to DB.
2018-11-11 02:00:42.477 - warn: hm-rpc.2 Reconnection to DB.
2018-11-11 02:00:43.811 - warn: alexa2.0 Reconnection to DB.
2018-11-11 02:00:43.491 - warn: hm-rpc.2 Reconnection to DB.
2018-11-11 02:00:42.483 - warn: netatmo.0 Reconnection to DB.
2018-11-11 02:00:44.051 - warn: netatmo.0 Reconnection to DB.
2018-11-11 02:00:42.211 - warn: ping.0 Reconnection to DB.
2018-11-11 02:00:43.855 - warn: ping.0 Reconnection to DB.
2018-11-11 02:00:41.945 - warn: hm-rpc.1 Reconnection to DB.
2018-11-11 02:00:43.234 - warn: hm-rpc.1 Reconnection to DB.
2018-11-11 02:00:42.343 - warn: web.0 Reconnection to DB.
2018-11-11 02:00:44.168 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:00:44.453 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:00:45.033 - warn: backitup.0 Reconnection to DB.
2018-11-11 02:00:44.434 - warn: simple-api.0 Reconnection to DB.
2018-11-11 02:00:45.961 - warn: simple-api.0 Reconnection to DB.
2018-11-11 02:00:46.358 - warn: backitup.0 Reconnection to DB.
2018-11-11 02:00:44.305 - warn: hm-rega.0 Reconnection to DB.
2018-11-11 02:00:46.581 - warn: hm-rega.0 Reconnection to DB.
2018-11-11 02:00:57.180 - error: hm-rpc.2 already running
2018-11-11 02:00:57.257 - error: hm-rpc.0 already running
2018-11-11 02:00:57.892 - error: host.vmiobroker instance system.adapter.hm-rpc.2 terminated with code 7 (Adapter already running)
2018-11-11 02:00:57.018 - warn: yamaha.0 Reconnection to DB.
2018-11-11 02:00:57.703 - warn: yamaha.0 Reconnection to DB.
2018-11-11 02:00:58.052 - error: backitup.0 already running
2018-11-11 02:00:57.968 - info: host.vmiobroker Restart adapter system.adapter.hm-rpc.2 because enabled
2018-11-11 02:00:58.156 - error: alexa2.0 already running
2018-11-11 02:00:58.255 - error: hm-rpc.1 already running
2018-11-11 02:00:58.276 - error: hm-rega.0 already running
2018-11-11 02:00:58.426 - error: cloud.0 already running
2018-11-11 02:00:58.512 - error: host.vmiobroker instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:58.512 - info: host.vmiobroker Restart adapter system.adapter.javascript.0 because enabled
2018-11-11 02:00:58.524 - error: host.vmiobroker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:58.524 - info: host.vmiobroker Restart adapter system.adapter.hm-rpc.0 because enabled
2018-11-11 02:00:59.182 - error: host.vmiobroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.221 - error: netatmo.0 already running
2018-11-11 02:00:59.199 - info: host.vmiobroker Restart adapter system.adapter.backitup.0 because enabled
2018-11-11 02:00:59.202 - error: host.vmiobroker instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.203 - info: host.vmiobroker Restart adapter system.adapter.hm-rega.0 because enabled
2018-11-11 02:00:59.207 - error: host.vmiobroker instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.207 - info: host.vmiobroker Restart adapter system.adapter.alexa2.0 because enabled
2018-11-11 02:00:59.211 - error: host.vmiobroker instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.211 - info: host.vmiobroker Restart adapter system.adapter.hm-rpc.1 because enabled
2018-11-11 02:00:59.401 - error: ping.0 already running
2018-11-11 02:00:59.446 - error: host.vmiobroker instance system.adapter.cloud.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.447 - info: host.vmiobroker Restart adapter system.adapter.cloud.0 because enabled
2018-11-11 02:00:59.448 - error: yamaha.0 already running
2018-11-11 02:00:59.441 - error: web.0 already running
2018-11-11 02:00:59.618 - error: host.vmiobroker instance system.adapter.ping.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.618 - info: host.vmiobroker Restart adapter system.adapter.ping.0 because enabled
2018-11-11 02:00:59.685 - error: host.vmiobroker instance system.adapter.netatmo.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:59.685 - info: host.vmiobroker Restart adapter system.adapter.netatmo.0 because enabled
2018-11-11 02:00:58.146 - warn: discovery.0 Reconnection to DB.
2018-11-11 02:00:59.881 - error: simple-api.0 already running
2018-11-11 02:01:00.062 - error: host.vmiobroker instance system.adapter.yamaha.0 terminated with code 7 (Adapter already running)
2018-11-11 02:01:00.062 - info: host.vmiobroker Restart adapter system.adapter.yamaha.0 because enabled
2018-11-11 02:01:00.065 - error: host.vmiobroker instance system.adapter.web.0 terminated with code 7 (Adapter already running)
2018-11-11 02:01:00.065 - info: host.vmiobroker Restart adapter system.adapter.web.0 because enabled
2018-11-11 02:00:59.304 - warn: discovery.0 Reconnection to DB.
2018-11-11 02:01:00.368 - error: discovery.0 already running
2018-11-11 02:01:00.399 - error: host.vmiobroker instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running)
2018-11-11 02:01:00.445 - info: host.vmiobroker Restart adapter system.adapter.simple-api.0 because enabled
2018-11-11 02:01:00.661 - error: host.vmiobroker instance system.adapter.discovery.0 terminated with code 7 (Adapter already running)
2018-11-11 02:01:00.661 - info: host.vmiobroker Restart adapter system.adapter.discovery.0 because enabled
2018-11-11 02:00:58.770 - warn: broadlink2.0 Reconnection to DB.
2018-11-11 02:01:00.247 - warn: broadlink2.0 Reconnection to DB.
2018-11-11 02:01:00.843 - error: broadlink2.0 already running
2018-11-11 02:01:01.060 - error: host.vmiobroker instance system.adapter.broadlink2.0 terminated with code 7 (Adapter already running)
2018-11-11 02:01:01.066 - info: host.vmiobroker Restart adapter system.adapter.broadlink2.0 because enabled
2018-11-11 02:01:29.805 - info: host.vmiobroker instance system.adapter.hm-rpc.2 started with pid 17842
2018-11-11 02:01:29.878 - info: host.vmiobroker instance system.adapter.javascript.0 started with pid 17843
2018-11-11 02:01:29.984 - info: host.vmiobroker instance system.adapter.hm-rpc.0 started with pid 17849
2018-11-11 02:01:30.041 - info: host.vmiobroker instance system.adapter.backitup.0 started with pid 17852
2018-11-11 02:01:30.261 - info: host.vmiobroker instance system.adapter.hm-rega.0 started with pid 17856
2018-11-11 02:01:30.338 - info: host.vmiobroker instance system.adapter.alexa2.0 started with pid 17867
2018-11-11 02:01:30.388 - info: host.vmiobroker instance system.adapter.hm-rpc.1 started with pid 17874
2018-11-11 02:01:30.687 - info: host.vmiobroker instance system.adapter.cloud.0 started with pid 17879
2018-11-11 02:01:30.862 - info: host.vmiobroker instance system.adapter.ping.0 started with pid 17885
2018-11-11 02:01:31.052 - info: host.vmiobroker instance system.adapter.netatmo.0 started with pid 17886
2018-11-11 02:01:31.624 - info: host.vmiobroker instance system.adapter.yamaha.0 started with pid 17902
2018-11-11 02:01:31.762 - info: host.vmiobroker instance system.adapter.web.0 started with pid 17903
2018-11-11 02:01:32.534 - info: host.vmiobroker instance system.adapter.simple-api.0 started with pid 17904
2018-11-11 02:01:32.572 - info: host.vmiobroker instance system.adapter.discovery.0 started with pid 17915
2018-11-11 02:01:32.790 - info: host.vmiobroker instance system.adapter.broadlink2.0 started with pid 17920
2018-11-11 02:01:56.831 - info: hm-rpc.0 starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.4
2018-11-11 02:02:00.308 - error: netatmo.0 no connection to objects DB
2018-11-11 02:02:01.463 - error: broadlink2.0 no connection to objects DB
2018-11-11 02:02:02.335 - error: discovery.0 no connection to states DB: Connection timeout
2018-11-11 02:02:02.535 - error: simple-api.0 no connection to states DB: Connection timeout
2018-11-11 02:02:02.828 - error: backitup.0 no connection to objects DB
2018-11-11 02:02:04.509 - error: alexa2.0 no connection to objects DB
2018-11-11 02:02:05.409 - error: web.0 no connection to objects DB
2018-11-11 02:02:06.006 - info: hm-rpc.1 starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.4
2018-11-11 02:02:08.832 - info: ping.0 starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.ping, node: v6.14.4
2018-11-11 02:02:08.822 - info: hm-rpc.2 starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.4
2018-11-11 02:02:01.613 - info: hm-rega.0 starting. Version 1.7.1 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.14.4
2018-11-11 02:02:01.645 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2018-11-11 02:02:09.578 - info: hm-rega.0 ReGaHSS 192.168.1.11 up
2018-11-11 02:02:09.655 - info: hm-rega.0 time difference local-ccu 1s
2018-11-11 02:02:09.743 - info: hm-rega.0 added/updated 5 favorites to enum.favorites
2018-11-11 02:02:09.903 - info: hm-rega.0 added/updated functions to enum.functions
2018-11-11 02:02:10.112 - info: hm-rega.0 added/updated rooms to enum.rooms
2018-11-11 02:02:10.806 - info: simple-api.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.simple-api, node: v6.14.4
2018-11-11 02:02:10.863 - info: simple-api.0 simpleAPI server listening on port 8087
2018-11-11 02:02:10.863 - info: simple-api.0 Allow states only when user is owner: false
2018-11-11 02:02:11.126 - info: simple-api.0 http server listening on port 8087
2018-11-11 02:02:12.101 - warn: ping.0 please update js-controller to at least 1.2.0
2018-11-11 02:02:13.231 - info: netatmo.0 starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.netatmo, node: v6.14.4
2018-11-11 02:02:13.259 - error: web.0 setObject id missing!!
2018-11-11 02:02:13.260 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.1.223:2000
2018-11-11 02:02:13.279 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.1.11:2000 with ["xmlrpc_bin://192.168.1.223:2000","hm-rpc.1"]
2018-11-11 02:02:13.286 - info: broadlink2.0 starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v6.14.4
2018-11-11 02:02:13.262 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.14.4
2018-11-11 02:02:13.301 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
2018-11-11 02:02:13.321 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
2018-11-11 02:02:13.326 - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v6.14.4
2018-11-11 02:02:14.543 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.1.223:2001
2018-11-11 02:02:14.544 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.1.11:2001 with ["xmlrpc_bin://192.168.1.223:2001","hm-rpc.0"]
2018-11-11 02:02:14.697 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
2018-11-11 02:02:14.742 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
2018-11-11 02:02:15.339 - info: netatmo.0 Registering realtime events with https://iobroker.herokuapp.com/netatmo/
2018-11-11 02:02:18.310 - error: hm-rpc.1 init error: Error: response timeout
2018-11-11 02:02:19.668 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:02:23.376 - info: alexa2.0 starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v6.14.4
2018-11-11 02:02:23.433 - info: hm-rpc.1 binrpc -> 311 devices
2018-11-11 02:02:23.459 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:02:23.472 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:02:23.496 - warn: hm-rega.0 Reconnection to DB.
2018-11-11 02:02:23.501 - warn: hm-rega.0 Reconnection to DB.
2018-11-11 02:02:23.794 - info: hm-rpc.1 Connected
2018-11-11 02:02:23.855 - info: backitup.0 starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.backitup, node: v6.14.4
2018-11-11 02:02:23.782 - warn: hm-rpc.2 Reconnection to DB.
2018-11-11 02:02:24.082 - warn: hm-rpc.2 Reconnection to DB.
2018-11-11 02:02:24.472 - error: hm-rega.0 already running
2018-11-11 02:02:24.478 - info: cloud.0 starting. Version 2.6.2 in /opt/iobroker/node_modules/iobroker.cloud, node: v6.14.4
2018-11-11 02:02:24.578 - info: backitup.0 [minimal] backup was activated at 02:00 every 1 day(s)
2018-11-11 02:02:24.614 - info: backitup.0 [ccu] backup was activated at 01:30 every 3 day(s)
2018-11-11 02:02:24.773 - error: host.vmiobroker instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:24.773 - info: host.vmiobroker Restart adapter system.adapter.hm-rega.0 because enabled
2018-11-11 02:02:24.809 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.14.4
2018-11-11 02:02:24.862 - info: javascript.0 requesting all states
2018-11-11 02:02:24.863 - info: javascript.0 requesting all objects
2018-11-11 02:02:25.335 - info: web.0 socket.io server listening on port 8082
2018-11-11 02:02:25.337 - info: web.0 http server listening on port 8082
2018-11-11 02:02:26.313 - info: cloud.0 Connecting with https://iobroker.pro:10555 with "@pro_christian.salzer@gmail.com_9325d180-e25b-11e7-86ee-214f5496"
2018-11-11 02:02:26.326 - info: yamaha.0 starting. Version 0.3.19 in /opt/iobroker/node_modules/iobroker.yamaha, node: v6.14.4
2018-11-11 02:02:31.693 - error: yamaha.0 Can not connect to yamaha receiver at 192.168.1.48 ETIMEDOUT
2018-11-11 02:02:32.034 - info: web.0 ==>Connected system.user.admin from 192.168.1.138
2018-11-11 02:02:32.691 - info: javascript.0 received all states
2018-11-11 02:02:34.490 - info: web.0 ==>Connected system.user.admin from 192.168.1.138
2018-11-11 02:02:34.499 - info: web.0 <==Disconnect system.user.admin from 192.168.1.138 vis.0
2018-11-11 02:02:40.884 - error: backitup.0 already running
2018-11-11 02:02:40.939 - error: host.vmiobroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:40.940 - info: host.vmiobroker Restart adapter system.adapter.backitup.0 because enabled
2018-11-11 02:02:40.949 - error: alexa2.0 already running
2018-11-11 02:02:41.412 - error: host.vmiobroker instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:41.413 - info: host.vmiobroker Restart adapter system.adapter.alexa2.0 because enabled
2018-11-11 02:02:41.425 - error: cloud.0 Error while connecting to cloud: Error: websocket error
2018-11-11 02:02:41.646 - error: yamaha.0 already running
2018-11-11 02:02:41.685 - error: Caught by controller[0]: { Error: connect EHOSTUNREACH 192.168.1.48:80
2018-11-11 02:02:41.685 - error: Caught by controller[0]: at Object.exports._errnoException (util.js:1020:11)
2018-11-11 02:02:41.685 - error: Caught by controller[0]: at exports._exceptionWithHostPort (util.js:1043:20)
2018-11-11 02:02:41.685 - error: Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)
2018-11-11 02:02:41.685 - error: Caught by controller[0]: code: 'EHOSTUNREACH',
2018-11-11 02:02:41.685 - error: Caught by controller[0]: errno: 'EHOSTUNREACH',
2018-11-11 02:02:41.685 - error: Caught by controller[0]: syscall: 'connect',
2018-11-11 02:02:41.685 - error: Caught by controller[0]: address: '192.168.1.48',
2018-11-11 02:02:41.686 - error: Caught by controller[0]: port: 80 }
2018-11-11 02:02:41.686 - error: host.vmiobroker instance system.adapter.yamaha.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:41.686 - info: host.vmiobroker Restart adapter system.adapter.yamaha.0 because enabled
2018-11-11 02:02:41.694 - error: netatmo.0 already running
2018-11-11 02:02:41.728 - error: web.0 already running
2018-11-11 02:02:41.732 - error: host.vmiobroker instance system.adapter.netatmo.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:41.745 - info: host.vmiobroker Restart adapter system.adapter.netatmo.0 because enabled
2018-11-11 02:02:41.749 - error: host.vmiobroker instance system.adapter.web.0 terminated with code 7 (Adapter already running)
2018-11-11 02:02:41.749 - info: host.vmiobroker Restart adapter system.adapter.web.0 because enabled
2018-11-11 02:02:41.978 - info: cloud.0 Trying to connect as system.user.admin
2018-11-11 02:02:45.460 - info: broadlink2.0 Discover UDP devices for 10sec on broadlink2.0
2018-11-11 02:02:48.580 - info: javascript.0 received all objects
2018-11-11 02:02:48.852 - info: javascript.0 Start javascript script.js.Alexa.wemos_openCarpet
2018-11-11 02:02:50.428 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:02:48.963 - info: javascript.0 script.js.Alexa.wemos_openCarpet: registered 1 subscription and 0 schedules
2018-11-11 02:02:48.963 - info: javascript.0 Start javascript script.js.Alexa.Fernsehschrank
2018-11-11 02:02:49.022 - info: javascript.0 script.js.Alexa.Fernsehschrank: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.030 - info: javascript.0 Start javascript script.js.Alexa.wemos_Farbverlauf(2)
2018-11-11 02:02:49.066 - info: javascript.0 script.js.Alexa.wemos_Farbverlauf(2): registered 1 subscription and 0 schedules
2018-11-11 02:02:49.084 - info: javascript.0 Start javascript script.js.Alexa.Fernsehlicht_weiss
2018-11-11 02:02:49.126 - info: javascript.0 script.js.Alexa.Fernsehlicht_weiss: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.135 - info: javascript.0 Start javascript script.js.Alexa.Fernsehlicht_langsam
2018-11-11 02:02:49.239 - info: javascript.0 script.js.Alexa.Fernsehlicht_langsam: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.247 - info: javascript.0 Start javascript script.js.Alexa.Beamer(2)
2018-11-11 02:02:49.288 - info: javascript.0 script.js.Alexa.Beamer(2): registered 1 subscription and 0 schedules
2018-11-11 02:02:49.288 - info: javascript.0 Start javascript script.js.Alexa.XELO_Syncrontuere_steuern
2018-11-11 02:02:49.338 - info: javascript.0 script.js.Alexa.XELO_Syncrontuere_steuern: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.339 - info: javascript.0 Start javascript script.js.Alexa.Digicorder_Wiedergabe(1)
2018-11-11 02:02:49.378 - info: javascript.0 script.js.Alexa.Digicorder_Wiedergabe(1): registered 1 subscription and 0 schedules
2018-11-11 02:02:49.385 - info: javascript.0 Start javascript script.js.Alexa.Digicorder_Programm_HochRunter
2018-11-11 02:02:49.463 - info: javascript.0 script.js.Alexa.Digicorder_Programm_HochRunter: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.464 - info: javascript.0 Start javascript script.js.Alexa.Garagentor
2018-11-11 02:02:49.540 - info: javascript.0 script.js.Alexa.Garagentor: registered 1 subscription and 0 schedules
2018-11-11 02:02:49.549 - info: javascript.0 Start javascript script.js.Logik.Durchflussmesser
2018-11-11 02:02:49.653 - info: javascript.0 script.js.Logik.Durchflussmesser: registered 1 subscription and 2 schedules
2018-11-11 02:02:49.666 - info: javascript.0 Start javascript script.js.Logik.Raumklima
2018-11-11 02:02:49.765 - info: javascript.0 script.js.Logik.Raumklima: Norden: kein Aussensensor angegeben. ### Messpunkte werden als Aussensensoren behandelt. ###
2018-11-11 02:02:49.892 - info: javascript.0 script.js.Logik.Raumklima: Norden_ALT: kein Aussensensor angegeben. ### Messpunkte werden als Aussensensoren behandelt. ###
2018-11-11 02:02:49.984 - info: javascript.0 script.js.Logik.Raumklima: Wetterstation: kein Aussensensor angegeben. ### Messpunkte werden als Aussensensoren behandelt. ###
2018-11-11 02:02:51.518 - info: javascript.0 script.js.Logik.Raumklima: Datenpunkte angelegt
2018-11-11 02:02:51.519 - info: javascript.0 script.js.Logik.Raumklima: registered 0 subscriptions and 1 schedule
2018-11-11 02:02:51.542 - info: javascript.0 Start javascript script.js.Logik.Windmesser
2018-11-11 02:02:51.641 - info: javascript.0 script.js.Logik.Windmesser: registered 1 subscription and 0 schedules
2018-11-11 02:02:51.679 - info: javascript.0 Start javascript script.js.Logik.Rauchrohr
2018-11-11 02:02:51.810 - info: javascript.0 script.js.Logik.Rauchrohr: registered 1 subscription and 0 schedules
2018-11-11 02:02:53.561 - info: javascript.0 script.js.Logik.Raumklima: Subscriptions angelegt: 42
2018-11-11 02:02:54.924 - info: host.vmiobroker instance system.adapter.hm-rega.0 started with pid 17998
2018-11-11 02:02:55.252 - warn: broadlink2.0 device RM:rm_mini3_wz not found, please rescan later again or delete it! It was: 192.168.1.59,IPv4,80,128,10039,rm,RM:rm_mini3_wz,RM Mini,37:27:3b:1:a8:c0
2018-11-11 02:02:55.262 - warn: broadlink2.0 device RM:rm_pro_wz not found, please rescan later again or delete it! It was: 192.168.1.60,IPv4,80,128,10119,rm,RM:rm_pro_wz,RM2 Pro Plus2,87:27:3c:1:a8:c0
2018-11-11 02:02:55.443 - info: broadlink2.0 Adapter broadlink2.0 started and found 0 devices named ''.
2018-11-11 02:02:55.454 - info: broadlink2.0 2 were not found: RM:rm_mini3_wz,RM:rm_pro_wz
2018-11-11 02:02:58.256 - info: hm-rega.0 starting. Version 1.7.1 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.14.4
2018-11-11 02:02:58.298 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2018-11-11 02:03:02.582 - info: hm-rega.0 ReGaHSS 192.168.1.11 up
2018-11-11 02:03:02.612 - info: hm-rega.0 time difference local-ccu 1s
2018-11-11 02:03:02.701 - info: hm-rega.0 added/updated 5 favorites to enum.favorites
2018-11-11 02:03:03.054 - info: hm-rega.0 added/updated functions to enum.functions
2018-11-11 02:03:03.410 - info: hm-rega.0 added/updated rooms to enum.rooms

Hier noch mal das ioBroker-Log nur nach hm-rpc.0 gefiltert:

2018-11-11 02:00:44.168 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:00:44.453 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:00:57.257 - error: hm-rpc.0 already running
2018-11-11 02:00:58.524 - error: host.vmiobroker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
2018-11-11 02:00:58.524 - info: host.vmiobroker Restart adapter system.adapter.hm-rpc.0 because enabled
2018-11-11 02:01:29.984 - info: host.vmiobroker instance system.adapter.hm-rpc.0 started with pid 17849
2018-11-11 02:01:56.831 - info: hm-rpc.0 starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.4
2018-11-11 02:02:01.645 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2018-11-11 02:02:14.543 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.1.223:2001
2018-11-11 02:02:14.544 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.1.11:2001 with ["xmlrpc_bin://192.168.1.223:2001","hm-rpc.0"]
2018-11-11 02:02:14.697 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
2018-11-11 02:02:14.742 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
2018-11-11 02:02:19.668 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:02:23.459 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:02:23.472 - warn: hm-rpc.0 Reconnection to DB.
2018-11-11 02:02:50.428 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:02:58.298 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2018-11-11 02:03:03.906 - info: hm-rega.0 renamed hm-rpc.0.JEQ0651409.0.UNREACH_ALARM to "UG_Power_FHZ2000:0.UNREACH_ALARM"
... jedemenge von den Meldungen ...
2018-11-11 02:03:06.640 - info: hm-rega.0 renamed hm-rpc.0.JEQ0738898.0.CONFIG_PENDING_ALARM to "BM Haustuer ALT:0.CONFIG_PENDING_ALARM"
2018-11-11 02:03:20.442 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:03:50.440 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:04:20.441 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 02:04:50.454 - error: hm-rpc.0 init error: Error: response timeout
... alle 30 Sekunden ...
2018-11-11 09:24:57.115 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 09:25:27.126 - error: hm-rpc.0 init error: Error: response timeout
2018-11-11 09:25:36.886 - info: host.vmiobroker object change system.adapter.hm-rpc.0
2018-11-11 09:25:36.887 - info: host.vmiobroker stopInstance system.adapter.hm-rpc.0
2018-11-11 09:25:37.891 - info: host.vmiobroker stopInstance timeout "1000 system.adapter.hm-rpc.0 killing pid 17849
2018-11-11 09:25:37.892 - info: hm-rpc.0 binrpc -> 192.168.1.11:2001 init ["xmlrpc_bin://192.168.1.223:2001",""]
2018-11-11 09:25:37.897 - info: hm-rpc.0 terminating
2018-11-11 09:25:37.915 - info: host.vmiobroker instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
2018-11-11 09:31:46.776 - info: host.vmiobroker object change system.adapter.hm-rpc.0
2018-11-11 09:32:09.953 - info: host.vmiobroker object change system.adapter.hm-rpc.0
2018-11-11 09:32:09.954 - info: host.vmiobroker "system.adapter.hm-rpc.0" enabled
2018-11-11 09:32:09.967 - info: host.vmiobroker instance system.adapter.hm-rpc.0 started with pid 21396
2018-11-11 09:32:10.375 - info: hm-rpc.0 starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.4
2018-11-11 09:32:10.757 - info: hm-rpc.0 xmlrpc server is trying to listen on 192.168.1.223:2001
2018-11-11 09:32:10.758 - info: hm-rpc.0 xmlrpc client is trying to connect to 192.168.1.11:2001 with ["http://192.168.1.223:2001","hm-rpc.0"]
2018-11-11 09:32:10.773 - info: hm-rpc.0 xmlrpc <- system.listMethods ["hm-rpc.0"]
2018-11-11 09:32:10.779 - info: hm-rpc.0 xmlrpc <- listDevices ["hm-rpc.0"]
2018-11-11 09:32:10.800 - info: hm-rpc.0 xmlrpc -> 680 devices
2018-11-11 09:32:11.103 - info: hm-rpc.0 Connected
2018-11-11 09:32:14.086 - info: hm-rega.0 renamed hm-rpc.0.JEQ0651409.0.UNREACH_ALARM to "UG_Power_FHZ2000:0.UNREACH_ALARM"
... jedemenge von den Meldungen ...
2018-11-11 09:32:16.332 - info: hm-rega.0 renamed hm-rpc.0.JEQ0738898.0.CONFIG_PENDING_ALARM to "BM Haustuer ALT:0.CONFIG_PENDING_ALARM"

Zum Schluss was zu den Versionen:

Host 1.4.2, ioBroker-Admin 3.5.10, hm-rpc 1.7.6, BackItUp 0.3.6, und ein paar andere, laut Admin sind alle installierten Adapter Up-To-Date, ioBroker läuft auf einer virtuellen Linux-Maschine und hat 2 GB Ram und 2 CPUs für sich, laut Admin-Oberfläche hat er normalerweise so um 1 GB an Ram-Nutzung, und es sind noch ca. 500 MB frei.

piVCCU2 2.31.25 läuft auf einem Raspi 3, und macht eigentlich keinerlei Ärger.

Irgendwelche Ideen?

Danke,

der Familienvater

Mikewolf

Hallo schau mal was unter callback Adresse steht im Adapter ,

Bei älteren inst steht meisten nix drinnen , und bei neueren muss zwingend eine callback Adresse angegeben werden

Seit ich diese auf meinen 2 iobroker Installationen eingestellt habe hatte ich keine Probs mehr mit den Rpc Adaptern

Mit freundlichen Grüßen

Mikewolf

Gesendet von iPhone mit Tapatalk

Familienvater

Hi,

die Adapter-Callback-Adresse ist leer, aber wenn ich mir die Beschreibung anschaue, dann wüsste ich nicht, was ich warum eintragen soll, die IP der virtuellen Maschine ist direkt aus dem Netzwerk erreichbar, da ist nichts dazwischen, was reverse NAT oder so bräuchte.

Der Familienvater

Mikewolf

Hallo ,

Bei mir habe ich Adresse vom iobroker drinnen,

Ohne gehts mittlerweile ja nimmer.

Wenn du nen neuen Rpc Adapter installierst lässt sich

Dieser ohne callback Adresse nicht mehr aktivieren

Bei mir auch in ner vm ohne nat

Seitdem läufst

Mit freundlichen Grüßen

Gesendet von iPhone mit Tapatalk

NEWS

Hm-rpc-Adapter stoppt rfd auf pivCCU2 nach BackItUp-Backup

Support us

745
Online

31.6k
Users

79.5k
Topics

1.3m
Posts

NEWS

Hm-rpc-Adapter stoppt rfd auf pivCCU2 nach BackItUp-Backup

Support us

745Online

31.6kUsers

79.5kTopics

1.3mPosts

745
Online

31.6k
Users

79.5k
Topics

1.3m
Posts