Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter

Scheduled Pinned Locked Moved Unsolved Error/Bug
fhem.0
63 Posts 8 Posters 5.0k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Altersrentner

    Guten Morgen,
    Es ist für mich schon verwunderlich, das Zuständiger sich dieses Fehlers annimmt..
    Es gibt keinen Hinweis ob das

    2019-03-11 03:57:35.634 - warn: fhem.0 Reconnection to DB.
    2019-03-11 03:57:35.637 - warn: fhem.0 Reconnection to DB.
    

    normal ist bzw. wodurch die Unterbrechungen um 04:00 hervorgerufen werden.
    Heute war es wieder so weit. 04:00 wurde alles gestoppt und fhem.0 ist nich mehr gestartet.
    Abbruch 110319_0400.PNG

    9-03-11 03:57:35.634 - warn: fhem.0 Reconnection to DB.
    2019-03-11 03:57:35.637 - warn: fhem.0 Reconnection to DB.
    2019-03-11 03:57:35.643 - info: fhem.0 event ioBroker "fhem.0.VentilWandhzg_HK1.state_switch on" > set VentilWandhzg_HK1 on
    2019-03-11 03:57:35.663 - info: fhem.0 event ioBroker "fhem.0.VentilFussbodenhzg_Vorbau.state_switch on" > set VentilFussbodenhzg_Vorbau on
    2019-03-11 03:59:26.193 - info: fhem.0 event ioBroker "fhem.0.GewaechshausLED_Ventilation.state_switch on" > set GewaechshausLED_Ventilation on
    2019-03-11 03:59:27.195 - info: fhem.0 event ioBroker "fhem.0.Ventilation.state_switch on" > set Ventilation on
    2019-03-11 04:00:00.064 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 started with pid 14264
    2019-03-11 04:00:00.117 - info: host.ioBroker-RasPi instance system.adapter.daswetter.0 started with pid 14270
    2019-03-11 04:00:00.183 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 14275
    2019-03-11 04:00:01.181 - info: fhem.0 event ioBroker "fhem.0.VentilWandhzg_HK2.state_switch on" > set VentilWandhzg_HK2 on
    2019-03-11 04:00:02.100 - info: dwd.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:00:02.363 - info: dwd.0 starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v8.12.0
    2019-03-11 04:00:02.356 - debug: daswetter.0 objectDB connected
    2019-03-11 04:00:02.442 - info: host.ioBroker-RasPi received SIGTERM
    2019-03-11 04:00:02.420 - debug: daswetter.0 statesDB connected
    2019-03-11 04:00:02.467 - info: web.0 terminating http server on port 8082
    2019-03-11 04:00:02.455 - info: admin.0 terminating http server on port 8081
    2019-03-11 04:00:02.427 - info: daswetter.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:00:02.470 - info: web.0 terminated http server on port 8082
    2019-03-11 04:00:02.519 - info: web.0 terminating http server on port 8082
    2019-03-11 04:00:02.447 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
    2019-03-11 04:00:02.448 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 2802
    2019-03-11 04:00:02.448 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
    2019-03-11 04:00:02.449 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 killing pid 2825
    2019-03-11 04:00:02.449 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
    2019-03-11 04:00:02.450 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 2835
    2019-03-11 04:00:02.450 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
    2019-03-11 04:00:02.451 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 killing pid 2845
    2019-03-11 04:00:02.451 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
    2019-03-11 04:00:02.452 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 killing pid 2855
    2019-03-11 04:00:02.454 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
    2019-03-11 04:00:02.455 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
    2019-03-11 04:00:02.457 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
    2019-03-11 04:00:02.458 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 2922
    2019-03-11 04:00:02.459 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
    2019-03-11 04:00:02.460 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0 killing pid 2971
    2019-03-11 04:00:02.461 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
    2019-03-11 04:00:02.462 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 killing pid 27447
    2019-03-11 04:00:02.462 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
    2019-03-11 04:00:02.469 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 killing pid 2992
    2019-03-11 04:00:02.472 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
    2019-03-11 04:00:02.473 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 killing pid 3002
    2019-03-11 04:00:02.494 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
    2019-03-11 04:00:02.494 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 killing pid 3012
    2019-03-11 04:00:02.495 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
    2019-03-11 04:00:02.496 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 killing pid 3018
    2019-03-11 04:00:02.506 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
    2019-03-11 04:00:02.507 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 killing pid 3024
    2019-03-11 04:00:02.508 - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
    2019-03-11 04:00:02.508 - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
    2019-03-11 04:00:02.508 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
    2019-03-11 04:00:02.509 - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
    2019-03-11 04:00:02.509 - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
    2019-03-11 04:00:02.509 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
    2019-03-11 04:00:02.510 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 killing pid 3038
    2019-03-11 04:00:02.510 - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
    2019-03-11 04:00:02.511 - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
    2019-03-11 04:00:02.511 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
    2019-03-11 04:00:02.512 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
    2019-03-11 04:00:02.512 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
    2019-03-11 04:00:02.512 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
    2019-03-11 04:00:02.515 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.dwd.0
    2019-03-11 04:00:02.530 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
    2019-03-11 04:00:02.530 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 killing pid 3054
    2019-03-11 04:00:02.533 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
    2019-03-11 04:00:02.533 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
    2019-03-11 04:00:02.534 - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
    2019-03-11 04:00:02.534 - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
    2019-03-11 04:00:02.537 - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
    2019-03-11 04:00:02.538 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.daswetter.0
    2019-03-11 04:00:02.538 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
    2019-03-11 04:00:02.539 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.yr.0
    2019-03-11 04:00:02.539 - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
    2019-03-11 04:00:02.540 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.feiertage.0
    2019-03-11 04:00:02.541 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
    2019-03-11 04:00:02.541 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.0
    2019-03-11 04:00:02.541 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
    2019-03-11 04:00:02.541 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 killing pid 3144
    2019-03-11 04:00:02.542 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
    2019-03-11 04:00:02.542 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 killing pid 3150
    2019-03-11 04:00:02.524 - info: terminal.0 terminating http server on port 8088
    2019-03-11 04:00:02.675 - info: host.ioBroker-RasPi instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.825 - info: ical.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:00:02.766 - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.794 - info: host.ioBroker-RasPi instance system.adapter.discovery.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.827 - info: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.855 - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.880 - info: host.ioBroker-RasPi instance system.adapter.socketio.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.901 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.923 - info: host.ioBroker-RasPi instance system.adapter.cul.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.944 - info: host.ioBroker-RasPi instance system.adapter.javascript.1 terminated with code 0 (OK)
    2019-03-11 04:00:02.966 - info: host.ioBroker-RasPi instance system.adapter.mihome.0 terminated with code 0 (OK)
    2019-03-11 04:00:02.990 - info: host.ioBroker-RasPi instance system.adapter.terminal.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.019 - info: host.ioBroker-RasPi instance system.adapter.tr-064.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.046 - info: host.ioBroker-RasPi instance system.adapter.zigbee.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.073 - info: host.ioBroker-RasPi instance system.adapter.shelly.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.095 - info: host.ioBroker-RasPi instance system.adapter.fhem.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.117 - info: host.ioBroker-RasPi instance system.adapter.history.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.138 - info: host.ioBroker-RasPi instance system.adapter.scenes.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.160 - info: host.ioBroker-RasPi instance system.adapter.backitup.0 terminated with code 0 (OK)
    2019-03-11 04:00:03.176 - info: daswetter.0 starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.daswetter, node: v8.12.0
    2019-03-11 04:00:03.183 - debug: daswetter.0 set timeout to 60 sec
    2019-03-11 04:00:03.184 - debug: daswetter.0 using new data structure
    2019-03-11 04:00:03.190 - debug: daswetter.0 calling forecast hourly: http://api.daswetter.com/index.php?api_lang=de&localidad=99265&affiliate_id=1q78xxh7eqsc&v=2.0&h=1
    2019-03-11 04:00:03.325 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.12.0
    2019-03-11 04:00:03.913 - debug: daswetter.0 hourly forecast done, objects in list 1635
    2019-03-11 04:00:03.927 - info: ical.0 processing URL: calendar1 http://11111.ics
    2019-03-11 04:00:03.918 - debug: daswetter.0 objects in list: 1635
    2019-03-11 04:00:04.221 - info: ical.0 processing URL: Google Mond https://calendar.google.com/calendar/ical/ht3jlfaac5lfd6263ulfh4tql8%40group.calendar.google.com/public/basic.ics
    2019-03-11 04:00:04.367 - info: ical.0 processing URL: Google Michael https://calendar.google.com/calendar/ical/m-baer%40t-online.de/private-9fe4ff3cfa48c1d1dd33e5167dff0445/basic.ics
    2019-03-11 04:00:04.369 - info: ical.0 processing URL: Google https://calendar.google.com/calendar/ical/de.german%23holiday%40group.v.calendar.google.com/public/basic.ics
    2019-03-11 04:00:07.967 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 terminated with code 0 (OK)
    2019-03-11 04:00:08.409 - info: host.ioBroker-RasPi received SIGTERM
    2019-03-11 04:00:08.410 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
    2019-03-11 04:00:08.410 - warn: host.ioBroker-RasPi stopInstance system.adapter.admin.0 not running
    2019-03-11 04:00:08.410 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
    2019-03-11 04:00:08.411 - warn: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 not running
    2019-03-11 04:00:08.411 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
    2019-03-11 04:00:08.411 - warn: host.ioBroker-RasPi stopInstance system.adapter.web.0 not running
    2019-03-11 04:00:08.411 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
    2019-03-11 04:00:08.411 - warn: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 not running
    2019-03-11 04:00:08.411 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
    2019-03-11 04:00:08.411 - warn: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 not running
    2019-03-11 04:00:08.411 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
    2019-03-11 04:00:08.412 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
    2019-03-11 04:00:08.412 - warn: host.ioBroker-RasPi stopInstance system.adapter.history.0 not running
    2019-03-11 04:00:08.412 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
    2019-03-11 04:00:08.412 - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 not running
    2019-03-11 04:00:08.412 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
    2019-03-11 04:00:08.412 - warn: host.ioBroker-RasPi stopInstance system.adapter.cul.0 not running
    2019-03-11 04:00:08.412 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
    2019-03-11 04:00:08.412 - warn: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 not running
    2019-03-11 04:00:08.413 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
    2019-03-11 04:00:08.413 - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 not running
    2019-03-11 04:00:08.413 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
    2019-03-11 04:00:08.413 - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 not running
    2019-03-11 04:00:08.413 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
    2019-03-11 04:00:08.413 - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 not running
    2019-03-11 04:00:08.413 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
    2019-03-11 04:00:08.413 - warn: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 not running
    2019-03-11 04:00:08.413 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
    2019-03-11 04:00:08.414 - warn: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 not running
    2019-03-11 04:00:08.414 - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
    2019-03-11 04:00:08.414 - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
    2019-03-11 04:00:08.414 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
    2019-03-11 04:00:08.414 - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
    2019-03-11 04:00:08.414 - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
    2019-03-11 04:00:08.414 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
    2019-03-11 04:00:08.414 - warn: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 not running
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
    2019-03-11 04:00:08.415 - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
    2019-03-11 04:00:08.415 - warn: host.ioBroker-RasPi stopInstance system.adapter.dwd.0 not scheduled
    2019-03-11 04:00:08.415 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
    2019-03-11 04:00:08.416 - warn: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 not running
    2019-03-11 04:00:08.416 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
    2019-03-11 04:00:08.416 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
    2019-03-11 04:00:08.416 - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
    2019-03-11 04:00:08.416 - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
    2019-03-11 04:00:08.416 - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
    2019-03-11 04:00:08.416 - warn: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0 not scheduled
    2019-03-11 04:00:08.416 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
    2019-03-11 04:00:08.417 - warn: host.ioBroker-RasPi stopInstance system.adapter.yr.0 not scheduled
    2019-03-11 04:00:08.417 - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
    2019-03-11 04:00:08.417 - warn: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0 not scheduled
    2019-03-11 04:00:08.417 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
    2019-03-11 04:00:08.417 - warn: host.ioBroker-RasPi stopInstance system.adapter.ical.0 not scheduled
    2019-03-11 04:00:08.417 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
    2019-03-11 04:00:08.417 - warn: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 not running
    2019-03-11 04:00:08.417 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
    2019-03-11 04:00:08.418 - warn: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 not running
    2019-03-11 04:00:09.512 - debug: daswetter.0 nothing to do
    2019-03-11 04:00:09.530 - error: host.ioBroker-RasPi instance system.adapter.daswetter.0 terminated with code 11 ()
    2019-03-11 04:00:10.051 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
    2019-03-11 04:00:12.557 - info: host.ioBroker-RasPi force terminating
    2019-03-11 04:01:41.976 - info: host.ioBroker-RasPi iobroker.js-controller version 1.4.2 js-controller starting
    2019-03-11 04:01:41.983 - info: host.ioBroker-RasPi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
    2019-03-11 04:01:41.984 - info: host.ioBroker-RasPi hostname: ioBroker-RasPi, node: v8.11.3
    2019-03-11 04:01:41.988 - info: host.ioBroker-RasPi ip addresses: 192.168.178.144 2003:dc:9be7:1b00:8b6c:1663:3ea2:42b6 fe80::50e8:da28:a103:30a2
    2019-03-11 04:01:44.085 - info: host.ioBroker-RasPi inMem-objects listening on port 9001
    2019-03-11 04:01:44.110 - info: host.ioBroker-RasPi InMemoryDB connected
    2019-03-11 04:01:44.239 - info: host.ioBroker-RasPi 36 instances found
    2019-03-11 04:01:44.300 - info: host.ioBroker-RasPi starting 30 instances
    2019-03-11 04:01:44.392 - info: host.ioBroker-RasPi instance system.adapter.admin.0 started with pid 633
    2019-03-11 04:01:44.410 - info: host.ioBroker-RasPi States connected to redis: 127.0.0.1:6379
    2019-03-11 04:01:47.143 - info: admin.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:01:47.339 - error: admin.0 setObject id missing!!
    2019-03-11 04:01:47.350 - info: admin.0 starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v8.11.3
    2019-03-11 04:01:47.374 - info: admin.0 requesting all states
    2019-03-11 04:01:47.377 - info: admin.0 requesting all objects
    2019-03-11 04:01:47.379 - info: admin.0 Request actual repository...
    2019-03-11 04:01:49.953 - info: host.ioBroker-RasPi instance system.adapter.discovery.0 started with pid 644
    2019-03-11 04:01:53.075 - info: admin.0 received all states
    2019-03-11 04:01:53.112 - info: host.ioBroker-RasPi instance system.adapter.web.0 started with pid 651
    2019-03-11 04:01:54.002 - info: discovery.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:01:54.186 - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.11.3
    2019-03-11 04:01:55.107 - info: web.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:01:55.270 - error: web.0 setObject id missing!!
    2019-03-11 04:01:55.279 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.11.3
    2019-03-11 04:01:56.208 - info: web.0 socket.io server listening on port 8082
    2019-03-11 04:01:56.212 - info: web.0 http server listening on port 8082
    2019-03-11 04:01:56.318 - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 started with pid 665
    2019-03-11 04:01:57.322 - info: rpi2.0 States connected to redis: 127.0.0.1:6379
    2019-03-11 04:01:57.483 - info: rpi2.0 starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.rpi2, node: v8.11.3
    2019-03-11 04:01:58.119 - info: admin.0 received all objects
    

    Wer kann hier bitte helfen.
    Danke
    Gruß Michael

    HomoranH Do not disturb
    HomoranH Do not disturb
    Homoran
    Global Moderator Administrators
    wrote on last edited by
    #28

    @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

    node: v8.12.0

    Habe mal gesucht:
    wenn du das nicht zwischenzeitlich geändert hast hast du

    node: v8.12.0
    

    Das hat ein Speicherleck

    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

    AlCalzoneA 1 Reply Last reply
    0
    • LausiDL LausiD

      @Altersrentner
      Naja, laut deinen Zeiten ist es ja zu jeder vollen Stunde so.
      Sieht eher so aus als ob der Speicher Pi voll läuft.
      Falls du auf die 3 Adapter mal verzichten kannst würde ich mal deaktivieren.
      Du machst nach dem Crash um 04:00 Uhr jeweils ein Reboot vom Pi, oder?
      Machst du den Reboot jedesmal etwa zur gleichen Uhrzeit?
      Ist ioBroker und FHEM auf einem Pi?
      Deine Adapter sind bis auf den FHEM Adapter wohl auf dem aktuellen Stand.
      Gruß LausiD

      A Offline
      A Offline
      Altersrentner
      wrote on last edited by
      #29

      @LausiD Ich fange mal hinten an;
      Ja Fhem ist nicht aktualisiert, Fhem läuft auf einem anderen Pi und läuft ohne Probleme.
      Nicht immer ist ein Reboot des Pi/ iobroker notwendig. Manchmal reicht auch ein Neustart vom
      Fhem Adapter. Werde wie vorgeschlagen jetzt die drei Adapter deaktivieren.
      Mal sehen was das Log morgen zeigt.
      Danke
      Gruß Michael

      1 Reply Last reply
      0
      • W Wildbill

        Dito, auch 1.1.1 die im stable Repo als letzte drin ist.

        Gruss, Jürgen

        LausiDL Offline
        LausiDL Offline
        LausiD
        wrote on last edited by
        #30

        @Wildbill sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

        Dito, auch 1.1.1 die im stable Repo als letzte drin ist.

        Gruss, Jürgen

        Um den FHEM Adapter auszuschliessen würde ich wie die Kollegen oben mit Version 1.1.1 an den Start gehen.

        @Homoran sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

        @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

        node: v8.12.0

        Habe mal gesucht:
        wenn du das nicht zwischenzeitlich geändert hast hast du

        node: v8.12.0
        

        Das hat ein Speicherleck

        Solltest du auch beachten, habe hier node 8.15.1 im Einsatz

        Gruß
        LausiD

        Doku zum FHEM Adapter
        Aktuelles zum FHEM Adapter
        Test FHEM Adapter

        A 1 Reply Last reply
        0
        • HomoranH Homoran

          @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

          node: v8.12.0

          Habe mal gesucht:
          wenn du das nicht zwischenzeitlich geändert hast hast du

          node: v8.12.0
          

          Das hat ein Speicherleck

          AlCalzoneA Offline
          AlCalzoneA Offline
          AlCalzone
          Developer
          wrote on last edited by
          #31

          @Homoran sagte in [Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in

          node: v8.12.0
          

          Das hat ein Speicherleck

          Stimmt nicht. 8.12 behebt das Leck.
          Außerdem äußert sich das Leck nicht so regelmäßig um eine bestimmte Uhrzeit.

          Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

          HomoranH 1 Reply Last reply
          0
          • AlCalzoneA AlCalzone

            @Homoran sagte in [Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in

            node: v8.12.0
            

            Das hat ein Speicherleck

            Stimmt nicht. 8.12 behebt das Leck.
            Außerdem äußert sich das Leck nicht so regelmäßig um eine bestimmte Uhrzeit.

            HomoranH Do not disturb
            HomoranH Do not disturb
            Homoran
            Global Moderator Administrators
            wrote on last edited by
            #32

            @AlCalzone
            War das Leck dann bis 8.12 (ausschließlich) ?

            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

            AlCalzoneA 1 Reply Last reply
            0
            • LausiDL LausiD

              @Wildbill sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

              Dito, auch 1.1.1 die im stable Repo als letzte drin ist.

              Gruss, Jürgen

              Um den FHEM Adapter auszuschliessen würde ich wie die Kollegen oben mit Version 1.1.1 an den Start gehen.

              @Homoran sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

              @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

              node: v8.12.0

              Habe mal gesucht:
              wenn du das nicht zwischenzeitlich geändert hast hast du

              node: v8.12.0
              

              Das hat ein Speicherleck

              Solltest du auch beachten, habe hier node 8.15.1 im Einsatz

              Gruß
              LausiD

              A Offline
              A Offline
              Altersrentner
              wrote on last edited by
              #33

              @LausiD Guten Morgen, nein ich hatte nicht aktualisiert, aber wurde eben nachgeholt.

              pi@ioBroker-RasPi:~ $ npm -v
              6.7.0
              pi@ioBroker-RasPi:~ $
              pi@ioBroker-RasPi:~ $ node -v
              v11.12.0
              

              Jetzt gibt es im Log wieder Fehler.

              ost.ioBroker-RasPi	2019-03-18 08:36:31.419	info	Restart adapter system.adapter.zigbee.0 because enabled
              host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	instance system.adapter.zigbee.0 terminated with code 1 ()
              host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:81:44)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:14:16)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:705:19)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:598:3)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
              host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:666:32)
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:840:18)
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 67. Please try re-compiling or re-installing
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 57. This version of Node.js requires
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: was compiled against a different Node.js version using
              host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/build/Release/bindings.node'
              host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: ^
              host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: throw e
              host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:88
              host.ioBroker-RasPi	2019-03-18 08:36:30.555	info	instance system.adapter.zigbee.0 started with pid 16049
              fhem.0	2019-03-18 08:36:20.423	info	event ioBroker "fhem.0.VentilWandhzg_HK1.state_switch off" > set VentilWandhzg_HK1 off
              fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
              fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
              host.ioBroker-RasPi	2019-03-18 08:36:00.559	info	Restart adapter system.adapter.zigbee.0 because enabled
              host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	instance system.adapter.zigbee.0 terminated with code 1 ()
              host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
              host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
              host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
              host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modul
              

              Gruß Michael

              AlCalzoneA 2 Replies Last reply
              0
              • HomoranH Homoran

                @AlCalzone
                War das Leck dann bis 8.12 (ausschließlich) ?

                AlCalzoneA Offline
                AlCalzoneA Offline
                AlCalzone
                Developer
                wrote on last edited by
                #34

                @Homoran Diverse 6.x-Versionen sind betroffen (ich weiß gerade nicht welche) und alle 8.x vor Version 8.12.

                Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                1 Reply Last reply
                0
                • A Altersrentner

                  @LausiD Guten Morgen, nein ich hatte nicht aktualisiert, aber wurde eben nachgeholt.

                  pi@ioBroker-RasPi:~ $ npm -v
                  6.7.0
                  pi@ioBroker-RasPi:~ $
                  pi@ioBroker-RasPi:~ $ node -v
                  v11.12.0
                  

                  Jetzt gibt es im Log wieder Fehler.

                  ost.ioBroker-RasPi	2019-03-18 08:36:31.419	info	Restart adapter system.adapter.zigbee.0 because enabled
                  host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	instance system.adapter.zigbee.0 terminated with code 1 ()
                  host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:81:44)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:14:16)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:705:19)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:598:3)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:666:32)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:840:18)
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 67. Please try re-compiling or re-installing
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 57. This version of Node.js requires
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: was compiled against a different Node.js version using
                  host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/build/Release/bindings.node'
                  host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: ^
                  host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: throw e
                  host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:88
                  host.ioBroker-RasPi	2019-03-18 08:36:30.555	info	instance system.adapter.zigbee.0 started with pid 16049
                  fhem.0	2019-03-18 08:36:20.423	info	event ioBroker "fhem.0.VentilWandhzg_HK1.state_switch off" > set VentilWandhzg_HK1 off
                  fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
                  fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
                  host.ioBroker-RasPi	2019-03-18 08:36:00.559	info	Restart adapter system.adapter.zigbee.0 because enabled
                  host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	instance system.adapter.zigbee.0 terminated with code 1 ()
                  host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
                  host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
                  host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
                  host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modul
                  

                  Gruß Michael

                  AlCalzoneA Offline
                  AlCalzoneA Offline
                  AlCalzone
                  Developer
                  wrote on last edited by AlCalzone
                  #35

                  @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                  Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/build/Release/bindings.node'
                  was compiled against a different Node.js version using
                  NODE_MODULE_VERSION 57. This version of Node.js requires
                  NODE_MODULE_VERSION 67. Please try re-compiling or re-installing
                  the module (for instance, using npm rebuild or npm install).

                  Da steht eigentlich alles was du wissen musst.

                  cd /opt/iobroker/node_modules/iobroker.zigbee
                  npm rebuild
                  

                  Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                  1 Reply Last reply
                  0
                  • A Altersrentner

                    @LausiD Guten Morgen, nein ich hatte nicht aktualisiert, aber wurde eben nachgeholt.

                    pi@ioBroker-RasPi:~ $ npm -v
                    6.7.0
                    pi@ioBroker-RasPi:~ $
                    pi@ioBroker-RasPi:~ $ node -v
                    v11.12.0
                    

                    Jetzt gibt es im Log wieder Fehler.

                    ost.ioBroker-RasPi	2019-03-18 08:36:31.419	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	instance system.adapter.zigbee.0 terminated with code 1 ()
                    host.ioBroker-RasPi	2019-03-18 08:36:31.419	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:81:44)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:14:16)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:705:19)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:598:3)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.418	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:666:32)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:840:18)
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 67. Please try re-compiling or re-installing
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: NODE_MODULE_VERSION 57. This version of Node.js requires
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: was compiled against a different Node.js version using
                    host.ioBroker-RasPi	2019-03-18 08:36:31.417	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/build/Release/bindings.node'
                    host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: ^
                    host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: throw e
                    host.ioBroker-RasPi	2019-03-18 08:36:31.416	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:88
                    host.ioBroker-RasPi	2019-03-18 08:36:30.555	info	instance system.adapter.zigbee.0 started with pid 16049
                    fhem.0	2019-03-18 08:36:20.423	info	event ioBroker "fhem.0.VentilWandhzg_HK1.state_switch off" > set VentilWandhzg_HK1 off
                    fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
                    fhem.0	2019-03-18 08:36:04.574	warn	Reconnection to DB.
                    host.ioBroker-RasPi	2019-03-18 08:36:00.559	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	instance system.adapter.zigbee.0 terminated with code 1 ()
                    host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
                    host.ioBroker-RasPi	2019-03-18 08:36:00.559	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:799:30)
                    host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:1:36)
                    host.ioBroker-RasPi	2019-03-18 08:36:00.558	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modul
                    

                    Gruß Michael

                    AlCalzoneA Offline
                    AlCalzoneA Offline
                    AlCalzone
                    Developer
                    wrote on last edited by
                    #36

                    @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                    pi@ioBroker-RasPi:~ $ node -v
                    v11.12.0

                    Kommando zurück, erst auf eine unterstützte Node-Version (8.x oder 10.x) downgraden! Ungerade Versionen sind Entwicklerversionen und sollten nicht genutzt werden!

                    Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                    A 1 Reply Last reply
                    0
                    • AlCalzoneA AlCalzone

                      @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                      pi@ioBroker-RasPi:~ $ node -v
                      v11.12.0

                      Kommando zurück, erst auf eine unterstützte Node-Version (8.x oder 10.x) downgraden! Ungerade Versionen sind Entwicklerversionen und sollten nicht genutzt werden!

                      A Offline
                      A Offline
                      Altersrentner
                      wrote on last edited by
                      #37

                      @AlCalzone Danke für die Nachricht.
                      Habe jetzt n 8.15.1 installiert.
                      "Da steht eigentlich alles was du wissen musst."
                      Bitte entschuldige; wenn ich es wüsste würde ich nicht fragen.
                      Jetzt wieder diese Fehler und es geht um Zigbee. der Adapter ist aber aktualisiert v 0.10.2.

                      
                      host.ioBroker-RasPi	2019-03-18 10:46:16.725	info	Restart adapter system.adapter.zigbee.0 because enabled
                      host.ioBroker-RasPi	2019-03-18 10:46:16.725	error	instance system.adapter.zigbee.0 terminated with code 1 ()
                      host.ioBroker-RasPi	2019-03-18 10:46:16.724	error	Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.723	error	Caught by controller[0]: at Module._compile (module.js:653:30)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.723	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/serialport/lib/bindings/linux.js:2:36)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.722	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:81:44)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.721	error	Caught by controller[0]: at require (internal/module.js:11:18)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.721	error	Caught by controller[0]: at Module.require (module.js:597:17)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.720	error	Caught by controller[0]: at Function.Module._load (module.js:498:3)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.720	error	Caught by controller[0]: at tryModuleLoad (module.js:506:12)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.719	error	Caught by controller[0]: at Module.load (module.js:566:32)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.718	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:682:18)
                      host.ioBroker-RasPi	2019-03-18 10:46:16.718	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                      host.ioBroker-RasPi	2019-03-18 10:46:16.717	error	Caught by controller[0]: NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
                      host.ioBroker-RasPi	2019-03-18 10:46:16.716	error	Caught by controller[0]: NODE_MODULE_VERSION 67. This version of Node.js requires
                      host.ioBroker-RasPi	2019-03-18 10:46:16.716	error	Caught by controller[0]: was compiled against a different Node.js version using
                      host.ioBroker-RasPi	2019-03-18 10:46:16.715	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/serialport/build/Release/serialport.node'
                      host.ioBroker-RasPi	2019-03-18 10:46:16.714	error	Caught by controller[0]: ^
                      host.ioBroker-RasPi	2019-03-18 10:46:16.714	error	Caught by controller[0]: throw e
                      host.ioBroker-RasPi	2019-03-18 10:46:16.713	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:88
                      host.ioBroker-RasPi	2019-03-18 10:46:15.708	info	instance system.adapter.zigbee.0 started with pid 25054
                      host.ioBroker-RasPi	2019-03-18 10:45:45.687	info	Restart adapter system.adapter.zigbee.0 because enabled
                      

                      Gruß Michael

                      1 Reply Last reply
                      0
                      • A Offline
                        A Offline
                        Altersrentner
                        wrote on last edited by
                        #38

                        Übrigens der Zigbee Adapter läuft nicht. Aller Startversuche scheitern,

                        1 Reply Last reply
                        0
                        • AlCalzoneA Offline
                          AlCalzoneA Offline
                          AlCalzone
                          Developer
                          wrote on last edited by
                          #39

                          Da steht ja auch immer noch der gleiche Fehler. Hast du die Befehle mal ausgeführt? Wenn ja, was war die Ausgabe davon?
                          Kann auch sein, dass du npm rebuild im Ordner /opt/iobroker/node_modules/iobroker.zigbee/node_modules/serialport ausführen musst.

                          Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                          1 Reply Last reply
                          0
                          • A Offline
                            A Offline
                            Altersrentner
                            wrote on last edited by Negalein
                            #40

                            @AlCalzone said in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                            Hast du die Befehle mal ausgeführt

                            Welche Befehle?

                            AlCalzoneA 1 Reply Last reply
                            0
                            • A Altersrentner

                              @AlCalzone said in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                              Hast du die Befehle mal ausgeführt

                              Welche Befehle?

                              AlCalzoneA Offline
                              AlCalzoneA Offline
                              AlCalzone
                              Developer
                              wrote on last edited by
                              #41

                              @Altersrentner Na die aus meinem Post, auf den du dich vorhin bezogen hast:

                              44fc37ee-a004-49f1-9d27-0a61356187a3-grafik.png

                              Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                              A 1 Reply Last reply
                              0
                              • AlCalzoneA AlCalzone

                                @Altersrentner Na die aus meinem Post, auf den du dich vorhin bezogen hast:

                                44fc37ee-a004-49f1-9d27-0a61356187a3-grafik.png

                                A Offline
                                A Offline
                                Altersrentner
                                wrote on last edited by
                                #42

                                @AlCalzone habe npm rebuiild ausgeführt.
                                Nun sieht es im Log schon besser aus.
                                Leider läuft der Zigbee Adapter nur mit gelb.
                                Laut Log muss der serielle Port eingestellt werden.

                                
                                zigbee.0	2019-03-18 12:41:51.036	error	Serial port not selected! Go to settings page.
                                zigbee.0	2019-03-18 12:41:51.029	info	starting. Version 0.10.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
                                zigbee.0	2019-03-18 12:41:49.914	info	States connected to redis: 127.0.0.1:6379
                                host.ioBroker-RasPi	2019-03-18 12:41:48.235	info	instance system.adapter.zigbee.0 started with pid 311
                                host.ioBroker-RasPi	2019-03-18 12:41:48.209	info	object change system.adapter.zigbee.0
                                host.ioBroker-RasPi	2019-03-18 12:41:46.747	info	instance system.adapter.zigbee.0 terminated with code 0 (OK)
                                host.ioBroker-RasPi	2019-03-18 12:41:46.640	info	stopInstance system.adapter.zigbee.0 killing pid 32677
                                host.ioBroker-RasPi	2019-03-18 12:41:46.640	info	stopInstance system.adapter.zigbee.0
                                host.ioBroker-RasPi	2019-03-18 12:41:46.639	info	object change system.adapter.zigbee.0
                                zigbee.0	2019-03-18 12:40:44.196	error	Serial port not selected! Go to settings page.
                                
                                

                                Kann das an der node v 8.15.1 liegen?

                                AlCalzoneA 1 Reply Last reply
                                0
                                • A Altersrentner

                                  @AlCalzone habe npm rebuiild ausgeführt.
                                  Nun sieht es im Log schon besser aus.
                                  Leider läuft der Zigbee Adapter nur mit gelb.
                                  Laut Log muss der serielle Port eingestellt werden.

                                  
                                  zigbee.0	2019-03-18 12:41:51.036	error	Serial port not selected! Go to settings page.
                                  zigbee.0	2019-03-18 12:41:51.029	info	starting. Version 0.10.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
                                  zigbee.0	2019-03-18 12:41:49.914	info	States connected to redis: 127.0.0.1:6379
                                  host.ioBroker-RasPi	2019-03-18 12:41:48.235	info	instance system.adapter.zigbee.0 started with pid 311
                                  host.ioBroker-RasPi	2019-03-18 12:41:48.209	info	object change system.adapter.zigbee.0
                                  host.ioBroker-RasPi	2019-03-18 12:41:46.747	info	instance system.adapter.zigbee.0 terminated with code 0 (OK)
                                  host.ioBroker-RasPi	2019-03-18 12:41:46.640	info	stopInstance system.adapter.zigbee.0 killing pid 32677
                                  host.ioBroker-RasPi	2019-03-18 12:41:46.640	info	stopInstance system.adapter.zigbee.0
                                  host.ioBroker-RasPi	2019-03-18 12:41:46.639	info	object change system.adapter.zigbee.0
                                  zigbee.0	2019-03-18 12:40:44.196	error	Serial port not selected! Go to settings page.
                                  
                                  

                                  Kann das an der node v 8.15.1 liegen?

                                  AlCalzoneA Offline
                                  AlCalzoneA Offline
                                  AlCalzone
                                  Developer
                                  wrote on last edited by
                                  #43

                                  @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                                  Laut Log muss der serielle Port eingestellt werden.

                                  Na, dann mach das doch ;)

                                  Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                                  A 2 Replies Last reply
                                  0
                                  • AlCalzoneA AlCalzone

                                    @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                                    Laut Log muss der serielle Port eingestellt werden.

                                    Na, dann mach das doch ;)

                                    A Offline
                                    A Offline
                                    Altersrentner
                                    wrote on last edited by
                                    #44

                                    @AlCalzone ist gemacht, :ok_hand:

                                    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0012013B01-if00 
                                    

                                    mal sehen was um 04:00 passiert
                                    Danke
                                    Gruß Michael

                                    1 Reply Last reply
                                    0
                                    • AlCalzoneA AlCalzone

                                      @Altersrentner sagte in Fhem Adapter bricht 04:00 Verbindung ab, ist das ein Problem in meinem System oder im Fhem.0 Adapter:

                                      Laut Log muss der serielle Port eingestellt werden.

                                      Na, dann mach das doch ;)

                                      A Offline
                                      A Offline
                                      Altersrentner
                                      wrote on last edited by
                                      #45

                                      @AlCalzone Hallo,
                                      Die Situation nach Aktualisierung ist hinsichtlich Stopp um 04:00 ist unverändert.

                                      9-03-19 03:55:21.199 - warn: fhem.0 Reconnection to DB.
                                      2019-03-19 03:56:36.377 - info: fhem.0 event ioBroker "fhem.0.GewaechshausLED_Ventilation.state_switch on" > set GewaechshausLED_Ventilation on
                                      2019-03-19 03:56:37.375 - info: fhem.0 event ioBroker "fhem.0.Ventilation.state_switch on" > set Ventilation on
                                      2019-03-19 03:58:52.860 - info: fhem.0 event ioBroker "fhem.0.VentilWandhzg_HK2.state_switch off" > set VentilWandhzg_HK2 off
                                      2019-03-19 03:59:24.444 - info: fhem.0 event ioBroker "fhem.0.GewaechshausLED_Ventilation.state_switch on" > set GewaechshausLED_Ventilation on
                                      2019-03-19 03:59:25.443 - info: fhem.0 event ioBroker "fhem.0.Ventilation.state_switch on" > set Ventilation on
                                      2019-03-19 04:00:00.030 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 started with pid 8325
                                      2019-03-19 04:00:01.841 - info: dwd.0 States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:00:02.006 - info: dwd.0 starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v8.15.1
                                      2019-03-19 04:00:02.913 - info: host.ioBroker-RasPi received SIGTERM
                                      2019-03-19 04:00:02.932 - info: web.0 terminating http server on port 8082
                                      2019-03-19 04:00:02.932 - info: web.0 terminated http server on port 8082
                                      2019-03-19 04:00:02.937 - info: admin.0 terminating http server on port 8081
                                      2019-03-19 04:00:02.946 - info: web.0 terminating http server on port 8082
                                      2019-03-19 04:00:02.972 - info: terminal.0 terminating http server on port 8088
                                      2019-03-19 04:00:02.976 - info: terminal.0 terminated http server on port 8088
                                      2019-03-19 04:00:02.985 - info: terminal.0 terminating http server on port 8088
                                      2019-03-19 04:00:02.984 - info: admin.0 terminating http server on port 8081
                                      2019-03-19 04:00:02.918 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
                                      2019-03-19 04:00:02.919 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 993
                                      2019-03-19 04:00:02.919 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
                                      2019-03-19 04:00:02.920 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 killing pid 1004
                                      2019-03-19 04:00:02.923 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
                                      2019-03-19 04:00:02.924 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 1014
                                      2019-03-19 04:00:02.924 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
                                      2019-03-19 04:00:02.925 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 killing pid 1024
                                      2019-03-19 04:00:02.925 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
                                      2019-03-19 04:00:02.927 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 killing pid 1034
                                      2019-03-19 04:00:02.929 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
                                      2019-03-19 04:00:02.931 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
                                      2019-03-19 04:00:02.934 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
                                      2019-03-19 04:00:02.935 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 1295
                                      2019-03-19 04:00:02.939 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
                                      2019-03-19 04:00:02.940 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0 killing pid 1122
                                      2019-03-19 04:00:02.941 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
                                      2019-03-19 04:00:02.944 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 killing pid 2575
                                      2019-03-19 04:00:02.956 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
                                      2019-03-19 04:00:02.957 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 killing pid 1146
                                      2019-03-19 04:00:02.958 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
                                      2019-03-19 04:00:02.958 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 killing pid 1157
                                      2019-03-19 04:00:02.961 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
                                      2019-03-19 04:00:02.962 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 killing pid 1167
                                      2019-03-19 04:00:02.962 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
                                      2019-03-19 04:00:02.962 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 killing pid 1180
                                      2019-03-19 04:00:02.966 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
                                      2019-03-19 04:00:02.967 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 killing pid 1181
                                      2019-03-19 04:00:02.967 - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
                                      2019-03-19 04:00:02.967 - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
                                      2019-03-19 04:00:02.968 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
                                      2019-03-19 04:00:02.968 - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
                                      2019-03-19 04:00:02.968 - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
                                      2019-03-19 04:00:02.968 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
                                      2019-03-19 04:00:02.969 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 killing pid 1182
                                      2019-03-19 04:00:02.969 - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
                                      2019-03-19 04:00:02.970 - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
                                      2019-03-19 04:00:02.970 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
                                      2019-03-19 04:00:02.970 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
                                      2019-03-19 04:00:02.975 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
                                      2019-03-19 04:00:02.975 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
                                      2019-03-19 04:00:02.978 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.dwd.0
                                      2019-03-19 04:00:02.979 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
                                      2019-03-19 04:00:02.979 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
                                      2019-03-19 04:00:02.980 - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
                                      2019-03-19 04:00:02.981 - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
                                      2019-03-19 04:00:02.981 - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
                                      2019-03-19 04:00:02.988 - warn: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0 not scheduled
                                      2019-03-19 04:00:02.988 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
                                      2019-03-19 04:00:02.989 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.yr.0
                                      2019-03-19 04:00:02.989 - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
                                      2019-03-19 04:00:02.990 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.feiertage.0
                                      2019-03-19 04:00:02.990 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
                                      2019-03-19 04:00:02.990 - warn: host.ioBroker-RasPi stopInstance system.adapter.ical.0 not scheduled
                                      2019-03-19 04:00:02.991 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
                                      2019-03-19 04:00:02.991 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 killing pid 1285
                                      2019-03-19 04:00:02.991 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
                                      2019-03-19 04:00:02.992 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 killing pid 1301
                                      2019-03-19 04:00:02.996 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
                                      2019-03-19 04:00:02.997 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 killing pid 1315
                                      2019-03-19 04:00:03.057 - info: host.ioBroker-RasPi instance system.adapter.fhem.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.123 - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.144 - info: socketio.0 terminating http server on port 8084
                                      2019-03-19 04:00:03.168 - info: host.ioBroker-RasPi instance system.adapter.shelly.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.201 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.225 - info: socketio.0 terminating http server on port 8084
                                      2019-03-19 04:00:03.254 - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.282 - info: host.ioBroker-RasPi instance system.adapter.discovery.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.305 - info: host.ioBroker-RasPi instance system.adapter.mihome.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.330 - info: host.ioBroker-RasPi instance system.adapter.terminal.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.354 - info: host.ioBroker-RasPi instance system.adapter.zigbee.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.377 - info: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.401 - info: host.ioBroker-RasPi instance system.adapter.socketio.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.424 - info: host.ioBroker-RasPi instance system.adapter.cul.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.448 - info: host.ioBroker-RasPi instance system.adapter.javascript.1 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.474 - info: host.ioBroker-RasPi instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.505 - info: host.ioBroker-RasPi instance system.adapter.tr-064.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.533 - info: host.ioBroker-RasPi instance system.adapter.scenes.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.558 - info: host.ioBroker-RasPi instance system.adapter.backitup.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:03.877 - info: host.ioBroker-RasPi instance system.adapter.history.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:05.307 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 terminated with code 0 (OK)
                                      2019-03-19 04:00:08.926 - info: host.ioBroker-RasPi received SIGTERM
                                      2019-03-19 04:00:08.927 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
                                      2019-03-19 04:00:08.927 - warn: host.ioBroker-RasPi stopInstance system.adapter.admin.0 not running
                                      2019-03-19 04:00:08.928 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
                                      2019-03-19 04:00:08.928 - warn: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 not running
                                      2019-03-19 04:00:08.928 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
                                      2019-03-19 04:00:08.929 - warn: host.ioBroker-RasPi stopInstance system.adapter.web.0 not running
                                      2019-03-19 04:00:08.929 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
                                      2019-03-19 04:00:08.929 - warn: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 not running
                                      2019-03-19 04:00:08.930 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
                                      2019-03-19 04:00:08.930 - warn: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 not running
                                      2019-03-19 04:00:08.930 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
                                      2019-03-19 04:00:08.930 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
                                      2019-03-19 04:00:08.931 - warn: host.ioBroker-RasPi stopInstance system.adapter.history.0 not running
                                      2019-03-19 04:00:08.931 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
                                      2019-03-19 04:00:08.932 - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 not running
                                      2019-03-19 04:00:08.932 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
                                      2019-03-19 04:00:08.932 - warn: host.ioBroker-RasPi stopInstance system.adapter.cul.0 not running
                                      2019-03-19 04:00:08.933 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
                                      2019-03-19 04:00:08.933 - warn: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 not running
                                      2019-03-19 04:00:08.933 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
                                      2019-03-19 04:00:08.934 - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 not running
                                      2019-03-19 04:00:08.934 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
                                      2019-03-19 04:00:08.934 - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 not running
                                      2019-03-19 04:00:08.934 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
                                      2019-03-19 04:00:08.935 - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 not running
                                      2019-03-19 04:00:08.935 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
                                      2019-03-19 04:00:08.935 - warn: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 not running
                                      2019-03-19 04:00:08.936 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
                                      2019-03-19 04:00:08.936 - warn: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 not running
                                      2019-03-19 04:00:08.936 - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
                                      2019-03-19 04:00:08.937 - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
                                      2019-03-19 04:00:08.937 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
                                      2019-03-19 04:00:08.937 - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
                                      2019-03-19 04:00:08.938 - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
                                      2019-03-19 04:00:08.938 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
                                      2019-03-19 04:00:08.938 - warn: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 not running
                                      2019-03-19 04:00:08.939 - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
                                      2019-03-19 04:00:08.939 - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
                                      2019-03-19 04:00:08.939 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
                                      2019-03-19 04:00:08.939 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
                                      2019-03-19 04:00:08.940 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
                                      2019-03-19 04:00:08.940 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
                                      2019-03-19 04:00:08.940 - warn: host.ioBroker-RasPi stopInstance system.adapter.dwd.0 not scheduled
                                      2019-03-19 04:00:08.941 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
                                      2019-03-19 04:00:08.941 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
                                      2019-03-19 04:00:08.941 - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
                                      2019-03-19 04:00:08.942 - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
                                      2019-03-19 04:00:08.942 - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
                                      2019-03-19 04:00:08.942 - warn: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0 not scheduled
                                      2019-03-19 04:00:08.943 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
                                      2019-03-19 04:00:08.943 - warn: host.ioBroker-RasPi stopInstance system.adapter.yr.0 not scheduled
                                      2019-03-19 04:00:08.943 - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
                                      2019-03-19 04:00:08.944 - warn: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0 not scheduled
                                      2019-03-19 04:00:08.944 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
                                      2019-03-19 04:00:08.944 - warn: host.ioBroker-RasPi stopInstance system.adapter.ical.0 not scheduled
                                      2019-03-19 04:00:08.945 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
                                      2019-03-19 04:00:08.945 - warn: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 not running
                                      2019-03-19 04:00:08.945 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
                                      2019-03-19 04:00:08.945 - warn: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 not running
                                      2019-03-19 04:00:08.946 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
                                      2019-03-19 04:00:08.946 - warn: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 not running
                                      2019-03-19 04:00:13.010 - info: host.ioBroker-RasPi force terminating
                                      2019-03-19 04:01:41.109 - info: host.ioBroker-RasPi iobroker.js-controller version 1.4.2 js-controller starting
                                      2019-03-19 04:01:41.116 - info: host.ioBroker-RasPi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                                      2019-03-19 04:01:41.117 - info: host.ioBroker-RasPi hostname: ioBroker-RasPi, node: v8.11.3
                                      2019-03-19 04:01:41.121 - info: host.ioBroker-RasPi ip addresses: 192.168.178.144 2003:dc:9bd7:3300:fbc8:59d4:babf:3078 fe80::50e8:da28:a103:30a2
                                      2019-03-19 04:01:43.275 - info: host.ioBroker-RasPi inMem-objects listening on port 9001
                                      2019-03-19 04:01:43.300 - info: host.ioBroker-RasPi InMemoryDB connected
                                      2019-03-19 04:01:43.426 - info: host.ioBroker-RasPi 36 instances found
                                      2019-03-19 04:01:43.489 - info: host.ioBroker-RasPi starting 28 instances
                                      2019-03-19 04:01:43.587 - info: host.ioBroker-RasPi instance system.adapter.admin.0 started with pid 638
                                      2019-03-19 04:01:43.604 - info: host.ioBroker-RasPi States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:01:46.449 - info: admin.0 States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:01:46.645 - error: admin.0 setObject id missing!!
                                      2019-03-19 04:01:46.654 - info: admin.0 starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v8.11.3
                                      2019-03-19 04:01:46.676 - info: admin.0 requesting all states
                                      2019-03-19 04:01:46.679 - info: admin.0 requesting all objects
                                      2019-03-19 04:01:46.681 - info: admin.0 Request actual repository...
                                      2019-03-19 04:01:49.370 - info: host.ioBroker-RasPi instance system.adapter.discovery.0 started with pid 648
                                      2019-03-19 04:01:51.928 - info: host.ioBroker-RasPi instance system.adapter.web.0 started with pid 654
                                      2019-03-19 04:01:53.084 - info: discovery.0 States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:01:53.327 - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.11.3
                                      2019-03-19 04:01:54.116 - info: admin.0 received all states
                                      2019-03-19 04:01:54.101 - info: web.0 States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:01:54.267 - error: web.0 setObject id missing!!
                                      2019-03-19 04:01:54.277 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.11.3
                                      2019-03-19 04:01:55.075 - info: web.0 socket.io server listening on port 8082
                                      2019-03-19 04:01:55.083 - info: web.0 http server listening on port 8082
                                      2019-03-19 04:01:55.523 - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 started with pid 668
                                      2019-03-19 04:01:56.557 - info: rpi2.0 States connected to redis: 127.0.0.1:6379
                                      2019-03-19 04:01:56.734 - info: rpi2.0 starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.rpi2, node: v8.11.3
                                      2019-03-19 04:01:58.115 - info: admin.0 received all objects
                                      2019-03-19 04:01:58.885 - info: admin.0 http server listening on port 8081
                                      2019-03-19 04:01:58.886 - info: admin.0 Use link "http://localhost:8081" to configure.
                                      2019-03-19 04:01:59.446 - info: host.ioBroker-RasPi Update repository "stable" under "http://download.iobroker.net/sources-dist-latest.json"
                                      2019-03-19 04:02:00.220 - info: host.ioBroker-RasPi instance system.adapter.socketio.0 started with pid 678
                                      2019-03-19 04:02:08.738 - info: admin.0 Repository received successfully.
                                      

                                      Es muss doch eine Erklärung dafür geben.
                                      Gruß Michael

                                      1 Reply Last reply
                                      0
                                      • A Offline
                                        A Offline
                                        Altersrentner
                                        wrote on last edited by
                                        #46

                                        Hallo,
                                        Heute Morgen das selbe Spiel. 04:00 wurde alles gestoppt. Die Adapter sind dann neu gestartet aber fehm.0 nicht. Nach Neustart von f.0 lief wieder alles normal. Es muss doch einen Grund dafür geben und ich kann mir fast nicht vorstellen, das mein System ein Einzelfall ist.
                                        Gruß Michael

                                        1 Reply Last reply
                                        0
                                        • LausiDL Offline
                                          LausiDL Offline
                                          LausiD
                                          wrote on last edited by LausiD
                                          #47

                                          Hallo Michael,
                                          du hast 36 Instanzen am Start, davon werden 28 beim Neustart gestartet.
                                          Ob das nicht alles etwas viel für den Pi ist?
                                          Um 04:00 Uhr löst der Start von Instanz dwd.0 das ganze aus......
                                          Zeige doch mal hier von der Konsole den Befehl "top" wenn alles läuft.
                                          Hast du FHEM Adapter auf Version 1.1.1 ?
                                          Würde mal dwd.0 und alle nicht unbedingt benötigten Instanzen beenden und nochmal eine Nacht abwarten...
                                          Gruß
                                          LausiD

                                          Doku zum FHEM Adapter
                                          Aktuelles zum FHEM Adapter
                                          Test FHEM Adapter

                                          R A 2 Replies Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          392

                                          Online

                                          32.4k

                                          Users

                                          81.5k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe