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

  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Proxmox iso

NEWS

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

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

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

Proxmox iso

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
89 Beiträge 9 Kommentatoren 9.7k Aufrufe 1 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.
  • eric2905E Offline
    eric2905E Offline
    eric2905
    schrieb am zuletzt editiert von
    #6

    Hast Du wenigstens mal ein paar Screenshots und/oder Logs?

    Aus der minimalen Beschreibung wird so keiner schlau (ist wie „druckt nicht“).

    Gruß,

    Eric

    Von unterwegs getippert

    Roses are red, violets are blue,

    if I listen to metal, my neighbours do too

    1 Antwort Letzte Antwort
    0
    • WebrangerW Offline
      WebrangerW Offline
      Webranger
      schrieb am zuletzt editiert von
      #7

      Momentan probier ich noch rum.

      Da ist die snapshoot funktion ja mehr als praktisch.

      Helfen würde mir aber jetzt um zu testen ob das einspielen des Backups funktioniert wie ich iobroker deinstallieren kann und dann version 2.9 drauf bekomme.

      Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

      1 Antwort Letzte Antwort
      0
      • eric2905E Offline
        eric2905E Offline
        eric2905
        schrieb am zuletzt editiert von
        #8

        Was sieht „wild aus“?

        Ein Restore sollte auf jeden Fall gehen.

        Gruß,

        Eric

        Von unterwegs getippert

        Roses are red, violets are blue,

        if I listen to metal, my neighbours do too

        1 Antwort Letzte Antwort
        0
        • WebrangerW Offline
          WebrangerW Offline
          Webranger
          schrieb am zuletzt editiert von
          #9

          So nochmal einen restore gemacht.

          So sieht das dann aus:

          2958_bildschirmfoto_2018-02-25_um_11.06.59.png

          2958_bildschirmfoto_2018-02-25_um_11.06.16.png

          2958_bildschirmfoto_2018-02-25_um_11.05.54.png

          2958_bildschirmfoto_2018-02-25_um_11.05.46.png

          Aber ich seh gerade in den LOGs das er dort noch ordentlich am "rödeln" ist.

          Ich lass ihn mal machen und warte mal ab was passiert.

          Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

          1 Antwort Letzte Antwort
          0
          • eric2905E Offline
            eric2905E Offline
            eric2905
            schrieb am zuletzt editiert von
            #10

            Wie bereits ein paar mal im Forum zu lesen ist, dauert es ein paar Stunden, bis nach einem Restore alles wieder funktioniert.

            Es werden alle benötigten Adapter auf dem neuen Host geladen, installiert (ggf. sogar kompiliert), konfiguriert, usw.

            Warte einfach mal ab.

            Gruß,

            Eric

            Von unterwegs getippert

            Roses are red, violets are blue,

            if I listen to metal, my neighbours do too

            1 Antwort Letzte Antwort
            0
            • WebrangerW Offline
              WebrangerW Offline
              Webranger
              schrieb am zuletzt editiert von
              #11

              Ist halt nur jetzt schon ziemlich viel rot in den logs zu sehen mit keine Berechtigung usw.

              Aber ich melde mich später wenn er durch ist.

              Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

              1 Antwort Letzte Antwort
              0
              • eric2905E Offline
                eric2905E Offline
                eric2905
                schrieb am zuletzt editiert von
                #12

                @ringdingringding:

                Ist halt nur jetzt schon ziemlich viel rot in den logs zu sehen mit keine Berechtigung usw. `
                Welche Logs?

                Ich sehe keinen einzigen Log-Auszug im Thread …

                Gruß,

                Eric

                Von unterwegs getippert

                Roses are red, violets are blue,

                if I listen to metal, my neighbours do too

                1 Antwort Letzte Antwort
                0
                • WebrangerW Offline
                  WebrangerW Offline
                  Webranger
                  schrieb am zuletzt editiert von
                  #13

                  Hier mal die logs während des restores

                  ! ` > 2018-02-25 11:53:19.204 - error: rpi2.0 No Value found for soc_temp

                  2018-02-25 11:53:39.726 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7086

                  2018-02-25 11:53:40.542 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:53:40.589 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:53:40.672 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:53:40.673 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:53:40.685 - info: mihome.0 terminating

                  2018-02-25 11:53:40.695 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:53:40.695 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:53:40.695 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:53:40.695 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:53:40.696 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:53:40.696 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:53:40.697 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:53:40.725 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7096

                  2018-02-25 11:53:41.587 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:53:41.675 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:53:41.703 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:53:41.704 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:53:41.753 - info: history.0 terminating

                  2018-02-25 11:53:41.763 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:53:41.763 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:53:41.763 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:53:41.763 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:53:41.763 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:53:41.764 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:53:41.765 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:53:41.765 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:53:41.765 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:53:41.766 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:53:41.766 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:54:00.022 - info: host.debian-iobroker instance system.adapter.tankerkoenig.0 started with pid 7106

                  2018-02-25 11:54:01.229 - info: tankerkoenig.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:54:01.275 - info: tankerkoenig.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v6.13.0

                  2018-02-25 11:54:01.510 - info: tankerkoenig.0 objects written

                  2018-02-25 11:54:01.808 - info: host.debian-iobroker instance system.adapter.tankerkoenig.0 terminated with code 0 (OK)

                  2018-02-25 11:54:10.708 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7118

                  2018-02-25 11:54:11.600 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:54:11.649 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:54:11.731 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:54:11.732 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:54:11.745 - info: mihome.0 terminating

                  2018-02-25 11:54:11.755 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:54:11.755 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:54:11.756 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:54:11.756 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:54:11.756 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:54:11.756 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:54:11.756 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:54:11.757 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:54:11.757 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:54:11.757 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:54:11.757 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:54:11.757 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:54:11.787 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7128

                  2018-02-25 11:54:12.652 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:54:12.737 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:54:12.760 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:54:12.760 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:54:12.800 - info: history.0 terminating

                  2018-02-25 11:54:12.810 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:54:12.810 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:54:12.810 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:54:12.810 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:54:12.811 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:54:12.811 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:54:12.811 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:54:12.811 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:54:12.811 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:54:12.813 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:54:12.813 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:54:12.813 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:54:12.814 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:54:12.814 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:54:12.814 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:54:12.814 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:54:12.814 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:54:19.328 - error: rpi2.0 No Value found for cpu_frequency

                  2018-02-25 11:54:19.335 - error: rpi2.0 No Value found for scaling_governor

                  2018-02-25 11:54:19.339 - error: rpi2.0 No Value found for memory_available

                  2018-02-25 11:54:19.339 - error: rpi2.0 No Value found for net_received

                  2018-02-25 11:54:19.339 - error: rpi2.0 No Value found for net_send

                  2018-02-25 11:54:19.340 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966712 25316220 8% /

                  /1024

                  2018-02-25 11:54:19.342 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966712 25316220 8% /

                  /1024

                  2018-02-25 11:54:19.343 - error: rpi2.0 No Value found for soc_temp

                  2018-02-25 11:54:41.767 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7174

                  2018-02-25 11:54:42.601 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:54:42.648 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:54:42.730 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:54:42.731 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:54:42.743 - info: mihome.0 terminating

                  2018-02-25 11:54:42.755 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:54:42.755 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:54:42.755 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:54:42.756 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:54:42.756 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:54:42.756 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:54:42.823 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7184

                  2018-02-25 11:54:43.780 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:54:43.868 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:54:43.889 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:54:43.890 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:54:43.929 - info: history.0 terminating

                  2018-02-25 11:54:43.939 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:54:43.939 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:54:43.940 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:54:43.941 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:54:43.941 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:54:43.941 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:54:43.941 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:54:43.941 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:55:00.020 - info: host.debian-iobroker instance system.adapter.tvspielfilm.0 started with pid 7195

                  2018-02-25 11:55:01.256 - info: tvspielfilm.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:55:01.300 - info: tvspielfilm.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v6.13.0

                  2018-02-25 11:55:01.352 - info: tvspielfilm.0 objects written

                  2018-02-25 11:55:12.767 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7207

                  2018-02-25 11:55:13.778 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:55:13.863 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:55:13.955 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:55:13.959 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7217

                  2018-02-25 11:55:13.956 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:55:13.981 - info: mihome.0 terminating

                  2018-02-25 11:55:13.999 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:55:14.000 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:55:14.001 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:55:14.001 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:55:14.001 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:55:14.001 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:55:14.001 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:55:14.849 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:55:14.937 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:55:14.961 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:55:14.961 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:55:15.011 - info: history.0 terminating

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:55:15.021 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:55:15.022 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:55:15.022 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:55:15.022 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:55:15.022 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:55:15.023 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:55:15.023 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:55:15.023 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:55:15.023 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:55:15.023 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:55:15.023 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:55:15.023 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:55:19.488 - error: rpi2.0 No Value found for cpu_frequency

                  2018-02-25 11:55:19.492 - error: rpi2.0 No Value found for scaling_governor

                  2018-02-25 11:55:19.494 - error: rpi2.0 No Value found for memory_available

                  2018-02-25 11:55:19.494 - error: rpi2.0 No Value found for net_received

                  2018-02-25 11:55:19.495 - error: rpi2.0 No Value found for net_send

                  2018-02-25 11:55:19.497 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966724 25316208 8% /

                  /1024

                  2018-02-25 11:55:19.498 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966724 25316208 8% /

                  /1024

                  2018-02-25 11:55:19.500 - error: rpi2.0 No Value found for soc_temp

                  2018-02-25 11:55:44.011 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7263

                  2018-02-25 11:55:44.845 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:55:44.930 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:55:45.037 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7273

                  2018-02-25 11:55:45.031 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:55:45.040 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:55:45.060 - info: mihome.0 terminating

                  2018-02-25 11:55:45.076 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:55:45.079 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:55:45.080 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:55:45.080 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:55:45.081 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:55:45.081 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:55:45.081 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:55:45.966 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:55:46.014 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:55:46.039 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:55:46.039 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:55:46.079 - info: history.0 terminating

                  2018-02-25 11:55:46.090 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:55:46.090 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:55:46.091 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:55:46.091 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:55:46.091 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:55:46.091 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:55:46.091 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:55:46.092 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:55:46.093 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:55:46.093 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:56:01.362 - info: tvspielfilm.0 force terminating adapter after 1 minute

                  2018-02-25 11:56:01.876 - info: host.debian-iobroker instance system.adapter.tvspielfilm.0 terminated with code 0 (OK)

                  2018-02-25 11:56:15.091 - info: host.debian-iobroker instance system.adapter.mihome.0 started with pid 7285

                  2018-02-25 11:56:15.977 - info: mihome.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:56:16.025 - info: mihome.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.mihome, node: v6.13.0

                  2018-02-25 11:56:16.112 - info: host.debian-iobroker instance system.adapter.history.0 started with pid 7295

                  2018-02-25 11:56:16.133 - error: mihome.0 uncaught exception: addMembership ENODEV

                  2018-02-25 11:56:16.133 - error: mihome.0 Error: addMembership ENODEV

                  at exports._errnoException (util.js:1020:11)

                  at Socket.addMembership (dgram.js:519:11)

                  at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  at emitNone (events.js:86:13)

                  at Socket.emit (events.js:185:7)

                  at startListening (dgram.js:121:10)

                  at _handle.lookup (dgram.js:226:7)

                  at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  at process._tickCallback (internal/process/next_tick.js:104:9)

                  2018-02-25 11:56:16.152 - info: mihome.0 terminating

                  2018-02-25 11:56:16.169 - error: Caught by controller[0]: { Error: addMembership ENODEV

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at exports._errnoException (util.js:1020:11)

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at Socket.addMembership (dgram.js:519:11)

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/mihome/Hub.js:101:25)

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at emitNone (events.js:86:13)

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at Socket.emit (events.js:185:7)

                  2018-02-25 11:56:16.171 - error: Caught by controller[0]: at startListening (dgram.js:121:10)

                  2018-02-25 11:56:16.173 - error: Caught by controller[0]: at _handle.lookup (dgram.js:226:7)

                  2018-02-25 11:56:16.174 - error: Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:83:11)

                  2018-02-25 11:56:16.174 - error: Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENODEV', errno: 'ENODEV', syscall: 'addMembership' }

                  2018-02-25 11:56:16.179 - error: host.debian-iobroker instance system.adapter.mihome.0 terminated with code 0 (OK)

                  2018-02-25 11:56:16.179 - info: host.debian-iobroker Restart adapter system.adapter.mihome.0 because enabled

                  2018-02-25 11:56:17.021 - info: history.0 States connected to redis: 127.0.0.1:6379

                  2018-02-25 11:56:17.069 - info: history.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0

                  2018-02-25 11:56:17.090 - error: history.0 uncaught exception: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:56:17.091 - error: history.0 Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  at Error (native)

                  at Object.fs.mkdirSync (fs.js:932:18)

                  at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:56:17.129 - info: history.0 terminating

                  2018-02-25 11:56:17.139 - error: Caught by controller[0]: { Error: ENOENT: no such file or directory, mkdir '/media/usb/History/'

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at Error (native)

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at Object.fs.mkdirSync (fs.js:932:18)

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at main (/opt/iobroker/node_modules/iobroker.history/history.js:319:12)

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at Object.ready (/opt/iobroker/node_modules/iobroker.history/history.js:114:9)

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4658:62)

                  2018-02-25 11:56:17.140 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)

                  2018-02-25 11:56:17.141 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

                  2018-02-25 11:56:17.141 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

                  2018-02-25 11:56:17.141 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

                  2018-02-25 11:56:17.141 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                  2018-02-25 11:56:17.141 - error: Caught by controller[0]: errno: -2,

                  2018-02-25 11:56:17.142 - error: Caught by controller[0]: code: 'ENOENT',

                  2018-02-25 11:56:17.142 - error: Caught by controller[0]: syscall: 'mkdir',

                  2018-02-25 11:56:17.142 - error: Caught by controller[0]: path: '/media/usb/History/' }

                  2018-02-25 11:56:17.142 - error: host.debian-iobroker instance system.adapter.history.0 terminated with code 0 (OK)

                  2018-02-25 11:56:17.142 - info: host.debian-iobroker Restart adapter system.adapter.history.0 because enabled

                  2018-02-25 11:56:19.648 - error: rpi2.0 No Value found for cpu_frequency

                  2018-02-25 11:56:19.651 - error: rpi2.0 No Value found for scaling_governor

                  2018-02-25 11:56:19.653 - error: rpi2.0 No Value found for memory_available

                  2018-02-25 11:56:19.653 - error: rpi2.0 No Value found for net_received

                  2018-02-25 11:56:19.654 - error: rpi2.0 No Value found for net_send

                  2018-02-25 11:56:19.655 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966740 25316192 8% /

                  /1024

                  2018-02-25 11:56:19.656 - error: rpi2.0 Cannot evaluate: Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf

                  /dev/sda1 28767268 1966740 25316192 8% /

                  /1024

                  2018-02-25 11:56:19.657 - error: rpi2.0 No Value found for soc_temp `

                  Die History errors kann ich mir sogar erklären weil ich die ausgelagert hatte auf usb und der ja nun nicht da ist.

                  Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

                  1 Antwort Letzte Antwort
                  0
                  • HomoranH Nicht stören
                    HomoranH Nicht stören
                    Homoran
                    Global Moderator Administrators
                    schrieb am zuletzt editiert von
                    #14

                    Welche node- Version?

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

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

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

                    1 Antwort Letzte Antwort
                    0
                    • eric2905E Offline
                      eric2905E Offline
                      eric2905
                      schrieb am zuletzt editiert von
                      #15

                      Das Backup stammt von einem Pi - zumindest sehe ich im Log den Pi-Adapter, der natürlich jetzt nicht mehr viel bringt.

                      Warte erst mal ab, bis der Restore durch ist. Ggf. musste Du auch noch das Restore.sh Script ausführen, damit Adapter neu für die geänderte Hardware kompiliert werden (steht auch schon ein oder zweimal im Forum).

                      Gruß,

                      Eric

                      Von unterwegs getippert

                      Roses are red, violets are blue,

                      if I listen to metal, my neighbours do too

                      1 Antwort Letzte Antwort
                      0
                      • WebrangerW Offline
                        WebrangerW Offline
                        Webranger
                        schrieb am zuletzt editiert von
                        #16

                        das ist richtig das das backup von einem pi ist.

                        Zieh davon ja um auf einen nuc mit proxmox

                        ;)

                        Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

                        1 Antwort Letzte Antwort
                        0
                        • eric2905E Offline
                          eric2905E Offline
                          eric2905
                          schrieb am zuletzt editiert von
                          #17

                          @Homoran:

                          Welche node- Version? `
                          Laut Log Node6

                          Von unterwegs getippert

                          Roses are red, violets are blue,

                          if I listen to metal, my neighbours do too

                          1 Antwort Letzte Antwort
                          0
                          • HomoranH Nicht stören
                            HomoranH Nicht stören
                            Homoran
                            Global Moderator Administrators
                            schrieb am zuletzt editiert von
                            #18

                            Hab ich nicht gesehen :oops:

                            Aber den ENODEV.

                            ist es denn die Node-Version für die jetzige Hardware?

                            Sorry!!!

                            ENODEV ist Error NO DEVice und nicht nodeVersion

                            Gruß

                            Rainer

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

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

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

                            1 Antwort Letzte Antwort
                            0
                            • WebrangerW Offline
                              WebrangerW Offline
                              Webranger
                              schrieb am zuletzt editiert von
                              #19

                              @eric2905:

                              Das Backup stammt von einem Pi - zumindest sehe ich im Log den Pi-Adapter, der natürlich jetzt nicht mehr viel bringt.

                              Warte erst mal ab, bis der Restore durch ist. Ggf. musste Du auch noch das Restore.sh Script ausführen, damit Adapter neu für die geänderte Hardware kompiliert werden (steht auch schon ein oder zweimal im Forum).

                              Gruß,

                              Eric

                              Von unterwegs getippert `

                              Restore.sh oder meinst du die reinstall.sh?

                              Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

                              1 Antwort Letzte Antwort
                              0
                              • eric2905E Offline
                                eric2905E Offline
                                eric2905
                                schrieb am zuletzt editiert von
                                #20

                                Sorry, Du hast recht - reinstall.sh natürlich.

                                Gruß,

                                Eric

                                Von unterwegs getippert

                                Roses are red, violets are blue,

                                if I listen to metal, my neighbours do too

                                1 Antwort Letzte Antwort
                                0
                                • HomoranH Nicht stören
                                  HomoranH Nicht stören
                                  Homoran
                                  Global Moderator Administrators
                                  schrieb am zuletzt editiert von
                                  #21

                                  Die reinstall.sh brauchst du nur, wenn du einfach die Ordner rüberkopierst, damit anschließend die Adapterpakete neu kompiliert werden (wenn nötig)

                                  Bei einem restore werden die Adapter beim Anlegen der Instanzen sowieso neu installiert.

                                  Deswegen dauert das ja so lange.

                                  Ich nutze immer ein und das selbe Backup für alle Neuinstallationen.

                                  Gruß

                                  Rainer

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

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

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

                                  1 Antwort Letzte Antwort
                                  0
                                  • WebrangerW Offline
                                    WebrangerW Offline
                                    Webranger
                                    schrieb am zuletzt editiert von
                                    #22

                                    Läuft jetzt Problemlos mit Admin 2.9 auf meinem NUC

                                    Eins ist mir noch aufgefallen.

                                    Beim Backup einspielen war alles da ausser im VIS, da fehlte mir das klompett von mir eingetragen css.

                                    Die css hatte ich ja zum Glück noch auf meinem laufendem System.

                                    Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

                                    1 Antwort Letzte Antwort
                                    0
                                    • HomoranH Nicht stören
                                      HomoranH Nicht stören
                                      Homoran
                                      Global Moderator Administrators
                                      schrieb am zuletzt editiert von
                                      #23

                                      @ringdingringding:

                                      ausser im VIS, da fehlte mir das klompett von mir eingetragen css. `
                                      Was meinst du damit?

                                      Alle Views waren aber da? Sollten sie zumindest!

                                      Wo war was an CSS eingetragen? und was war da jetzt?

                                      Gruß

                                      Rainer

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

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

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

                                      1 Antwort Letzte Antwort
                                      0
                                      • WebrangerW Offline
                                        WebrangerW Offline
                                        Webranger
                                        schrieb am zuletzt editiert von
                                        #24

                                        Die views waren alle da.

                                        Rechts wo ich die angewählten widgets bearbeiten kann gib es einen “Reiter“ wo ich meine custom css eintragen kann.

                                        Diese css daten wurden nicht mit zurück gespielt.

                                        Intel NUC Celeron, Xiaomi Gateway, Fritzbox 7590, XS1

                                        1 Antwort Letzte Antwort
                                        0
                                        • B Offline
                                          B Offline
                                          Baerny
                                          schrieb am zuletzt editiert von
                                          #25

                                          @ringdingringding:

                                          Manchmal muß man einfach mal 30 minuten was anderes machen und selber weiter gucken.

                                          sudo installieren und curl und jetzt komm ich weiter.

                                          Hoffe ich mach alles richtig ;) `

                                          Auch ich scheitere daran, Sudo auf Debian zu installieren. Die 30 Minuten Zeit habe ich mir genommen und Tante Google befragt. Leider ohne Erfolg. ( steht sicherlich irgendwo in Google, hab aber das richtige nicht gefunden)

                                          Hat einer einen Link für mich wir ich das anstelle?

                                          Danke im voraus

                                          Baerny

                                          CCU 2 | Intel NUC mit Proxmox

                                          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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          480

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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