Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. 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

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

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

    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Altersrentner @LausiD last edited by

      @LausiD Jetzt habe ich gefunden, wonach Du gefragt hast:

      2019-03-08 04:00:04.974  - info: ical.0 processing URL: calendar1 http://11111.ics
      2019-03-08 04:00:05.185  - 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-08 04:00:05.489  - info: ical.0 processing URL: Google Michael https://calendar.google.com/calendar/ical/m-baer%40t-online.de/private-9fe4ff3cfa48c1d1dd33e5167dff0445/basic.ics
      2019-03-08 04:00:05.493  - info: ical.0 processing URL: Google Mond https://calendar.google.com/calendar/ical/ht3jlfaac5lfd6263ulfh4tql8%40group.calendar.google.com/public/basic.ics
      2019-03-08 04:00:08.442  - info: host.ioBroker-RasPi instance system.adapter.dwd.0 terminated with code 0 (OK)
      2019-03-08 04:00:09.911  - info: host.ioBroker-RasPi received SIGTERM
      2019-03-08 04:00:09.912  - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
      2019-03-08 04:00:09.914  - warn: host.ioBroker-RasPi stopInstance system.adapter.admin.0 not running
      2019-03-08 04:00:09.914  - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
      2019-03-08 04:00:09.915  - warn: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 not running
      2019-03-08 04:00:09.915  - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
      2019-03-08 04:00:09.915  - warn: host.ioBroker-RasPi stopInstance system.adapter.web.0 not running
      2019-03-08 04:00:09.915  - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
      2019-03-08 04:00:09.915  - warn: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 not running
      2019-03-08 04:00:09.915  - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
      2019-03-08 04:00:09.915  - warn: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 not running
      2019-03-08 04:00:09.916  - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
      2019-03-08 04:00:09.916  - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
      2019-03-08 04:00:09.916  - warn: host.ioBroker-RasPi stopInstance system.adapter.history.0 not running
      2019-03-08 04:00:09.916  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
      2019-03-08 04:00:09.916  - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 not running
      2019-03-08 04:00:09.916  - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
      2019-03-08 04:00:09.917  - warn: host.ioBroker-RasPi stopInstance system.adapter.cul.0 not running
      2019-03-08 04:00:09.917  - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
      2019-03-08 04:00:09.917  - warn: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 not running
      2019-03-08 04:00:09.917  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
      2019-03-08 04:00:09.917  - warn: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 not running
      2019-03-08 04:00:09.917  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
      2019-03-08 04:00:09.917  - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 not running
      2019-03-08 04:00:09.917  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
      2019-03-08 04:00:09.918  - warn: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 not running
      2019-03-08 04:00:09.918  - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
      2019-03-08 04:00:09.918  - warn: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 not running
      2019-03-08 04:00:09.918  - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
      2019-03-08 04:00:09.918  - warn: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 not running
      2019-03-08 04:00:09.918  - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
      2019-03-08 04:00:09.918  - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
      2019-03-08 04:00:09.918  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
      2019-03-08 04:00:09.919  - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
      2019-03-08 04:00:09.919  - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
      2019-03-08 04:00:09.919  - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
      2019-03-08 04:00:09.919  - warn: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 not running
      2019-03-08 04:00:09.919  - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
      2019-03-08 04:00:09.919  - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
      2019-03-08 04:00:09.919  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
      2019-03-08 04:00:09.919  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
      2019-03-08 04:00:09.920  - warn: host.ioBroker-RasPi stopInstance system.adapter.dwd.0 not scheduled
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
      2019-03-08 04:00:09.920  - warn: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 not running
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
      2019-03-08 04:00:09.920  - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
      2019-03-08 04:00:09.921  - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
      2019-03-08 04:00:09.921  - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
      2019-03-08 04:00:09.921  - warn: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0 not scheduled
      2019-03-08 04:00:09.921  - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
      2019-03-08 04:00:09.921  - warn: host.ioBroker-RasPi stopInstance system.adapter.yr.0 not scheduled
      2019-03-08 04:00:09.921  - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
      2019-03-08 04:00:09.921  - warn: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0 not scheduled
      2019-03-08 04:00:09.921  - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
      2019-03-08 04:00:09.922  - warn: host.ioBroker-RasPi stopInstance system.adapter.ical.0 not scheduled
      2019-03-08 04:00:09.922  - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
      2019-03-08 04:00:09.922  - warn: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 not running
      2019-03-08 04:00:09.922  - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
      2019-03-08 04:00:09.922  - warn: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 not running
      2019-03-08 04:00:11.051  - debug: daswetter.0 nothing to do
      2019-03-08 04:00:11.068  - error: host.ioBroker-RasPi instance system.adapter.daswetter.0 terminated with code 11 ()
      2019-03-08 04:00:11.354  - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
      2019-03-08 04:00:13.991  - info: host.ioBroker-RasPi force terminating
      
      
      2019-03-08 04:00:03.964  - info: terminal.0 terminating http server on port 8088
      2019-03-08 04:00:03.964  - info: tr-064.0 terminating
      2019-03-08 04:00:03.965  - info: rpi2.0 terminating
      2019-03-08 04:00:03.965  - info: terminal.0 terminated http server on port 8088
      2019-03-08 04:00:03.952  - info: web.0 terminated http server on port 8082
      2019-03-08 04:00:03.972  - info: web.0 terminating
      2019-03-08 04:00:03.974  - info: terminal.0 terminating
      2019-03-08 04:00:03.905  - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
      2019-03-08 04:00:03.905  - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 636
      2019-03-08 04:00:03.909  - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
      2019-03-08 04:00:03.910  - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 killing pid 647
      2019-03-08 04:00:03.910  - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
      2019-03-08 04:00:03.911  - info: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 657
      2019-03-08 04:00:03.911  - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
      2019-03-08 04:00:03.911  - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 killing pid 667
      2019-03-08 04:00:03.912  - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
      2019-03-08 04:00:03.912  - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 killing pid 677
      2019-03-08 04:00:03.913  - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
      2019-03-08 04:00:03.913  - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
      2019-03-08 04:00:03.918  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
      2019-03-08 04:00:03.919  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 758
      2019-03-08 04:00:03.922  - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
      2019-03-08 04:00:03.922  - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0 killing pid 764
      2019-03-08 04:00:03.923  - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
      2019-03-08 04:00:03.923  - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 killing pid 12614
      2019-03-08 04:00:03.924  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
      2019-03-08 04:00:03.930  - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 killing pid 788
      2019-03-08 04:00:03.931  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
      2019-03-08 04:00:03.931  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 killing pid 798
      2019-03-08 04:00:03.932  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
      2019-03-08 04:00:03.932  - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 killing pid 804
      2019-03-08 04:00:03.940  - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
      2019-03-08 04:00:03.940  - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 killing pid 810
      2019-03-08 04:00:03.950  - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
      2019-03-08 04:00:03.951  - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 killing pid 828
      2019-03-08 04:00:03.952  - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
      2019-03-08 04:00:03.953  - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
      2019-03-08 04:00:03.954  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
      2019-03-08 04:00:03.955  - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
      2019-03-08 04:00:03.955  - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
      2019-03-08 04:00:03.956  - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
      2019-03-08 04:00:03.957  - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 killing pid 834
      2019-03-08 04:00:03.967  - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
      2019-03-08 04:00:03.968  - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
      2019-03-08 04:00:03.968  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
      2019-03-08 04:00:03.969  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
      2019-03-08 04:00:03.969  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
      2019-03-08 04:00:03.970  - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
      2019-03-08 04:00:03.973  - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.dwd.0
      2019-03-08 04:00:03.974  - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
      2019-03-08 04:00:03.974  - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 killing pid 899
      2019-03-08 04:00:03.974  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
      2019-03-08 04:00:03.975  - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
      2019-03-08 04:00:03.975  - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
      2019-03-08 04:00:03.975  - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
      2019-03-08 04:00:03.976  - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
      2019-03-08 04:00:03.976  - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.daswetter.0
      2019-03-08 04:00:03.976  - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
      2019-03-08 04:00:03.977  - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.yr.0
      2019-03-08 04:00:03.978  - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
      2019-03-08 04:00:03.978  - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.feiertage.0
      2019-03-08 04:00:03.978  - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
      2019-03-08 04:00:03.979  - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.0
      2019-03-08 04:00:03.979  - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
      2019-03-08 04:00:03.979  - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 killing pid 939
      2019-03-08 04:00:03.979  - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
      2019-03-08 04:00:03.980  - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 killing pid 945
      2019-03-08 04:00:04.000  - info: shelly.0 terminating
      2019-03-08 04:00:04.012  - info: discovery.0 terminating
      2019-03-08 04:00:04.009  - info: javascript.1 terminating
      2019-03-08 04:00:04.024  - info: socketio.0 terminating
      2019-03-08 04:00:04.047  - info: cul.0 terminating
      2019-03-08 04:00:04.074  - info: zigbee.0 terminating
      2019-03-08 04:00:04.218  - info: host.ioBroker-RasPi instance system.adapter.discovery.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.449  - info: scenes.0 terminating
      2019-03-08 04:00:04.487  - info: backitup.0 terminating
      2019-03-08 04:00:04.646  - debug: daswetter.0 redis pmessage  io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1552014004620,"q":0,"from":"system.host.ioBroker-RasPi","lc":1551983129186}
      2019-03-08 04:00:04.650  - debug: daswetter.0 system.adapter.admin.0: logging false
      2019-03-08 04:00:04.250  - info: host.ioBroker-RasPi instance system.adapter.terminal.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.278  - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.310  - info: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.339  - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.367  - info: host.ioBroker-RasPi instance system.adapter.socketio.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.394  - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.423  - info: host.ioBroker-RasPi instance system.adapter.cul.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.456  - info: host.ioBroker-RasPi instance system.adapter.javascript.1 terminated with code 0 (OK)
      2019-03-08 04:00:04.495  - info: host.ioBroker-RasPi instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.528  - info: host.ioBroker-RasPi instance system.adapter.mihome.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.557  - info: host.ioBroker-RasPi instance system.adapter.tr-064.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.585  - info: host.ioBroker-RasPi instance system.adapter.zigbee.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.616  - info: host.ioBroker-RasPi instance system.adapter.shelly.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.700  - info: host.ioBroker-RasPi instance system.adapter.history.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.727  - info: host.ioBroker-RasPi instance system.adapter.scenes.0 terminated with code 0 (OK)
      2019-03-08 04:00:04.757  - info: host.ioBroker-RasPi instance system.adapter.backitup.0 terminated with code 0 (OK)
      
      

      Danach tauchen die Blöcke nicht mehr auf.
      Gruß Michael

      1 Reply Last reply Reply Quote 0
      • LausiD
        LausiD last edited by

        Hallo Michael,
        so wie ich das sehe werden bei dir um 04:00 Uhr alle Instanzen gestoppt.
        Denke ist auf keinem Fall ein Problem des FHEM Adapter.
        Wie bekommst du ioBroker wieder an den Start? Neustart Pi?
        Vielleicht können die ioBroker Jungs noch was dazu sagen.....

        Gruß
        LausiD

        1 Reply Last reply Reply Quote 0
        • A
          Altersrentner last edited by

          Hallo LausiD,
          Ich sehe das genau so wie Du.
          Der Neustart erfolgt über Konsole.
          Dann denke ich, ist das auch nicht normal -oder??

          fhem.0	2019-03-09 13:44:28.036	warn	Reconnection to DB.
          fhem.0	2019-03-09 13:44:28.027	warn	Reconnection to DB.
          

          Gruß Michael

          1 Reply Last reply Reply Quote 0
          • A
            Altersrentner last edited by

            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

            Homoran 1 Reply Last reply Reply Quote 0
            • AlCalzone
              AlCalzone Developer last edited by

              Hast du ein Backup o.ä. konfiguriert? Es ist für mich doch arg verwunderlich, dass genau um 4 der komplette ioBroker runterfährt.

              A 1 Reply Last reply Reply Quote 0
              • A
                Altersrentner @AlCalzone last edited by

                @AlCalzone Ja, über backitup, Standard Backup um 02:00 jeden Tag und Komplett alle 2 Tage um 03:00.
                Daran kann es meiner Meinung aber nicht liegen, da die erste mir bewusste Unterbrechung im Januar während unsere Urlaubs
                gewesen war. Zu der Zeit wurden die Sicherungen noch händisch durchgeführt.
                Danke Gruß
                Michael

                AlCalzone 1 Reply Last reply Reply Quote 0
                • AlCalzone
                  AlCalzone Developer @Altersrentner last edited by

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

                  Komplett alle 2 Tage um 03:00.

                  Nur mal wild geraten:

                  • 04:00 Uhr aus dem Log ist 03:00 UTC
                  • Backitup fährt den ioBroker fürs Komplett-Backup um 03:00 UTC herunter und dann nicht mehr sauber hoch
                  A 1 Reply Last reply Reply Quote 0
                  • A
                    Altersrentner @AlCalzone last edited by

                    @AlCalzone Hallo, danke Für Deine Unterstützung. Wenn der Schuldige das backup ist,
                    Wie sollte ich vorgehen damit das backup gemacht wird aber der iobroker anschließend wieder sauber startet..
                    Danke
                    Gruß Michael

                    1 Reply Last reply Reply Quote 0
                    • AlCalzone
                      AlCalzone Developer last edited by

                      Ich weiß es nicht - erst mal sollten wir herausfinden, ob es das wirklich ist oder doch was anderes. Vielleicht setzt du mal das Komplett-Backup aus und beobachtest - Standard sollte ja ohne Unterbrechung tun.

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        Altersrentner @AlCalzone last edited by

                        @AlCalzone Danke für Deine Antwort. Wie in dem Log zu sehen wurden wieder die Adapter gestoppt.
                        Ein backup wurde aber nicht durchgeführt.

                        19-03-15 03:55:29.322 - warn: fhem.0 Reconnection to DB.
                        2019-03-15 03:55:29.325 - warn: fhem.0 Reconnection to DB.
                        2019-03-15 04:00:00.045 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 started with pid 23955
                        2019-03-15 04:00:00.116 - info: host.ioBroker-RasPi instance system.adapter.daswetter.0 started with pid 23961
                        2019-03-15 04:00:00.170 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 23966
                        2019-03-15 04:00:01.870 - info: dwd.0 States connected to redis: 127.0.0.1:6379
                        2019-03-15 04:00:02.032 - debug: daswetter.0 objectDB connected
                        2019-03-15 04:00:02.102 - info: dwd.0 starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v8.11.3
                        2019-03-15 04:00:02.086 - debug: daswetter.0 statesDB connected
                        2019-03-15 04:00:02.095 - info: daswetter.0 States connected to redis: 127.0.0.1:6379
                        2019-03-15 04:00:02.226 - info: daswetter.0 starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.daswetter, node: v8.11.3
                        2019-03-15 04:00:02.239 - debug: daswetter.0 set timeout to 60 sec
                        2019-03-15 04:00:02.240 - debug: daswetter.0 using new data structure
                        2019-03-15 04:00:02.246 - 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-15 04:00:02.379 - info: ical.0 States connected to redis: 127.0.0.1:6379
                        2019-03-15 04:00:02.576 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.11.3
                        2019-03-15 04:00:02.950 - debug: daswetter.0 hourly forecast done, objects in list 1635
                        2019-03-15 04:00:02.955 - debug: daswetter.0 objects in list: 1635
                        2019-03-15 04:00:03.169 - info: ical.0 processing URL: calendar1 http://11111.ics
                        2019-03-15 04:00:03.276 - info: ical.0 processing URL: Google Michael https://calendar.google.com/calendar/ical/m-baer%40t-online.de/private-9fe4ff3cfa48c1d1dd33e5167dff0445/basic.ics
                        2019-03-15 04:00:03.804 - info: ical.0 processing URL: Google Mond https://calendar.google.com/calendar/ical/ht3jlfaac5lfd6263ulfh4tql8%40group.calendar.google.com/public/basic.ics
                        2019-03-15 04:00:03.819 - 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-15 04:00:04.028 - info: host.ioBroker-RasPi received SIGTERM
                        2019-03-15 04:00:04.087 - info: fhem.0 terminating
                        2019-03-15 04:00:04.034 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
                        2019-03-15 04:00:04.034 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 733
                        2019-03-15 04:00:04.037 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
                        2019-03-15 04:00:04.037 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 killing pid 749
                        2019-03-15 04:00:04.037 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
                        2019-03-15 04:00:04.038 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 767
                        2019-03-15 04:00:04.038 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
                        2019-03-15 04:00:04.038 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 killing pid 783
                        2019-03-15 04:00:04.039 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
                        2019-03-15 04:00:04.040 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 killing pid 799
                        2019-03-15 04:00:04.040 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
                        2019-03-15 04:00:04.041 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
                        2019-03-15 04:00:04.042 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
                        2019-03-15 04:00:04.042 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 1032
                        2019-03-15 04:00:04.044 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0
                        2019-03-15 04:00:04.046 - info: host.ioBroker-RasPi stopInstance system.adapter.cul.0 killing pid 727
                        2019-03-15 04:00:04.047 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0
                        2019-03-15 04:00:04.047 - info: host.ioBroker-RasPi stopInstance system.adapter.fhem.0 killing pid 743
                        2019-03-15 04:00:04.048 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1
                        2019-03-15 04:00:04.049 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.1 killing pid 772
                        2019-03-15 04:00:04.052 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0
                        2019-03-15 04:00:04.052 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome-vacuum.0 killing pid 789
                        2019-03-15 04:00:04.054 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0
                        2019-03-15 04:00:04.055 - info: host.ioBroker-RasPi stopInstance system.adapter.mihome.0 killing pid 800
                        2019-03-15 04:00:04.056 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
                        2019-03-15 04:00:04.057 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 killing pid 853
                        2019-03-15 04:00:04.057 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0
                        2019-03-15 04:00:04.058 - info: host.ioBroker-RasPi stopInstance system.adapter.terminal.0 killing pid 867
                        2019-03-15 04:00:04.058 - info: host.ioBroker-RasPi stopInstance system.adapter.harmony.0
                        2019-03-15 04:00:04.059 - warn: host.ioBroker-RasPi stopInstance system.adapter.harmony.0 not running
                        2019-03-15 04:00:04.059 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
                        2019-03-15 04:00:04.060 - info: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0
                        2019-03-15 04:00:04.061 - warn: host.ioBroker-RasPi stopInstance system.adapter.alexa2.0 not running
                        2019-03-15 04:00:04.062 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0
                        2019-03-15 04:00:04.062 - info: host.ioBroker-RasPi stopInstance system.adapter.tr-064.0 killing pid 877
                        2019-03-15 04:00:04.063 - info: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
                        2019-03-15 04:00:04.063 - warn: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
                        2019-03-15 04:00:04.063 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
                        2019-03-15 04:00:04.064 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
                        2019-03-15 04:00:04.064 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
                        2019-03-15 04:00:04.064 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
                        2019-03-15 04:00:04.066 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.dwd.0
                        2019-03-15 04:00:04.066 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0
                        2019-03-15 04:00:04.066 - info: host.ioBroker-RasPi stopInstance system.adapter.zigbee.0 killing pid 976
                        2019-03-15 04:00:04.067 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
                        2019-03-15 04:00:04.068 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-plumb.0
                        2019-03-15 04:00:04.068 - info: host.ioBroker-RasPi stopInstance system.adapter.samsung.0
                        2019-03-15 04:00:04.069 - warn: host.ioBroker-RasPi stopInstance system.adapter.samsung.0 not running
                        2019-03-15 04:00:04.070 - info: host.ioBroker-RasPi stopInstance system.adapter.daswetter.0
                        2019-03-15 04:00:04.070 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.daswetter.0
                        2019-03-15 04:00:04.071 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
                        2019-03-15 04:00:04.072 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.yr.0
                        2019-03-15 04:00:04.073 - info: host.ioBroker-RasPi stopInstance system.adapter.feiertage.0
                        2019-03-15 04:00:04.073 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.feiertage.0
                        2019-03-15 04:00:04.074 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
                        2019-03-15 04:00:04.074 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.0
                        2019-03-15 04:00:04.075 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0
                        2019-03-15 04:00:04.075 - info: host.ioBroker-RasPi stopInstance system.adapter.shelly.0 killing pid 1062
                        2019-03-15 04:00:04.099 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
                        2019-03-15 04:00:04.100 - info: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 killing pid 1072
                        2019-03-15 04:00:04.154 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.204 - info: host.ioBroker-RasPi instance system.adapter.rpi2.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.245 - info: host.ioBroker-RasPi instance system.adapter.shelly.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.268 - info: host.ioBroker-RasPi instance system.adapter.fhem.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.304 - info: host.ioBroker-RasPi instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.344 - info: host.ioBroker-RasPi instance system.adapter.zigbee.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.383 - info: web.0 terminating http server on port 8082
                        2019-03-15 04:00:04.409 - info: host.ioBroker-RasPi instance system.adapter.cul.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.436 - info: host.ioBroker-RasPi instance system.adapter.socketio.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.464 - info: host.ioBroker-RasPi instance system.adapter.mihome.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.494 - info: host.ioBroker-RasPi instance system.adapter.tr-064.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.474 - info: web.0 terminated http server on port 8082
                        2019-03-15 04:00:04.510 - info: web.0 terminating
                        2019-03-15 04:00:04.309 - info: admin.0 terminating http server on port 8081
                        2019-03-15 04:00:04.613 - info: host.ioBroker-RasPi instance system.adapter.javascript.1 terminated with code 0 (OK)
                        2019-03-15 04:00:04.451 - info: terminal.0 terminating http server on port 8088
                        2019-03-15 04:00:04.652 - info: host.ioBroker-RasPi instance system.adapter.history.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.675 - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.701 - info: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.725 - info: host.ioBroker-RasPi instance system.adapter.discovery.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.746 - info: host.ioBroker-RasPi instance system.adapter.terminal.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.768 - info: host.ioBroker-RasPi instance system.adapter.backitup.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.790 - info: host.ioBroker-RasPi instance system.adapter.scenes.0 terminated with code 0 (OK)
                        2019-03-15 04:00:04.799 - debug: daswetter.0 redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1552618804793,"q":0,"from":"system.host.ioBroker-RasPi","lc":1552605477976}
                        2019-03-15 04:00:04.802 - debug: daswetter.0 system.adapter.admin.0: logging false
                        2019-03-15 04:00:07.577 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 terminated with code 0 (OK)
                        2019-03-15 04:00:09.420 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
                        2019-03-15 04:00:09.500 - debug: daswetter.0 nothing to do
                        2019-03-15 04:00:09.516 - error: host.ioBroker-RasPi instance system.adapter.daswetter.0 terminated with code 11 ()
                        2019-03-15 04:00:10.037 - info: host.ioBroker-RasPi received SIGTERM
                        2019-03-15 04:00:10.037 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
                        2019-03-15 04:00:10.037 - warn: host.ioBroker-RasPi stopInstance system.adapter.admin.0 not running
                        2019-03-15 04:00:10.038 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
                        2019-03-15 04:00:10.038 - warn: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 not running
                        2019-03-15 04:00:10.038 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
                        2019-03-15 04:00:10.038 - warn: host.ioBroker-RasPi stopInstance system.adapter.web.0 not running
                        2019-03-15 04:00:10.038 - info: host.ioBroker-RasPi stopI
                        

                        Gruß Michael

                        1 Reply Last reply Reply Quote 0
                        • AlCalzone
                          AlCalzone Developer last edited by

                          Hast du Skripte laufen, die sowas machen?

                          A 1 Reply Last reply Reply Quote 0
                          • A
                            Altersrentner @AlCalzone last edited by

                            @AlCalzone Wie könnte ich das prüfen? es gibt aber kein Skript, welches in dem
                            Zeitraum schalten soll.
                            Gruß Michael

                            1 Reply Last reply Reply Quote 0
                            • LausiD
                              LausiD last edited by

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

                              03-15 04:00:00.045 - info: host.ioBroker-RasPi instance system.adapter.dwd.0 started with pid 23955
                              2019-03-15 04:00:00.116 - info: host.ioBroker-RasPi instance system.adapter.daswetter.0 started with pid 23961
                              2019-03-15 04:00:00.170 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 23966

                              Startest du um 04:00 Uhr gleichzeitig die 3 Instanzen dwd.0, daswetter.0 und ical.0????
                              Das könnte für den kleinen Pi eventuell etwas zu viel sein....

                              Gruß
                              LausiD

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                Altersrentner @LausiD last edited by

                                @LausiD Hallo, ich glaube Du hast ins Schwarze getroffen.
                                das Wetter = */30 * * * *
                                dwd = */5 * * * *
                                ical = 0,20 * * * *
                                Die Einstellungen habe ich aber nicht vorgenommen.
                                Wenn das der Auslöser sein sollte wie soll ich die Zeiten ändern.
                                Gruß Michael

                                1 Reply Last reply Reply Quote 0
                                • LausiD
                                  LausiD last edited by

                                  @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 1 Reply Last reply Reply Quote 0
                                  • Homoran
                                    Homoran Global Moderator Administrators @Altersrentner last edited by

                                    @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

                                    AlCalzone 1 Reply Last reply Reply Quote 0
                                    • A
                                      Altersrentner @LausiD last edited by

                                      @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 Reply Quote 0
                                      • LausiD
                                        LausiD @Wildbill last edited by

                                        @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 1 Reply Last reply Reply Quote 0
                                        • AlCalzone
                                          AlCalzone Developer @Homoran last edited by

                                          @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.

                                          Homoran 1 Reply Last reply Reply Quote 0
                                          • Homoran
                                            Homoran Global Moderator Administrators @AlCalzone last edited by

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

                                            AlCalzone 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            456
                                            Online

                                            31.8k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            fhem.0
                                            8
                                            63
                                            3780
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo