Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. IoBroker Backup einspielen

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    UNSOLVED IoBroker Backup einspielen

    This topic has been deleted. Only users with topic management privileges can see it.
    • wendy2702
      wendy2702 last edited by

      hast du nach dem "systemctl start iobroker" als Bestätigung das password des "root" users eingegeben, liest sich nicht so.

      1 Reply Last reply Reply Quote 1
      • M
        maxpd last edited by

        passwort habe ich noch nicht geändert. also pi | raspberry. Letzteres hab ich als Kennwort verwendet

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

          was passiert wenn du

          sudo systemctl start iobroker
          

          oder nur

          iobroker start
          

          machst?

          M 1 Reply Last reply Reply Quote 1
          • M
            maxpd @wendy2702 last edited by

            @wendy2702 said in IoBroker Backup einspielen:

            iobroker start

            pi@iobroker:/opt/iobroker $ sudo systemctl start iobroker
            pi@iobroker:/opt/iobroker $ iobroker start
            pi@iobroker:/opt/iobroker $
            
            
            1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @maxpd last edited by Homoran

              @maxpd sagte in IoBroker Backup einspielen:

              Authentication is required to start 'iobroker.service'.

              Authenticating as: root

              Password:

              hier fragt er ganz deutlich nach dem root-Passwort!

              1 Reply Last reply Reply Quote 0
              • M
                maxpd last edited by

                das ist normal leer und da ich nichts geändert habe, hab ichs nun auch mit einem leeren probiert. ohne erfolg.

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

                  @maxpd und du kannst in der Zeile in der "root" steht nicht "pi" stattdessen eingeben?

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    maxpd @Homoran last edited by

                    @Homoran Leider nein. Ich habe nun auch pi als PAsswort probiert. geht auch nicht.

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

                      @maxpd du könntest natürlich ein Passwort für root vergeben mit sudo passwd root

                      M 1 Reply Last reply Reply Quote 1
                      • M
                        maxpd @Homoran last edited by maxpd

                        @Homoran danke dir. dann klappts auch mit der authentifizierung. Aber der output vom logfile ist immer noch der gleiche:

                        pi@iobroker:/opt/iobroker $ systemctl start iobroker
                        ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
                        Authentication is required to start 'iobroker.service'.
                        Authenticating as: root
                        Password:
                        ==== AUTHENTICATION COMPLETE ===
                        pi@iobroker:/opt/iobroker $ sudo tail -f /opt/iobroker/log/iobroker.2020-04-06.log
                        2020-04-06 15:38:15.484  - info: iobroker
                        2020-04-06 15:38:15.484  - info: iobroker ERR!
                        2020-04-06 15:38:15.485  - info: iobroker  A complete log of this run can be found in:
                        2020-04-06 15:38:15.485  - info: iobroker npm
                        2020-04-06 15:38:15.485  - info: iobroker
                        2020-04-06 15:38:15.486  - info: iobroker ERR!
                        2020-04-06 15:38:15.486  - info: iobroker      /home/iobroker/.npm/_logs/2020-04-06T13_38_15_453Z-debug.log
                        2020-04-06 15:38:15.502  - error: iobroker host.iobroker Adapter directory "null" does not exists
                        2020-04-06 15:38:15.525  - error: iobroker Cannot parse null/io-package.json:Error: ENOENT: no such file or directory, open 'null/io-package.json'
                        2020-04-06 15:38:15.533  - info: iobroker exit 0
                        
                        
                        

                        PS:

                        pi@iobroker:/opt/iobroker $ iobroker list instances
                          system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                        
                        
                        Homoran 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @maxpd last edited by

                          @maxpd sagte in IoBroker Backup einspielen:

                          sudo tail -f /opt/iobroker/log/iobroker.2020-04-06.log

                          Bin nicht an meinem System:
                          kommt da wirklich ein Punkt hinter iobroker?

                          @maxpd sagte in IoBroker Backup einspielen:

                          system.adapter.admin.0 : admin - enabled, port: 8081, bind: 0.0.0.0, run as: admin

                          der läuft doch gar nicht, oder ist da noch ein + davor, das du uns unterschlägst?
                          iobroker start admin

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            maxpd @Homoran last edited by maxpd

                            @Homoran Gemäß Google scheint ein Punkt korrekt.
                            auch wenn ich den admin starte, startet der admin nicht. Kein + davor. Unterschlagen habe ich nichts.

                            M 1 Reply Last reply Reply Quote 0
                            • wendy2702
                              wendy2702 last edited by

                              Wenn du den Admin startest, mache vorher den Befehl um in das log zu schauen in einer zweiten Session und auch noch für das SYSLOG:

                              tail -f /var/log/syslog
                              

                              Was kommt dann?

                              1 Reply Last reply Reply Quote 1
                              • M
                                maxpd @maxpd last edited by

                                @maxpd

                                pi@iobroker:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs
                                2020-04-06 20:34:13.889  - info: host.iobroker iobroker.js-controller version 1.5.11 js-controller starting
                                2020-04-06 20:34:13.893  - info: host.iobroker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                                2020-04-06 20:34:13.894  - info: host.iobroker hostname: iobroker, node: v10.19.0
                                2020-04-06 20:34:13.896  - info: host.iobroker ip addresses: 192.168.178.30
                                2020-04-06 20:34:13.964  - info: host.iobroker  inMem-states listening on port 9000
                                2020-04-06 20:34:14.369  - info: host.iobroker  inMem-objects listening on port 9001
                                2020-04-06 20:34:14.387  - error: Another instance is running or some application uses port!
                                2020-04-06 20:34:14.387  - error: uncaught exception: listen EADDRINUSE: address already in use 127.0.0.1:9000
                                2020-04-06 20:34:14.391  - info: host.iobroker terminated
                                2020-04-06 20:34:14.395  - info: iobroker _restart
                                listen EADDRINUSE: address already in use 127.0.0.1:9001
                                Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
                                    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
                                    at listenInCluster (net.js:1328:12)
                                    at doListen (net.js:1461:7)
                                    at process._tickCallback (internal/process/next_tick.js:63:19)
                                    at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
                                    at startup (internal/bootstrap/node.js:283:19)
                                    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
                                
                                

                                Läuft hier was parallel und warum 2 Ports gleich belegt?

                                Eine neue Instanz des Admin Adapters unter einem anderen Port startet auch nicht.
                                Dabei ist mir eingefallen, ich habe parallel den alten Raspi mit iobroker noch laufen.
                                Den habe ich mal gestoppt. Dennoch geht der Admin nicht an.
                                Hier aber was ganz interessantes!!

                                pi@iobroker:/opt/iobroker $ node node_modules/iobroker.admin/admin.js --logs
                                internal/modules/cjs/loader.js:638
                                    throw err;
                                    ^
                                
                                Error: Cannot find module '/opt/iobroker/node_modules/iobroker.admin/admin.js'
                                    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
                                    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
                                    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
                                    at startup (internal/bootstrap/node.js:283:19)
                                    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
                                
                                

                                Warum geht die admin.js flöten, wenn ich ein Backup einspiele?

                                @wendy2702

                                vor admin start

                                pi@iobroker:/opt/iobroker $ tail -f /var/log/syslog
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Monobit: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Poker: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Runs: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Long run: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: HRNG source speed: (min=481.362; avg=506.536; max=511.798)Kibits/s
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS tests speed: (min=17.324; avg=28.821; max=31.371)Mibits/s
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Lowest ready-buffers level: 2
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Entropy starvations: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
                                

                                Nach Admin start

                                pi@iobroker:/opt/iobroker $ tail -f /var/log/syslog
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Runs: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Long run: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: HRNG source speed: (min=481.362; avg=506.536; max=511.798)Kibits/s
                                Apr  6 20:27:41 iobroker rngd[382]: stats: FIPS tests speed: (min=17.324; avg=28.821; max=31.371)Mibits/s
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Lowest ready-buffers level: 2
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Entropy starvations: 0
                                Apr  6 20:27:41 iobroker rngd[382]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
                                Apr  6 20:41:47 iobroker systemd[1]: Started Session c3 of user pi.
                                Apr  6 20:43:19 iobroker systemd[1]: Started Session c4 of user pi.
                                
                                
                                

                                Der Log lässt putty irgendwie abstürzen. Die Pfeiltasten schreiben nur noch komische Zeichen und einen Pfad sehe ich auch nicht mehr.

                                
                                pi@iobroker:/opt/iobroker $ sudo tail -f /opt/iobroker/log/iobroker.2020-04-06.log
                                2020-04-06 15:38:15.484  - info: iobroker ERR!
                                2020-04-06 15:38:15.485  - info: iobroker  A complete log of this run can be found in:
                                2020-04-06 15:38:15.485  - info: iobroker npm
                                2020-04-06 15:38:15.485  - info: iobroker
                                2020-04-06 15:38:15.486  - info: iobroker ERR!
                                2020-04-06 15:38:15.486  - info: iobroker      /home/iobroker/.npm/_logs/2020-04-06T13_38_15_453Z-debug.log
                                2020-04-06 15:38:15.502  - error: iobroker host.iobroker Adapter directory "null" does not exists
                                2020-04-06 15:38:15.525  - error: iobroker Cannot parse null/io-package.json:Error: ENOENT: no such file or directory, open 'null/io-package.json'
                                2020-04-06 15:38:15.533  - info: iobroker exit 0
                                2020-04-06 16:37:54.510  - info: host.iobroker Delete log file iobroker.2019-07-23.log
                                ^[[A
                                
                                
                                ^[[A^[[D^[[C^[[B^[[D^[[C^[[A^[[D^[[B^[[D^[[A^[[B
                                
                                

                                Ich habe noch eine andere Möglichkeit gefunden an das log zu kommen. Das ist dann allerdings länger als putty zulässt. Der allerletzte Eintrag ist aber auch sehr interessant:

                                cat log/iobroker.JJJJ-MM-TT.log
                                
                                2020-04-06 20:47:09.992  - error: host.iobroker startInstance system.adapter.admin.0Invalid version of "js-controller". Installed "1.5.11", required ">=2.0.0
                                
                                

                                Wenn ich dann ein Upgrade Versuche, meckert er mit einem Socket und die js.controller Version scheint er doch nicht upgedatet zu haben:

                                pi@iobroker:/opt/iobroker $ iobroker upgrade self
                                Update js-controller from @1.5.11 to @2.2.9
                                NPM version: 6.13.4
                                npm install iobroker.js-controller@2.2.9 --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
                                In file included from ../src/unix_dgram.cc:5:
                                ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
                                ../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                                     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                              ^
                                In file included from ../../nan/nan.h:54,
                                                 from ../src/unix_dgram.cc:5:
                                ../src/unix_dgram.cc: At global scope:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                       (node::addon_register_func) (regfunc),                          \
                                                                           ^
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
                                   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                   ^~~~~~~~~~~~~
                                ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                                 NODE_MODULE(unix_dgram, Initialize)
                                 ^~~~~~~~~~~
                                In file included from /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:63,
                                                 from ../../nan/nan.h:54,
                                                 from ../src/unix_dgram.cc:5:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78:   required from here
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                                reinterpret_cast<Callback>(callback), type);
                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
                                ../../nan/nan_object_wrap.h:65:61:   required from here
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                In file included from ../src/main.cpp:3:
                                ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
                                ../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                                     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                              ^
                                In file included from ../../nan/nan.h:54,
                                                 from ../src/main.cpp:3:
                                ../src/main.cpp: At global scope:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                       (node::addon_register_func) (regfunc),                          \
                                                                           ^
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
                                   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                   ^~~~~~~~~~~~~
                                ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’
                                 NODE_MODULE(diskusage, Init)
                                 ^~~~~~~~~~~
                                In file included from /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:63,
                                                 from ../../nan/nan.h:54,
                                                 from ../src/main.cpp:3:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78:   required from here
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                                reinterpret_cast<Callback>(callback), type);
                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
                                ../../nan/nan_object_wrap.h:65:61:   required from here
                                /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.3 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                
                                Host "iobroker" (linux) updated
                                Execute: chmod -R 777 /opt/iobroker
                                chmod: changing permissions of '/opt/iobroker/backups': Operation not permitted
                                chmod: changing permissions of '/opt/iobroker/backups/2020_04_05-14_51_50_backupiobroker.tar.gz': Operation not permitted
                                chmod: changing permissions of '/opt/iobroker/log/restart.log': Operation not permitted
                                Chmod finished. Restart controller
                                Starting node restart.js
                                pi@iobroker:/opt/iobroker $ iobroker start
                                pi@iobroker:/opt/iobroker $ iobroker list instances
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                Socket.io Server detected. Please update to js-controller 2.0 or higher!
                                  system.adapter.admin.0                 : admin                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                  system.adapter.admin.1                 : admin                 -  enabled, port: 8089, bind: 0.0.0.0, run as: admin
                                  system.adapter.chromecast.0            : chromecast            - disabled
                                  system.adapter.cloud.0                 : cloud                 - disabled
                                  system.adapter.denon.0                 : denon                 - disabled
                                  system.adapter.discovery.0             : discovery             - disabled
                                  system.adapter.google-sharedlocations.0: google-sharedlocations - disabled
                                  system.adapter.history.0               : history               - disabled
                                  system.adapter.hm-rega.0               : hm-rega               - disabled
                                  system.adapter.hm-rpc.0                : hm-rpc                - disabled, port: 0
                                  system.adapter.info.0                  : info                  - disabled
                                  system.adapter.iot.0                   : iot                   - disabled
                                  system.adapter.javascript.0            : javascript            - disabled
                                  system.adapter.lgtv.0                  : lgtv                  - disabled
                                  system.adapter.mihome-vacuum.0         : mihome-vacuum         - disabled, port: 54321
                                  system.adapter.ping.0                  : ping                  - disabled
                                  system.adapter.sayit.0                 : sayit                 - disabled, port: 0
                                  system.adapter.shelly.0                : shelly                - disabled, port: 1882, bind: 0.0.0.0
                                  system.adapter.sonoff.0                : sonoff                - disabled, port: 1883, bind: 0.0.0.0
                                  system.adapter.telegram.0              : telegram              - disabled, port: 8443, bind: 0.0.0.0
                                  system.adapter.telegram.1              : telegram              - disabled, port: 8443, bind: 0.0.0.0
                                  system.adapter.telegram.2              : telegram              - disabled, port: 8443, bind: 0.0.0.0
                                  system.adapter.terminal.0              : terminal              - disabled, port: 8088, bind: 0.0.0.0, run as: admin
                                  system.adapter.text2command.0          : text2command          - disabled
                                  system.adapter.tr-064.0                : tr-064                - disabled
                                  system.adapter.web.0                   : web                   - disabled, port: 8082, bind: 0.0.0.0, run as: admin
                                  system.adapter.wifilight.0             : wifilight             - disabled
                                  system.adapter.yeelight-2.0            : yeelight-2            - disabled
                                  system.adapter.zigbee.0                : zigbee                - disabled
                                
                                + instance is alive
                                pi@iobroker:/opt/iobroker $
                                
                                
                                1 Reply Last reply Reply Quote 0
                                • wendy2702
                                  wendy2702 last edited by wendy2702

                                  Was genau hast du jetzt gemacht?

                                  Wenn du iobroker neu installiert hast und dann ein restore sollte ein Upgrade nicht mehr nötig sein.

                                  Nach welcher Anleitung hast du iobroker installiert?

                                  Hier hatten wir auch das Problem mit dem JS Controller und es konnte durch neu Installation und restore gelöst werden

                                  https://forum.iobroker.net/topic/30539/update-js-controller-1-5-14-auf-2-2-9-schlägt-fehl/16

                                  M 1 Reply Last reply Reply Quote 1
                                  • M
                                    maxpd @wendy2702 last edited by

                                    @wendy2702 Ich habe nach iobroker upgrade self den Stecker gezogen. Am nächsten Tag lief der Admin ^^

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

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate
                                    FAQ Cloud / IOT
                                    HowTo: Node.js-Update
                                    HowTo: Backup/Restore
                                    Downloads
                                    BLOG

                                    587
                                    Online

                                    31.7k
                                    Users

                                    79.7k
                                    Topics

                                    1.3m
                                    Posts

                                    backup iobroker
                                    11
                                    93
                                    19465
                                    Loading More Posts
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                    The ioBroker Community 2014-2023
                                    logo