Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Fehler nach Admin-Adapter update auf 3.6.12

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    23
    1
    1.3k

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.5k

Fehler nach Admin-Adapter update auf 3.6.12

Geplant Angeheftet Gesperrt Verschoben Gelöst Error/Bug
adminfehler
17 Beiträge 4 Kommentatoren 903 Aufrufe 4 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • I Offline
    I Offline
    ioBroker_Yasmin
    schrieb am zuletzt editiert von Negalein
    #1

    Hallo ihr lieben,
    wenn ich den Admin-Adapter von aktuell 3.6.7 auf 3.6.12 aktualisiere, bekomme ich daraufhin keine Adminoberfläche mehr zu sehen.
    Im Log-File taucht dann dieses auf

    2019-12-03 18:34:05.198  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27068
    2019-12-03 18:34:05.726  - info: admin.0 (27068) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
    2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all states
    2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all objects
    2019-12-03 18:34:05.834  - info: admin.0 (27068) received all objects
    2019-12-03 18:34:05.920  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(s
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tatus).
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
    
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F4826FD780
    2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
    

    Hat da jemand eine Idee oder Lösung zu?

    Danke schonmal
    Yasmin

    Mod-Edit: Thema ins passende Forum verschoben!

    I arteckA 2 Antworten Letzte Antwort
    0
    • I ioBroker_Yasmin

      @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

      @ioBroker_Yasmin
      Bist du im Richtigen Verzeichnis?
      Wie hast du installiert?
      Welche Version von Installer?

      Ja, ich bin im richtigen Verzeichnis. Mit welcher Version ich ursprünglich installiert habe, kann ich nicht mehr sagen.
      Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

      sigi234S Online
      sigi234S Online
      sigi234
      Forum Testing Most Active
      schrieb am zuletzt editiert von sigi234
      #14

      @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

      Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

      Nimm diesen:

      https://www.iobroker.net/#de/download

      Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
      Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast. Lösche nicht die alte Installation und sichere dir den Ordner iobroker-data

      Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
      Immer Daten sichern!

      I 1 Antwort Letzte Antwort
      1
      • I ioBroker_Yasmin

        Hallo ihr lieben,
        wenn ich den Admin-Adapter von aktuell 3.6.7 auf 3.6.12 aktualisiere, bekomme ich daraufhin keine Adminoberfläche mehr zu sehen.
        Im Log-File taucht dann dieses auf

        2019-12-03 18:34:05.198  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27068
        2019-12-03 18:34:05.726  - info: admin.0 (27068) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
        2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all states
        2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all objects
        2019-12-03 18:34:05.834  - info: admin.0 (27068) received all objects
        2019-12-03 18:34:05.920  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(s
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tatus).
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
        
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F4826FD780
        2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
        

        Hat da jemand eine Idee oder Lösung zu?

        Danke schonmal
        Yasmin

        Mod-Edit: Thema ins passende Forum verschoben!

        I Offline
        I Offline
        ioBroker_Yasmin
        schrieb am zuletzt editiert von
        #2

        Danke für das Verschieben.

        Der Fehler tritt bei mir mit allen Versionen neuer 3.6.7 auf.
        Wenn Ihr mehr Informationen dazu benötigt. Sagt mir bitte bescheid.

        LG Yasmin

        1 Antwort Letzte Antwort
        0
        • I ioBroker_Yasmin

          Hallo ihr lieben,
          wenn ich den Admin-Adapter von aktuell 3.6.7 auf 3.6.12 aktualisiere, bekomme ich daraufhin keine Adminoberfläche mehr zu sehen.
          Im Log-File taucht dann dieses auf

          2019-12-03 18:34:05.198  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27068
          2019-12-03 18:34:05.726  - info: admin.0 (27068) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
          2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all states
          2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all objects
          2019-12-03 18:34:05.834  - info: admin.0 (27068) received all objects
          2019-12-03 18:34:05.920  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(s
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tatus).
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
          
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F4826FD780
          2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
          

          Hat da jemand eine Idee oder Lösung zu?

          Danke schonmal
          Yasmin

          Mod-Edit: Thema ins passende Forum verschoben!

          arteckA Offline
          arteckA Offline
          arteck
          Developer Most Active
          schrieb am zuletzt editiert von
          #3

          @ioBroker_Yasmin kannst du bitte den gesamten LOG aus /opt/iobroker/log posten

          zigbee hab ich, zwave auch, nuc's genauso und HA auch

          1 Antwort Letzte Antwort
          0
          • I Offline
            I Offline
            ioBroker_Yasmin
            schrieb am zuletzt editiert von
            #4

            Ich hab es zwischendurch immer wieder mal gelöscht, weil es zu viel wurde, aber hier ist, denke ich alles drin, was nötig ist.

            
            2019-12-03 18:31:01.644  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:31:31.653  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 5452
            2019-12-03 18:31:32.173  - info: admin.0 (5452) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:31:32.185  - info: admin.0 (5452) requesting all states
            2019-12-03 18:31:32.185  - info: admin.0 (5452) requesting all objects
            2019-12-03 18:31:32.272  - info: admin.0 (5452) received all objects
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(sta
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tus).
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000E5E43ED580
            2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:31:32.356  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:32:02.366  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27076
            2019-12-03 18:32:02.900  - info: admin.0 (27076) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:32:02.912  - info: admin.0 (27076) requesting all states
            2019-12-03 18:32:02.912  - info: admin.0 (27076) requesting all objects
            2019-12-03 18:32:02.990  - info: admin.0 (27076) received all objects
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error 
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: in , line 0
            
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
            
            2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000005113CFD340
            2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:32:03.079  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:32:33.085  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 4680
            2019-12-03 18:32:33.615  - info: admin.0 (4680) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:32:33.626  - info: admin.0 (4680) requesting all states
            2019-12-03 18:32:33.626  - info: admin.0 (4680) requesting all objects
            2019-12-03 18:32:33.708  - info: admin.0 (4680) received all objects
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal erro
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: r in , line 0
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000A1E0AFD6B0
            2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:32:33.790  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:33:03.797  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 25140
            2019-12-03 18:33:04.305  - info: admin.0 (25140) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:33:04.317  - info: admin.0 (25140) requesting all states
            2019-12-03 18:33:04.317  - info: admin.0 (25140) requesting all objects
            2019-12-03 18:33:04.401  - info: admin.0 (25140) received all objects
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]:  in , line 0
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000D7FC6FD5D0
            2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:33:04.484  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:33:34.498  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 16836
            2019-12-03 18:33:35.019  - info: admin.0 (16836) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:33:35.030  - info: admin.0 (16836) requesting all states
            2019-12-03 18:33:35.030  - info: admin.0 (16836) requesting all objects
            2019-12-03 18:33:35.109  - info: admin.0 (16836) received all objects
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(status).
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000584CD1D190
            2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:33:35.191  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:34:05.198  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27068
            2019-12-03 18:34:05.726  - info: admin.0 (27068) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all states
            2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all objects
            2019-12-03 18:34:05.834  - info: admin.0 (27068) received all objects
            2019-12-03 18:34:05.920  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(s
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tatus).
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F4826FD780
            2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:34:05.921  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:34:35.940  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 26364
            2019-12-03 18:34:36.465  - info: admin.0 (26364) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:34:36.476  - info: admin.0 (26364) requesting all states
            2019-12-03 18:34:36.476  - info: admin.0 (26364) requesting all objects
            2019-12-03 18:34:36.551  - info: admin.0 (26364) received all objects
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SU
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: CCESS(status).
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:34:36.636  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F08D6FD7B0
            2019-12-03 18:34:36.636  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:34:36.636  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:35:06.642  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 8940
            2019-12-03 18:35:07.153  - info: admin.0 (8940) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:35:07.163  - info: admin.0 (8940) requesting all states
            2019-12-03 18:35:07.164  - info: admin.0 (8940) requesting all objects
            2019-12-03 18:35:07.239  - info: admin.0 (8940) received all objects
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCC
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: ESS(status).
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000009CEADDD5E0
            2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:35:07.321  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:35:37.328  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 11144
            2019-12-03 18:35:37.879  - info: admin.0 (11144) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:35:37.890  - info: admin.0 (11144) requesting all states
            2019-12-03 18:35:37.890  - info: admin.0 (11144) requesting all objects
            2019-12-03 18:35:37.977  - info: admin.0 (11144) received all objects
            2019-12-03 18:35:38.061  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: SUCCESS(status).
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
            
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000005AB47BD230
            2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
            2019-12-03 18:35:38.062  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
            2019-12-03 18:36:08.083  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 2852
            2019-12-03 18:36:08.601  - info: admin.0 (2852) starting. Version 3.6.7 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
            2019-12-03 18:36:08.611  - info: admin.0 (2852) requesting all states
            2019-12-03 18:36:08.611  - info: admin.0 (2852) requesting all objects
            2019-12-03 18:36:08.612  - info: admin.0 (2852) Request actual repository...
            2019-12-03 18:36:08.660  - info: host.DESKTOP-D0F4V8L Update repository "default" under "http://download.iobroker.net/sources-dist.json"
            2019-12-03 18:36:08.688  - info: admin.0 (2852) received all objects
            2019-12-03 18:36:08.703  - info: admin.0 (2852) received all states
            2019-12-03 18:36:08.710  - info: admin.0 (2852) http server listening on port 8081
            2019-12-03 18:36:08.710  - info: admin.0 (2852) Use link "http://localhost:8081" to configure.
            2019-12-03 18:36:08.875  - info: admin.0 (2852) Repository received successfully.
            
            

            Der Fehler wiederholt sich ständig, bis ich wieder auf 3.6.7 zurückgesetzt habe.

            crunchipC 1 Antwort Letzte Antwort
            0
            • I ioBroker_Yasmin

              Ich hab es zwischendurch immer wieder mal gelöscht, weil es zu viel wurde, aber hier ist, denke ich alles drin, was nötig ist.

              
              2019-12-03 18:31:01.644  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:31:31.653  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 5452
              2019-12-03 18:31:32.173  - info: admin.0 (5452) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:31:32.185  - info: admin.0 (5452) requesting all states
              2019-12-03 18:31:32.185  - info: admin.0 (5452) requesting all objects
              2019-12-03 18:31:32.272  - info: admin.0 (5452) received all objects
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(sta
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tus).
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000E5E43ED580
              2019-12-03 18:31:32.356  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:31:32.356  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:32:02.366  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27076
              2019-12-03 18:32:02.900  - info: admin.0 (27076) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:32:02.912  - info: admin.0 (27076) requesting all states
              2019-12-03 18:32:02.912  - info: admin.0 (27076) requesting all objects
              2019-12-03 18:32:02.990  - info: admin.0 (27076) received all objects
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error 
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: in , line 0
              
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
              
              2019-12-03 18:32:03.078  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000005113CFD340
              2019-12-03 18:32:03.079  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:32:03.079  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:32:33.085  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 4680
              2019-12-03 18:32:33.615  - info: admin.0 (4680) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:32:33.626  - info: admin.0 (4680) requesting all states
              2019-12-03 18:32:33.626  - info: admin.0 (4680) requesting all objects
              2019-12-03 18:32:33.708  - info: admin.0 (4680) received all objects
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal erro
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: r in , line 0
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000A1E0AFD6B0
              2019-12-03 18:32:33.790  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:32:33.790  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:33:03.797  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 25140
              2019-12-03 18:33:04.305  - info: admin.0 (25140) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:33:04.317  - info: admin.0 (25140) requesting all states
              2019-12-03 18:33:04.317  - info: admin.0 (25140) requesting all objects
              2019-12-03 18:33:04.401  - info: admin.0 (25140) received all objects
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]:  in , line 0
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: # Check failed: U_SUCCESS(status).
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000D7FC6FD5D0
              2019-12-03 18:33:04.484  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:33:04.484  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:33:34.498  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 16836
              2019-12-03 18:33:35.019  - info: admin.0 (16836) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:33:35.030  - info: admin.0 (16836) requesting all states
              2019-12-03 18:33:35.030  - info: admin.0 (16836) requesting all objects
              2019-12-03 18:33:35.109  - info: admin.0 (16836) received all objects
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(status).
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000584CD1D190
              2019-12-03 18:33:35.191  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:33:35.191  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:34:05.198  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 27068
              2019-12-03 18:34:05.726  - info: admin.0 (27068) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all states
              2019-12-03 18:34:05.741  - info: admin.0 (27068) requesting all objects
              2019-12-03 18:34:05.834  - info: admin.0 (27068) received all objects
              2019-12-03 18:34:05.920  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCCESS(s
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: tatus).
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F4826FD780
              2019-12-03 18:34:05.921  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:34:05.921  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:34:35.940  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 26364
              2019-12-03 18:34:36.465  - info: admin.0 (26364) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:34:36.476  - info: admin.0 (26364) requesting all states
              2019-12-03 18:34:36.476  - info: admin.0 (26364) requesting all objects
              2019-12-03 18:34:36.551  - info: admin.0 (26364) received all objects
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SU
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: CCESS(status).
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:36.635  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:34:36.636  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 000000F08D6FD7B0
              2019-12-03 18:34:36.636  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:34:36.636  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:35:06.642  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 8940
              2019-12-03 18:35:07.153  - info: admin.0 (8940) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:35:07.163  - info: admin.0 (8940) requesting all states
              2019-12-03 18:35:07.164  - info: admin.0 (8940) requesting all objects
              2019-12-03 18:35:07.239  - info: admin.0 (8940) received all objects
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_SUCC
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: ESS(status).
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000009CEADDD5E0
              2019-12-03 18:35:07.321  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:35:07.321  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:35:37.328  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 11144
              2019-12-03 18:35:37.879  - info: admin.0 (11144) starting. Version 3.6.12 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:35:37.890  - info: admin.0 (11144) requesting all states
              2019-12-03 18:35:37.890  - info: admin.0 (11144) requesting all objects
              2019-12-03 18:35:37.977  - info: admin.0 (11144) received all objects
              2019-12-03 18:35:38.061  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: 
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: #
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Fatal error in , line 0
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: # Check failed: U_
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: SUCCESS(status).
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #
              
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L Caught by controller[1]: #FailureMessage Object: 0000005AB47BD230
              2019-12-03 18:35:38.062  - error: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 3221225477 (3221225477)
              2019-12-03 18:35:38.062  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.admin.0 because enabled
              2019-12-03 18:36:08.083  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 started with pid 2852
              2019-12-03 18:36:08.601  - info: admin.0 (2852) starting. Version 3.6.7 in C:/iobroker/node_modules/iobroker.admin, node: v12.0.0
              2019-12-03 18:36:08.611  - info: admin.0 (2852) requesting all states
              2019-12-03 18:36:08.611  - info: admin.0 (2852) requesting all objects
              2019-12-03 18:36:08.612  - info: admin.0 (2852) Request actual repository...
              2019-12-03 18:36:08.660  - info: host.DESKTOP-D0F4V8L Update repository "default" under "http://download.iobroker.net/sources-dist.json"
              2019-12-03 18:36:08.688  - info: admin.0 (2852) received all objects
              2019-12-03 18:36:08.703  - info: admin.0 (2852) received all states
              2019-12-03 18:36:08.710  - info: admin.0 (2852) http server listening on port 8081
              2019-12-03 18:36:08.710  - info: admin.0 (2852) Use link "http://localhost:8081" to configure.
              2019-12-03 18:36:08.875  - info: admin.0 (2852) Repository received successfully.
              
              

              Der Fehler wiederholt sich ständig, bis ich wieder auf 3.6.7 zurückgesetzt habe.

              crunchipC Abwesend
              crunchipC Abwesend
              crunchip
              Forum Testing Most Active
              schrieb am zuletzt editiert von
              #5

              @ioBroker_Yasmin habe es jetzt nur auf die schnelle mit dem handy überflogen, aber es wäre möglich das dein node v12 das Problem sein könnte. Eventuell ein downgrade auf v10 und dann nochmal den admin probieren

              umgestiegen von Proxmox auf Unraid

              1 Antwort Letzte Antwort
              0
              • I Offline
                I Offline
                ioBroker_Yasmin
                schrieb am zuletzt editiert von
                #6

                @crunchip Ich hab node jetzt über den win-installer in der Version 10.17.0 installiert. Jetzt geht gar nichts mehr. npm wird nicht mehr erkannt.
                Habe dann versucht über den installer iobroker zu reparieren....ich glaub ich bin zu blond dafür...

                2019-12-07 08:38:31.864  - info: harmony.0 (11356) [CONNECT] lost Connection to Harmony Hub (192.168.178.33)
                2019-12-07 08:38:33.693  - info: alexa2.0 (2604) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                2019-12-07 08:38:39.622  - info: alexa2.0 (2604) Alexa-Push-Connection established. Disable Polling
                2019-12-07 08:38:44.050  - info: harmony.0 (11356) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                2019-12-07 09:04:10.923  - info: host.DESKTOP-D0F4V8L iobroker upgrade admin
                2019-12-07 09:04:13.971  - info: host.DESKTOP-D0F4V8L iobroker Update admin from @3.6.7 to @3.6.12
                2019-12-07 09:04:13.975  - info: host.DESKTOP-D0F4V8L iobroker host.DESKTOP-D0F4V8L Adapter "system.adapter.admin.0" is stopped.
                2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L "system.adapter.admin.0" disabled
                2019-12-07 09:04:13.980  - info: admin.0 (9380) Adapter is disabled => stop
                2019-12-07 09:04:13.984  - info: admin.0 (9380) terminating http server on port 8081
                2019-12-07 09:04:13.990  - info: admin.0 (9380) Got terminate signal TERMINATE_YOURSELF
                2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 (force=false, process=true)
                2019-12-07 09:04:13.983  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 send kill signal
                2019-12-07 09:04:13.991  - info: admin.0 (9380) terminating
                2019-12-07 09:04:13.992  - info: admin.0 (9380) Terminated (NO_ERROR): Without reason
                2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Der Befehl "npm" ist entweder falsch geschrieben oder
                konnte nicht gefunden werden.
                
                2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Error trying to check npm version: Error: Command failed: npm -vDer Befehl "npm" ist entweder falsch geschrieben oder
                konnte nicht gefunden werden.
                !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly.Use "npm install -g npm@4" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                2019-12-07 09:04:14.511  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                2019-12-07 09:04:15.029  - info: host.DESKTOP-D0F4V8L iobroker exit 30
                2019-12-07 09:08:05.142  - info: host.DESKTOP-D0F4V8L iobroker.js-controller version 2.1.1 js-controller starting
                2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
                2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L hostname: DESKTOP-D0F4V8L, node: v10.17.0
                2019-12-07 09:08:05.178  - info: host.DESKTOP-D0F4V8L ip addresses: fe80::4869:651f:dd28:fdbc 192.168.178.51 169.254.253.188
                2019-12-07 09:08:05.318  - info: host.DESKTOP-D0F4V8L connected to Objects and States
                2019-12-07 09:08:05.344  - info: host.DESKTOP-D0F4V8L 9 instances found
                2019-12-07 09:08:05.351  - info: host.DESKTOP-D0F4V8L starting 8 instances
                2019-12-07 09:08:05.367  - info: host.DESKTOP-D0F4V8L instance system.adapter.discovery.0 started with pid 9532
                2019-12-07 09:08:06.400  - info: discovery.0 (9532) starting. Version 1.3.0 in C:/iobroker/node_modules/iobroker.discovery, node: v10.17.0
                2019-12-07 09:08:09.393  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 12856
                2019-12-07 09:08:12.577  - info: tr-064.0 (12856) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                2019-12-07 09:08:13.369  - info: host.DESKTOP-D0F4V8L instance system.adapter.ping.0 started with pid 8956
                2019-12-07 09:08:13.901  - info: ping.0 (8956) starting. Version 1.3.2 in C:/iobroker/node_modules/iobroker.ping, node: v10.17.0
                2019-12-07 09:08:17.377  - info: host.DESKTOP-D0F4V8L instance system.adapter.harmony.0 started with pid 15672
                2019-12-07 09:08:17.779  - error: tr-064.0 (12856) uncaught exception: Cannot read property 'val' of undefined
                2019-12-07 09:08:17.780  - error: tr-064.0 (12856) TypeError: Cannot read property 'val' of undefined
                    at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                    at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                    at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                    at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                    at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                    at process._tickCallback (internal/process/next_tick.js:68:7)
                2019-12-07 09:08:17.784  - info: tr-064.0 (12856) terminating
                2019-12-07 09:08:17.785  - info: tr-064.0 (12856) Terminated (NO_ERROR): Without reason
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: TypeError: Cannot read property 'val' of undefined
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:68:7)
                2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR)
                2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.tr-064.0 because enabled
                2019-12-07 09:08:19.300  - info: harmony.0 (15672) starting. Version 1.2.2 in C:/iobroker/node_modules/iobroker.harmony, node: v10.17.0
                2019-12-07 09:08:19.318  - info: harmony.0 (15672) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
                2019-12-07 09:08:21.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.web.0 started with pid 15936
                2019-12-07 09:08:22.333  - info: web.0 (15936) starting. Version 2.4.10 in C:/iobroker/node_modules/iobroker.web, node: v10.17.0
                2019-12-07 09:08:22.961  - info: web.0 (15936) socket.io server listening on port 8082
                2019-12-07 09:08:22.962  - info: web.0 (15936) http server listening on port 8082
                2019-12-07 09:08:25.362  - info: host.DESKTOP-D0F4V8L instance system.adapter.history.0 started with pid 17256
                2019-12-07 09:08:26.306  - info: history.0 (17256) starting. Version 1.8.6 in C:/iobroker/node_modules/iobroker.history, node: v10.17.0
                2019-12-07 09:08:29.363  - info: host.DESKTOP-D0F4V8L instance system.adapter.javascript.0 started with pid 11396
                2019-12-07 09:08:29.568  - info: harmony.0 (15672) [DISCOVER] Discovered Harmony Hub (192.168.178.33) and will try to connect
                2019-12-07 09:08:29.589  - info: harmony.0 (15672) [CONNECT] Connecting to Harmony Hub (192.168.178.33)
                2019-12-07 09:08:30.779  - info: harmony.0 (15672) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                2019-12-07 09:08:31.551  - info: harmony.0 (15672) [PROCESS] Synced hub config for Harmony Hub (192.168.178.33)
                2019-12-07 09:08:31.792  - info: javascript.0 (11396) starting. Version 4.1.12 in C:/iobroker/node_modules/iobroker.javascript, node: v10.17.0
                2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all states
                2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all objects
                2019-12-07 09:08:31.937  - info: javascript.0 (11396) received all objects
                2019-12-07 09:08:31.939  - info: javascript.0 (11396) received all states
                2019-12-07 09:08:31.986  - info: javascript.0 (11396) Start javascript script.js.Skripte.Anrufmonitor
                2019-12-07 09:08:32.033  - info: javascript.0 (11396) script.js.Skripte.Anrufmonitor: registered 1 subscription and 0 schedules
                2019-12-07 09:08:33.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 18024
                2019-12-07 09:08:34.246  - info: alexa2.0 (18024) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                2019-12-07 09:08:46.803  - info: alexa2.0 (18024) Update cookie in adapter configuration ... restarting ...
                2019-12-07 09:08:46.805  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 (force=false, process=true)
                2019-12-07 09:08:46.806  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 send kill signal
                2019-12-07 09:08:46.817  - info: alexa2.0 (18024) Got terminate signal TERMINATE_YOURSELF
                2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Alexa-Push-Connection Error: Error: WebSocket was closed before the connection was established
                2019-12-07 09:08:46.818  - info: alexa2.0 (18024) terminating
                2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                2019-12-07 09:08:47.321  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-12-07 09:08:48.307  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 20828
                2019-12-07 09:08:49.336  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 21092
                2019-12-07 09:08:49.885  - info: tr-064.0 (20828) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                2019-12-07 09:08:50.700  - info: alexa2.0 (21092) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                2019-12-07 09:08:54.886  - info: alexa2.0 (21092) Unknown Device, but enabling commands, Try it and report back if commands work.
                2019-12-07 09:08:54.887  - info: alexa2.0 (21092) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
                2019-12-07 09:08:54.887  - info: alexa2.0 (21092)     Device-type:A30YDR2MK8HMRV (TIMERS_AND_ALARMS,SALMON,TAHOE_BYOD,PANDORA,PAIR_BT_SINK,TIMERS_ALARMS_NOTIFICATIONS_VOLUME,AUDIO_CONTROLS,CHANGE_NAME,ALEXA_PRESENCE,I_HEART_RADIO,DISPLAY_BRIGHTNESS_ADJUST,SLEEP,DREAM_TRAINING,TUPLE,CLOCK_FORMAT_24_HR,EARCONS,PAIR_BT_SOURCE,GOLDFISH,PERSISTENT_CONNECTION,VOLUME_SETTING,AMAZON_MUSIC,FAR_FIELD_WAKE_WORD,DS_VOLUME_SETTING,MICROPHONE,VOICE_TRAINING,SET_LOCALE,FLASH_BRIEFING,ALEXA_GESTURES,REQUIRES_OOBE_FOR_SETUP,MUSIC_SKILL,AUDIO_PLAYER,DISPLAY_POWER_TOGGLE,POPTART,GUARD_EARCON,REMINDERS,PAIR_REMOTE,ACTIVE_AFTER_FRO,ASCENDING_ALARM_VOLUME,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,DISPLAY_ADAPTIVE_BRIGHTNESS,CUSTOM_ALARM_TONE,KINDLE_BOOKS,ALLOW_LOG_UPLOAD,AUDIBLE,TUNE_IN,SUPPORT_CALENDAR_ALERT,SOUND_SETTINGS,BT_PAIRING_FLOW_V2,GADGETS,UPDATE_WIFI,DEREGISTER_DEVICE,TUPLE_CATEGORY_A,LEMUR_ALPHA,SUPPORTS_SOFTWARE_VERSION,DIALOG_INTERFACE_VERSION)
                2019-12-07 09:08:55.151  - info: alexa2.0 (21092) Alexa-Push-Connection established. Disable Polling
                2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52220 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52221 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-12-07 09:25:33.176  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52227 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-12-07 09:25:33.407  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52228 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                

                Ich geh mal davon aus, das es jetzt völlig hinüber ist :rolling_on_the_floor_laughing:

                crunchipC 2 Antworten Letzte Antwort
                0
                • I ioBroker_Yasmin

                  @crunchip Ich hab node jetzt über den win-installer in der Version 10.17.0 installiert. Jetzt geht gar nichts mehr. npm wird nicht mehr erkannt.
                  Habe dann versucht über den installer iobroker zu reparieren....ich glaub ich bin zu blond dafür...

                  2019-12-07 08:38:31.864  - info: harmony.0 (11356) [CONNECT] lost Connection to Harmony Hub (192.168.178.33)
                  2019-12-07 08:38:33.693  - info: alexa2.0 (2604) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                  2019-12-07 08:38:39.622  - info: alexa2.0 (2604) Alexa-Push-Connection established. Disable Polling
                  2019-12-07 08:38:44.050  - info: harmony.0 (11356) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                  2019-12-07 09:04:10.923  - info: host.DESKTOP-D0F4V8L iobroker upgrade admin
                  2019-12-07 09:04:13.971  - info: host.DESKTOP-D0F4V8L iobroker Update admin from @3.6.7 to @3.6.12
                  2019-12-07 09:04:13.975  - info: host.DESKTOP-D0F4V8L iobroker host.DESKTOP-D0F4V8L Adapter "system.adapter.admin.0" is stopped.
                  2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L "system.adapter.admin.0" disabled
                  2019-12-07 09:04:13.980  - info: admin.0 (9380) Adapter is disabled => stop
                  2019-12-07 09:04:13.984  - info: admin.0 (9380) terminating http server on port 8081
                  2019-12-07 09:04:13.990  - info: admin.0 (9380) Got terminate signal TERMINATE_YOURSELF
                  2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 (force=false, process=true)
                  2019-12-07 09:04:13.983  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 send kill signal
                  2019-12-07 09:04:13.991  - info: admin.0 (9380) terminating
                  2019-12-07 09:04:13.992  - info: admin.0 (9380) Terminated (NO_ERROR): Without reason
                  2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Der Befehl "npm" ist entweder falsch geschrieben oder
                  konnte nicht gefunden werden.
                  
                  2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Error trying to check npm version: Error: Command failed: npm -vDer Befehl "npm" ist entweder falsch geschrieben oder
                  konnte nicht gefunden werden.
                  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly.Use "npm install -g npm@4" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                  2019-12-07 09:04:14.511  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                  2019-12-07 09:04:15.029  - info: host.DESKTOP-D0F4V8L iobroker exit 30
                  2019-12-07 09:08:05.142  - info: host.DESKTOP-D0F4V8L iobroker.js-controller version 2.1.1 js-controller starting
                  2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
                  2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L hostname: DESKTOP-D0F4V8L, node: v10.17.0
                  2019-12-07 09:08:05.178  - info: host.DESKTOP-D0F4V8L ip addresses: fe80::4869:651f:dd28:fdbc 192.168.178.51 169.254.253.188
                  2019-12-07 09:08:05.318  - info: host.DESKTOP-D0F4V8L connected to Objects and States
                  2019-12-07 09:08:05.344  - info: host.DESKTOP-D0F4V8L 9 instances found
                  2019-12-07 09:08:05.351  - info: host.DESKTOP-D0F4V8L starting 8 instances
                  2019-12-07 09:08:05.367  - info: host.DESKTOP-D0F4V8L instance system.adapter.discovery.0 started with pid 9532
                  2019-12-07 09:08:06.400  - info: discovery.0 (9532) starting. Version 1.3.0 in C:/iobroker/node_modules/iobroker.discovery, node: v10.17.0
                  2019-12-07 09:08:09.393  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 12856
                  2019-12-07 09:08:12.577  - info: tr-064.0 (12856) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                  2019-12-07 09:08:13.369  - info: host.DESKTOP-D0F4V8L instance system.adapter.ping.0 started with pid 8956
                  2019-12-07 09:08:13.901  - info: ping.0 (8956) starting. Version 1.3.2 in C:/iobroker/node_modules/iobroker.ping, node: v10.17.0
                  2019-12-07 09:08:17.377  - info: host.DESKTOP-D0F4V8L instance system.adapter.harmony.0 started with pid 15672
                  2019-12-07 09:08:17.779  - error: tr-064.0 (12856) uncaught exception: Cannot read property 'val' of undefined
                  2019-12-07 09:08:17.780  - error: tr-064.0 (12856) TypeError: Cannot read property 'val' of undefined
                      at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                      at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                      at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                      at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                      at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                      at process._tickCallback (internal/process/next_tick.js:68:7)
                  2019-12-07 09:08:17.784  - info: tr-064.0 (12856) terminating
                  2019-12-07 09:08:17.785  - info: tr-064.0 (12856) Terminated (NO_ERROR): Without reason
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: TypeError: Cannot read property 'val' of undefined
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                  2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:68:7)
                  2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR)
                  2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.tr-064.0 because enabled
                  2019-12-07 09:08:19.300  - info: harmony.0 (15672) starting. Version 1.2.2 in C:/iobroker/node_modules/iobroker.harmony, node: v10.17.0
                  2019-12-07 09:08:19.318  - info: harmony.0 (15672) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
                  2019-12-07 09:08:21.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.web.0 started with pid 15936
                  2019-12-07 09:08:22.333  - info: web.0 (15936) starting. Version 2.4.10 in C:/iobroker/node_modules/iobroker.web, node: v10.17.0
                  2019-12-07 09:08:22.961  - info: web.0 (15936) socket.io server listening on port 8082
                  2019-12-07 09:08:22.962  - info: web.0 (15936) http server listening on port 8082
                  2019-12-07 09:08:25.362  - info: host.DESKTOP-D0F4V8L instance system.adapter.history.0 started with pid 17256
                  2019-12-07 09:08:26.306  - info: history.0 (17256) starting. Version 1.8.6 in C:/iobroker/node_modules/iobroker.history, node: v10.17.0
                  2019-12-07 09:08:29.363  - info: host.DESKTOP-D0F4V8L instance system.adapter.javascript.0 started with pid 11396
                  2019-12-07 09:08:29.568  - info: harmony.0 (15672) [DISCOVER] Discovered Harmony Hub (192.168.178.33) and will try to connect
                  2019-12-07 09:08:29.589  - info: harmony.0 (15672) [CONNECT] Connecting to Harmony Hub (192.168.178.33)
                  2019-12-07 09:08:30.779  - info: harmony.0 (15672) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                  2019-12-07 09:08:31.551  - info: harmony.0 (15672) [PROCESS] Synced hub config for Harmony Hub (192.168.178.33)
                  2019-12-07 09:08:31.792  - info: javascript.0 (11396) starting. Version 4.1.12 in C:/iobroker/node_modules/iobroker.javascript, node: v10.17.0
                  2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all states
                  2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all objects
                  2019-12-07 09:08:31.937  - info: javascript.0 (11396) received all objects
                  2019-12-07 09:08:31.939  - info: javascript.0 (11396) received all states
                  2019-12-07 09:08:31.986  - info: javascript.0 (11396) Start javascript script.js.Skripte.Anrufmonitor
                  2019-12-07 09:08:32.033  - info: javascript.0 (11396) script.js.Skripte.Anrufmonitor: registered 1 subscription and 0 schedules
                  2019-12-07 09:08:33.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 18024
                  2019-12-07 09:08:34.246  - info: alexa2.0 (18024) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                  2019-12-07 09:08:46.803  - info: alexa2.0 (18024) Update cookie in adapter configuration ... restarting ...
                  2019-12-07 09:08:46.805  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 (force=false, process=true)
                  2019-12-07 09:08:46.806  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 send kill signal
                  2019-12-07 09:08:46.817  - info: alexa2.0 (18024) Got terminate signal TERMINATE_YOURSELF
                  2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Alexa-Push-Connection Error: Error: WebSocket was closed before the connection was established
                  2019-12-07 09:08:46.818  - info: alexa2.0 (18024) terminating
                  2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                  2019-12-07 09:08:47.321  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                  2019-12-07 09:08:48.307  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 20828
                  2019-12-07 09:08:49.336  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 21092
                  2019-12-07 09:08:49.885  - info: tr-064.0 (20828) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                  2019-12-07 09:08:50.700  - info: alexa2.0 (21092) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                  2019-12-07 09:08:54.886  - info: alexa2.0 (21092) Unknown Device, but enabling commands, Try it and report back if commands work.
                  2019-12-07 09:08:54.887  - info: alexa2.0 (21092) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
                  2019-12-07 09:08:54.887  - info: alexa2.0 (21092)     Device-type:A30YDR2MK8HMRV (TIMERS_AND_ALARMS,SALMON,TAHOE_BYOD,PANDORA,PAIR_BT_SINK,TIMERS_ALARMS_NOTIFICATIONS_VOLUME,AUDIO_CONTROLS,CHANGE_NAME,ALEXA_PRESENCE,I_HEART_RADIO,DISPLAY_BRIGHTNESS_ADJUST,SLEEP,DREAM_TRAINING,TUPLE,CLOCK_FORMAT_24_HR,EARCONS,PAIR_BT_SOURCE,GOLDFISH,PERSISTENT_CONNECTION,VOLUME_SETTING,AMAZON_MUSIC,FAR_FIELD_WAKE_WORD,DS_VOLUME_SETTING,MICROPHONE,VOICE_TRAINING,SET_LOCALE,FLASH_BRIEFING,ALEXA_GESTURES,REQUIRES_OOBE_FOR_SETUP,MUSIC_SKILL,AUDIO_PLAYER,DISPLAY_POWER_TOGGLE,POPTART,GUARD_EARCON,REMINDERS,PAIR_REMOTE,ACTIVE_AFTER_FRO,ASCENDING_ALARM_VOLUME,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,DISPLAY_ADAPTIVE_BRIGHTNESS,CUSTOM_ALARM_TONE,KINDLE_BOOKS,ALLOW_LOG_UPLOAD,AUDIBLE,TUNE_IN,SUPPORT_CALENDAR_ALERT,SOUND_SETTINGS,BT_PAIRING_FLOW_V2,GADGETS,UPDATE_WIFI,DEREGISTER_DEVICE,TUPLE_CATEGORY_A,LEMUR_ALPHA,SUPPORTS_SOFTWARE_VERSION,DIALOG_INTERFACE_VERSION)
                  2019-12-07 09:08:55.151  - info: alexa2.0 (21092) Alexa-Push-Connection established. Disable Polling
                  2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52220 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                  2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52221 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                  2019-12-07 09:25:33.176  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52227 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                  2019-12-07 09:25:33.407  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52228 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                  

                  Ich geh mal davon aus, das es jetzt völlig hinüber ist :rolling_on_the_floor_laughing:

                  crunchipC Abwesend
                  crunchipC Abwesend
                  crunchip
                  Forum Testing Most Active
                  schrieb am zuletzt editiert von
                  #7

                  @ioBroker_Yasmin mit win installer kenne ich mich leider gar nicht aus,
                  entweder du folgst diesem Befehl

                  Aborting install because the npm version could not be checked!Please check that npm is installed correctly.Use "npm install -g npm@4" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                  

                  oder aber , mal @Stabilostick fragen, er kann mit Sicherheit helfen

                  umgestiegen von Proxmox auf Unraid

                  1 Antwort Letzte Antwort
                  0
                  • I Offline
                    I Offline
                    ioBroker_Yasmin
                    schrieb am zuletzt editiert von
                    #8

                    Naja, da der Befehl npm nicht mehr funktioniert ist das schwierig npm mit npm zu installieren

                    C:\iobroker>npm install -g npm@latest
                    Der Befehl "npm" ist entweder falsch geschrieben oder
                    konnte nicht gefunden werden.
                    
                    C:\iobroker>
                    

                    @Stabilostick Hast du eventuell noch einen Tipp?

                    sigi234S 1 Antwort Letzte Antwort
                    0
                    • I ioBroker_Yasmin

                      @crunchip Ich hab node jetzt über den win-installer in der Version 10.17.0 installiert. Jetzt geht gar nichts mehr. npm wird nicht mehr erkannt.
                      Habe dann versucht über den installer iobroker zu reparieren....ich glaub ich bin zu blond dafür...

                      2019-12-07 08:38:31.864  - info: harmony.0 (11356) [CONNECT] lost Connection to Harmony Hub (192.168.178.33)
                      2019-12-07 08:38:33.693  - info: alexa2.0 (2604) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                      2019-12-07 08:38:39.622  - info: alexa2.0 (2604) Alexa-Push-Connection established. Disable Polling
                      2019-12-07 08:38:44.050  - info: harmony.0 (11356) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                      2019-12-07 09:04:10.923  - info: host.DESKTOP-D0F4V8L iobroker upgrade admin
                      2019-12-07 09:04:13.971  - info: host.DESKTOP-D0F4V8L iobroker Update admin from @3.6.7 to @3.6.12
                      2019-12-07 09:04:13.975  - info: host.DESKTOP-D0F4V8L iobroker host.DESKTOP-D0F4V8L Adapter "system.adapter.admin.0" is stopped.
                      2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L "system.adapter.admin.0" disabled
                      2019-12-07 09:04:13.980  - info: admin.0 (9380) Adapter is disabled => stop
                      2019-12-07 09:04:13.984  - info: admin.0 (9380) terminating http server on port 8081
                      2019-12-07 09:04:13.990  - info: admin.0 (9380) Got terminate signal TERMINATE_YOURSELF
                      2019-12-07 09:04:13.982  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 (force=false, process=true)
                      2019-12-07 09:04:13.983  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.admin.0 send kill signal
                      2019-12-07 09:04:13.991  - info: admin.0 (9380) terminating
                      2019-12-07 09:04:13.992  - info: admin.0 (9380) Terminated (NO_ERROR): Without reason
                      2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Der Befehl "npm" ist entweder falsch geschrieben oder
                      konnte nicht gefunden werden.
                      
                      2019-12-07 09:04:14.021  - error: host.DESKTOP-D0F4V8L iobroker Error trying to check npm version: Error: Command failed: npm -vDer Befehl "npm" ist entweder falsch geschrieben oder
                      konnte nicht gefunden werden.
                      !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly.Use "npm install -g npm@4" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                      2019-12-07 09:04:14.511  - info: host.DESKTOP-D0F4V8L instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                      2019-12-07 09:04:15.029  - info: host.DESKTOP-D0F4V8L iobroker exit 30
                      2019-12-07 09:08:05.142  - info: host.DESKTOP-D0F4V8L iobroker.js-controller version 2.1.1 js-controller starting
                      2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
                      2019-12-07 09:08:05.145  - info: host.DESKTOP-D0F4V8L hostname: DESKTOP-D0F4V8L, node: v10.17.0
                      2019-12-07 09:08:05.178  - info: host.DESKTOP-D0F4V8L ip addresses: fe80::4869:651f:dd28:fdbc 192.168.178.51 169.254.253.188
                      2019-12-07 09:08:05.318  - info: host.DESKTOP-D0F4V8L connected to Objects and States
                      2019-12-07 09:08:05.344  - info: host.DESKTOP-D0F4V8L 9 instances found
                      2019-12-07 09:08:05.351  - info: host.DESKTOP-D0F4V8L starting 8 instances
                      2019-12-07 09:08:05.367  - info: host.DESKTOP-D0F4V8L instance system.adapter.discovery.0 started with pid 9532
                      2019-12-07 09:08:06.400  - info: discovery.0 (9532) starting. Version 1.3.0 in C:/iobroker/node_modules/iobroker.discovery, node: v10.17.0
                      2019-12-07 09:08:09.393  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 12856
                      2019-12-07 09:08:12.577  - info: tr-064.0 (12856) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                      2019-12-07 09:08:13.369  - info: host.DESKTOP-D0F4V8L instance system.adapter.ping.0 started with pid 8956
                      2019-12-07 09:08:13.901  - info: ping.0 (8956) starting. Version 1.3.2 in C:/iobroker/node_modules/iobroker.ping, node: v10.17.0
                      2019-12-07 09:08:17.377  - info: host.DESKTOP-D0F4V8L instance system.adapter.harmony.0 started with pid 15672
                      2019-12-07 09:08:17.779  - error: tr-064.0 (12856) uncaught exception: Cannot read property 'val' of undefined
                      2019-12-07 09:08:17.780  - error: tr-064.0 (12856) TypeError: Cannot read property 'val' of undefined
                          at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                          at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                          at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                          at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                          at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                          at process._tickCallback (internal/process/next_tick.js:68:7)
                      2019-12-07 09:08:17.784  - info: tr-064.0 (12856) terminating
                      2019-12-07 09:08:17.785  - info: tr-064.0 (12856) Terminated (NO_ERROR): Without reason
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]: TypeError: Cannot read property 'val' of undefined
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at Devices.setState (C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:642:36)
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at C:\iobroker\node_modules\iobroker.tr-064\node_modules\soef\soef.js:609:26
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at (anonymous function).(anonymous function)._0x5c1e98 (C:\iobroker\node_modules\iobroker.js-controller\node_modules\iobroker.objects-redis\index.js:17:76202)
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at tryCatcher (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\utils.js:11:23)
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at promise.then (C:\iobroker\node_modules\iobroker.js-controller\node_modules\standard-as-callback\built\index.js:19:49)
                      2019-12-07 09:08:18.293  - error: host.DESKTOP-D0F4V8L Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:68:7)
                      2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR)
                      2019-12-07 09:08:18.294  - info: host.DESKTOP-D0F4V8L Restart adapter system.adapter.tr-064.0 because enabled
                      2019-12-07 09:08:19.300  - info: harmony.0 (15672) starting. Version 1.2.2 in C:/iobroker/node_modules/iobroker.harmony, node: v10.17.0
                      2019-12-07 09:08:19.318  - info: harmony.0 (15672) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
                      2019-12-07 09:08:21.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.web.0 started with pid 15936
                      2019-12-07 09:08:22.333  - info: web.0 (15936) starting. Version 2.4.10 in C:/iobroker/node_modules/iobroker.web, node: v10.17.0
                      2019-12-07 09:08:22.961  - info: web.0 (15936) socket.io server listening on port 8082
                      2019-12-07 09:08:22.962  - info: web.0 (15936) http server listening on port 8082
                      2019-12-07 09:08:25.362  - info: host.DESKTOP-D0F4V8L instance system.adapter.history.0 started with pid 17256
                      2019-12-07 09:08:26.306  - info: history.0 (17256) starting. Version 1.8.6 in C:/iobroker/node_modules/iobroker.history, node: v10.17.0
                      2019-12-07 09:08:29.363  - info: host.DESKTOP-D0F4V8L instance system.adapter.javascript.0 started with pid 11396
                      2019-12-07 09:08:29.568  - info: harmony.0 (15672) [DISCOVER] Discovered Harmony Hub (192.168.178.33) and will try to connect
                      2019-12-07 09:08:29.589  - info: harmony.0 (15672) [CONNECT] Connecting to Harmony Hub (192.168.178.33)
                      2019-12-07 09:08:30.779  - info: harmony.0 (15672) [CONNECT] Connected to Harmony Hub (192.168.178.33)
                      2019-12-07 09:08:31.551  - info: harmony.0 (15672) [PROCESS] Synced hub config for Harmony Hub (192.168.178.33)
                      2019-12-07 09:08:31.792  - info: javascript.0 (11396) starting. Version 4.1.12 in C:/iobroker/node_modules/iobroker.javascript, node: v10.17.0
                      2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all states
                      2019-12-07 09:08:31.812  - info: javascript.0 (11396) requesting all objects
                      2019-12-07 09:08:31.937  - info: javascript.0 (11396) received all objects
                      2019-12-07 09:08:31.939  - info: javascript.0 (11396) received all states
                      2019-12-07 09:08:31.986  - info: javascript.0 (11396) Start javascript script.js.Skripte.Anrufmonitor
                      2019-12-07 09:08:32.033  - info: javascript.0 (11396) script.js.Skripte.Anrufmonitor: registered 1 subscription and 0 schedules
                      2019-12-07 09:08:33.364  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 18024
                      2019-12-07 09:08:34.246  - info: alexa2.0 (18024) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                      2019-12-07 09:08:46.803  - info: alexa2.0 (18024) Update cookie in adapter configuration ... restarting ...
                      2019-12-07 09:08:46.805  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 (force=false, process=true)
                      2019-12-07 09:08:46.806  - info: host.DESKTOP-D0F4V8L stopInstance system.adapter.alexa2.0 send kill signal
                      2019-12-07 09:08:46.817  - info: alexa2.0 (18024) Got terminate signal TERMINATE_YOURSELF
                      2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Alexa-Push-Connection Error: Error: WebSocket was closed before the connection was established
                      2019-12-07 09:08:46.818  - info: alexa2.0 (18024) terminating
                      2019-12-07 09:08:46.818  - info: alexa2.0 (18024) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2019-12-07 09:08:47.321  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                      2019-12-07 09:08:48.307  - info: host.DESKTOP-D0F4V8L instance system.adapter.tr-064.0 started with pid 20828
                      2019-12-07 09:08:49.336  - info: host.DESKTOP-D0F4V8L instance system.adapter.alexa2.0 started with pid 21092
                      2019-12-07 09:08:49.885  - info: tr-064.0 (20828) starting. Version 0.4.18 in C:/iobroker/node_modules/iobroker.tr-064, node: v10.17.0
                      2019-12-07 09:08:50.700  - info: alexa2.0 (21092) starting. Version 2.6.4 in C:/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
                      2019-12-07 09:08:54.886  - info: alexa2.0 (21092) Unknown Device, but enabling commands, Try it and report back if commands work.
                      2019-12-07 09:08:54.887  - info: alexa2.0 (21092) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
                      2019-12-07 09:08:54.887  - info: alexa2.0 (21092)     Device-type:A30YDR2MK8HMRV (TIMERS_AND_ALARMS,SALMON,TAHOE_BYOD,PANDORA,PAIR_BT_SINK,TIMERS_ALARMS_NOTIFICATIONS_VOLUME,AUDIO_CONTROLS,CHANGE_NAME,ALEXA_PRESENCE,I_HEART_RADIO,DISPLAY_BRIGHTNESS_ADJUST,SLEEP,DREAM_TRAINING,TUPLE,CLOCK_FORMAT_24_HR,EARCONS,PAIR_BT_SOURCE,GOLDFISH,PERSISTENT_CONNECTION,VOLUME_SETTING,AMAZON_MUSIC,FAR_FIELD_WAKE_WORD,DS_VOLUME_SETTING,MICROPHONE,VOICE_TRAINING,SET_LOCALE,FLASH_BRIEFING,ALEXA_GESTURES,REQUIRES_OOBE_FOR_SETUP,MUSIC_SKILL,AUDIO_PLAYER,DISPLAY_POWER_TOGGLE,POPTART,GUARD_EARCON,REMINDERS,PAIR_REMOTE,ACTIVE_AFTER_FRO,ASCENDING_ALARM_VOLUME,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,DISPLAY_ADAPTIVE_BRIGHTNESS,CUSTOM_ALARM_TONE,KINDLE_BOOKS,ALLOW_LOG_UPLOAD,AUDIBLE,TUNE_IN,SUPPORT_CALENDAR_ALERT,SOUND_SETTINGS,BT_PAIRING_FLOW_V2,GADGETS,UPDATE_WIFI,DEREGISTER_DEVICE,TUPLE_CATEGORY_A,LEMUR_ALPHA,SUPPORTS_SOFTWARE_VERSION,DIALOG_INTERFACE_VERSION)
                      2019-12-07 09:08:55.151  - info: alexa2.0 (21092) Alexa-Push-Connection established. Disable Polling
                      2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52220 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                      2019-12-07 09:25:32.309  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52221 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                      2019-12-07 09:25:33.176  - error: host.DESKTOP-D0F4V8L States 127.0.0.1:52227 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                      2019-12-07 09:25:33.407  - error: host.DESKTOP-D0F4V8L Objects 127.0.0.1:52228 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                      

                      Ich geh mal davon aus, das es jetzt völlig hinüber ist :rolling_on_the_floor_laughing:

                      crunchipC Abwesend
                      crunchipC Abwesend
                      crunchip
                      Forum Testing Most Active
                      schrieb am zuletzt editiert von
                      #9

                      @ioBroker_Yasmin vllt bringt dich das hier auch weiter
                      https://www.iobroker.net/#de/documentation/install/windows.md

                      umgestiegen von Proxmox auf Unraid

                      1 Antwort Letzte Antwort
                      0
                      • I ioBroker_Yasmin

                        Naja, da der Befehl npm nicht mehr funktioniert ist das schwierig npm mit npm zu installieren

                        C:\iobroker>npm install -g npm@latest
                        Der Befehl "npm" ist entweder falsch geschrieben oder
                        konnte nicht gefunden werden.
                        
                        C:\iobroker>
                        

                        @Stabilostick Hast du eventuell noch einen Tipp?

                        sigi234S Online
                        sigi234S Online
                        sigi234
                        Forum Testing Most Active
                        schrieb am zuletzt editiert von
                        #10

                        @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                        Naja, da der Befehl npm nicht mehr funktioniert ist das schwierig npm mit npm zu installieren

                        Was kommt bei:

                        cd..iobroker
                        iobroker list instances
                        node -v
                        nodejs -v
                        npm -v

                        Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Immer Daten sichern!

                        I 1 Antwort Letzte Antwort
                        0
                        • sigi234S sigi234

                          @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                          Naja, da der Befehl npm nicht mehr funktioniert ist das schwierig npm mit npm zu installieren

                          Was kommt bei:

                          cd..iobroker
                          iobroker list instances
                          node -v
                          nodejs -v
                          npm -v

                          I Offline
                          I Offline
                          ioBroker_Yasmin
                          schrieb am zuletzt editiert von
                          #11

                          @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                          Was kommt bei:

                          cd..iobroker
                          iobroker list instances
                          node -v
                          nodejs -v
                          npm -v

                          C:\iobroker>iobroker list instances
                          
                          C:\iobroker>node node_modules/iobroker.js-controller/iobroker.js list instances
                          Das System kann den angegebenen Pfad nicht finden.
                          
                          C:\iobroker>node -v
                          Das System kann den angegebenen Pfad nicht finden.
                          
                          C:\iobroker>nodejs -v
                          Der Befehl "nodejs" ist entweder falsch geschrieben oder
                          konnte nicht gefunden werden.
                          
                          C:\iobroker>npm -v
                          Der Befehl "npm" ist entweder falsch geschrieben oder
                          konnte nicht gefunden werden.
                          
                          C:\iobroker>
                          
                          sigi234S 1 Antwort Letzte Antwort
                          0
                          • I ioBroker_Yasmin

                            @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                            Was kommt bei:

                            cd..iobroker
                            iobroker list instances
                            node -v
                            nodejs -v
                            npm -v

                            C:\iobroker>iobroker list instances
                            
                            C:\iobroker>node node_modules/iobroker.js-controller/iobroker.js list instances
                            Das System kann den angegebenen Pfad nicht finden.
                            
                            C:\iobroker>node -v
                            Das System kann den angegebenen Pfad nicht finden.
                            
                            C:\iobroker>nodejs -v
                            Der Befehl "nodejs" ist entweder falsch geschrieben oder
                            konnte nicht gefunden werden.
                            
                            C:\iobroker>npm -v
                            Der Befehl "npm" ist entweder falsch geschrieben oder
                            konnte nicht gefunden werden.
                            
                            C:\iobroker>
                            
                            sigi234S Online
                            sigi234S Online
                            sigi234
                            Forum Testing Most Active
                            schrieb am zuletzt editiert von
                            #12

                            @ioBroker_Yasmin
                            Bist du im Richtigen Verzeichnis?
                            Wie hast du installiert?
                            Welche Version von Installer?

                            Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                            Immer Daten sichern!

                            I 1 Antwort Letzte Antwort
                            0
                            • sigi234S sigi234

                              @ioBroker_Yasmin
                              Bist du im Richtigen Verzeichnis?
                              Wie hast du installiert?
                              Welche Version von Installer?

                              I Offline
                              I Offline
                              ioBroker_Yasmin
                              schrieb am zuletzt editiert von
                              #13

                              @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                              @ioBroker_Yasmin
                              Bist du im Richtigen Verzeichnis?
                              Wie hast du installiert?
                              Welche Version von Installer?

                              Ja, ich bin im richtigen Verzeichnis. Mit welcher Version ich ursprünglich installiert habe, kann ich nicht mehr sagen.
                              Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                              sigi234S 1 Antwort Letzte Antwort
                              0
                              • I ioBroker_Yasmin

                                @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                @ioBroker_Yasmin
                                Bist du im Richtigen Verzeichnis?
                                Wie hast du installiert?
                                Welche Version von Installer?

                                Ja, ich bin im richtigen Verzeichnis. Mit welcher Version ich ursprünglich installiert habe, kann ich nicht mehr sagen.
                                Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                sigi234S Online
                                sigi234S Online
                                sigi234
                                Forum Testing Most Active
                                schrieb am zuletzt editiert von sigi234
                                #14

                                @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                Nimm diesen:

                                https://www.iobroker.net/#de/download

                                Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast. Lösche nicht die alte Installation und sichere dir den Ordner iobroker-data

                                Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                Immer Daten sichern!

                                I 1 Antwort Letzte Antwort
                                1
                                • sigi234S sigi234

                                  @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                  Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                  Nimm diesen:

                                  https://www.iobroker.net/#de/download

                                  Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                  Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast. Lösche nicht die alte Installation und sichere dir den Ordner iobroker-data

                                  I Offline
                                  I Offline
                                  ioBroker_Yasmin
                                  schrieb am zuletzt editiert von
                                  #15

                                  @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                  @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                  Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                  Nimm diesen:

                                  https://www.iobroker.net/#de/download

                                  Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                  Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast.

                                  Ok, hab mit dem Installer die alte Installation entfernt und setzte jetzt alles neu auf.
                                  Danke für die Hilfe. Bin hier echt verzweifelt.

                                  sigi234S 1 Antwort Letzte Antwort
                                  0
                                  • I ioBroker_Yasmin

                                    @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                    @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                    Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                    Nimm diesen:

                                    https://www.iobroker.net/#de/download

                                    Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                    Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast.

                                    Ok, hab mit dem Installer die alte Installation entfernt und setzte jetzt alles neu auf.
                                    Danke für die Hilfe. Bin hier echt verzweifelt.

                                    sigi234S Online
                                    sigi234S Online
                                    sigi234
                                    Forum Testing Most Active
                                    schrieb am zuletzt editiert von
                                    #16

                                    @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                    @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                    @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                    Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                    Nimm diesen:

                                    https://www.iobroker.net/#de/download

                                    Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                    Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast.

                                    Ok, hab mit dem Installer die alte Installation entfernt und setzte jetzt alles neu auf.
                                    Danke für die Hilfe. Bin hier echt verzweifelt.

                                    Ok, dann mach jetzt eine saubere Neuinstallation.

                                    Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                    Immer Daten sichern!

                                    I 1 Antwort Letzte Antwort
                                    0
                                    • sigi234S sigi234

                                      @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                      Nimm diesen:

                                      https://www.iobroker.net/#de/download

                                      Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                      Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast.

                                      Ok, hab mit dem Installer die alte Installation entfernt und setzte jetzt alles neu auf.
                                      Danke für die Hilfe. Bin hier echt verzweifelt.

                                      Ok, dann mach jetzt eine saubere Neuinstallation.

                                      I Offline
                                      I Offline
                                      ioBroker_Yasmin
                                      schrieb am zuletzt editiert von
                                      #17

                                      @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      @sigi234 sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      @ioBroker_Yasmin sagte in Fehler nach Admin-Adapter update auf 3.6.12:

                                      Der Installer den ich heute benutzt habe ist iobroker-1.5.11.a-windows-installer.exe

                                      Nimm diesen:

                                      https://www.iobroker.net/#de/download

                                      Virenscanner deaktivieren , entweder eine neue Installation oder Migration.
                                      Falls Migration : dauert sehr lange, es werden dann nach und nach die Adapter installiert außer die die du aus eigener Url installiert hast.

                                      Ok, hab mit dem Installer die alte Installation entfernt und setzte jetzt alles neu auf.
                                      Danke für die Hilfe. Bin hier echt verzweifelt.

                                      Ok, dann mach jetzt eine saubere Neuinstallation.

                                      Ok, läuft alles wieder. Meine Skripte hatte ich zum Glück gesichert.

                                      Danke nochmal

                                      1 Antwort Letzte Antwort
                                      0
                                      Antworten
                                      • In einem neuen Thema antworten
                                      Anmelden zum Antworten
                                      • Älteste zuerst
                                      • Neuste zuerst
                                      • Meiste Stimmen


                                      Support us

                                      ioBroker
                                      Community Adapters
                                      Donate

                                      642

                                      Online

                                      32.5k

                                      Benutzer

                                      81.7k

                                      Themen

                                      1.3m

                                      Beiträge
                                      Community
                                      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                      ioBroker Community 2014-2025
                                      logo
                                      • Anmelden

                                      • Du hast noch kein Konto? Registrieren

                                      • Anmelden oder registrieren, um zu suchen
                                      • Erster Beitrag
                                        Letzter Beitrag
                                      0
                                      • Home
                                      • Aktuell
                                      • Tags
                                      • Ungelesen 0
                                      • Kategorien
                                      • Unreplied
                                      • Beliebt
                                      • GitHub
                                      • Docu
                                      • Hilfe