Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Ständige Fehler bei Aktualisierung von Adaptern

    NEWS

    • Informationen zum Spamschutz im Forum

    • Beta-Start ioBroker-Matter Adapter

    • JAHRESRÜCKBLICK 2024 ✨

    Ständige Fehler bei Aktualisierung von Adaptern

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

      Führst du die Installation als echter root aus oder per sudo? Da scheint was mit den Berechtigungen nicht zu stimmen.

      Du kannst mal probieren, die Ordner wieder in die richtigen Besitzverhältnisse zu bringen:

      chown -R root /root

      chown -R $(whoami) /opt/iobroker

      letzeren Befehl per sudo, wenn du iobroker auch als normaler User mit sudo installierst.

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

        @AlCalzone:

        Führst du die Installation als echter root aus oder per sudo? Da scheint was mit den Berechtigungen nicht zu stimmen.

        Du kannst mal probieren, die Ordner wieder in die richtigen Besitzverhältnisse zu bringen:

        chown -R root /root

        chown -R $(whoami) /opt/iobroker

        letzeren Befehl per sudo, wenn du iobroker auch als normaler User mit sudo installierst. `

        danke für deine mühen, hab es gerade hin bekommen. iobroker läuft wieder.

        bin nach dieser Anleitung erstmal vorgegangen und iobroker läuft erstmal wieder. versuche jetzt mal updates durchzuführen der adapter.

        danke

        ich hab ja nun auf den neuen admin geupdatet 2.0.

        mein problem besteht jetzt darin das sich kein adapter starten lässt??? 😮

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

          @fischi87:

          mein problem besteht jetzt darin das sich kein adapter starten lässt??? 😮 `
          Was sagen die Logs?

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

            @AlCalzone:

            @fischi87:

            mein problem besteht jetzt darin das sich kein adapter starten lässt??? 😮 Was sagen die Logs?

            hier das log:

            host.RaspberryPi	2018-03-10 11:41:40.550	error	instance system.adapter.telegram.0 terminated with code 0 (OK)
host.RaspberryPi	2018-03-10 11:41:40.550	error	Caught by controller[3]: at require (internal/module.js:20:19)
host.RaspberryPi	2018-03-10 11:41:40.550	error	Caught by controller[3]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.550	error	Caught by controller[3]: at Function.Module._load (module.js:445:3)
host.RaspberryPi	2018-03-10 11:41:40.550	error	Caught by controller[3]: at tryModuleLoad (module.js:453:12)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Module.load (module.js:494:32)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Object.Module._extensions..js (module.js:586:10)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Module._compile (module.js:577:32)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Object. (/opt/iobroker/node_modules/node-telegram-bot-api/src/telegram.js:10:17)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at require (internal/module.js:20:19)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.549	error	Caught by controller[3]: at Function.Module._load (module.js:445:3)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at tryModuleLoad (module.js:453:12)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at Module.load (module.js:494:32)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at Object.Module._extensions..js (module.js:586:10)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at Module._compile (module.js:577:32)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at Object. (/opt/iobroker/node_modules/request-promise/lib/rp.js:10:19)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at module.exports (/opt/iobroker/node_modules/stealthy-require/lib/index.js:62:23)
host.RaspberryPi	2018-03-10 11:41:40.548	error	Caught by controller[3]: at /opt/iobroker/node_modules/request-promise/lib/rp.js:11:16
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[3]: at require (internal/module.js:20:19)
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[3]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[3]: at Function.Module._load (module.js:424:25)
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[3]: at Function.Module._resolveFilename (module.js:476:15)
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[3]: 2018-03-10 11:41:39.971 - telegram.0 Error: Cannot find module 'request'
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[2]: 2018-03-10 11:41:39.967 - telegram.0 uncaught exception: Cannot find module 'request'
host.RaspberryPi	2018-03-10 11:41:40.547	error	Caught by controller[1]: at require (internal/module.js:20:19) code: 'MODULE_NOT_FOUND' }
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at Function.Module._load (module.js:445:3)
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at tryModuleLoad (module.js:453:12)
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at Module.load (module.js:494:32)
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at Object.Module._extensions..js (module.js:586:10)
host.RaspberryPi	2018-03-10 11:41:40.546	error	Caught by controller[1]: at Module._compile (module.js:577:32)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at Object. (/opt/iobroker/node_modules/node-telegram-bot-api/src/telegram.js:10:17)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at require (internal/module.js:20:19)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at Function.Module._load (module.js:445:3)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at tryModuleLoad (module.js:453:12)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at Module.load (module.js:494:32)
host.RaspberryPi	2018-03-10 11:41:40.545	error	Caught by controller[1]: at Object.Module._extensions..js (module.js:586:10)
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at Module._compile (module.js:577:32)
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at Object. (/opt/iobroker/node_modules/request-promise/lib/rp.js:10:19)
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at module.exports (/opt/iobroker/node_modules/stealthy-require/lib/index.js:62:23)
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at /opt/iobroker/node_modules/request-promise/lib/rp.js:11:16
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at require (internal/module.js:20:19)
host.RaspberryPi	2018-03-10 11:41:40.544	error	Caught by controller[1]: at Module.require (module.js:504:17)
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[1]: at Function.Module._load (module.js:424:25)
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[1]: at Function.Module._resolveFilename (module.js:476:15)
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[1]: { Error: Cannot find module 'request'
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[0]: ###
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[0]: ### npm install request --save
host.RaspberryPi	2018-03-10 11:41:40.543	error	Caught by controller[0]: ###
host.RaspberryPi	2018-03-10 11:41:40.542	error	Caught by controller[0]: ### But required by "request-promise".
host.RaspberryPi	2018-03-10 11:41:40.542	error	Caught by controller[0]: ### The "request" library is not installed automatically anymore.
host.RaspberryPi	2018-03-10 11:41:40.541	error	Caught by controller[0]: ###

            habe jetzt mal die request library installiert aber da bekomme ich auch Fehler:

            gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 4.1.19-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
gyp ERR! node -v v6.13.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
iobroker.core@1.0.0 /opt/iobroker
└─┬ request@2.83.0 
  └─┬ form-data@2.3.2 
    └── combined-stream@1.0.6 

npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/body-parser/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/cliui/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/engine.io/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/engine.io-client/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/express/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/express-session/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/finalhandler/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/form-data/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/http-errors/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.admin/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/le-acme-core/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io-client/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/wrap-ansi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/yargs/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/cliui/node_modules/wrap-ansi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io/node_modules/engine.io/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io/node_modules/socket.io-parser/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io-client/node_modules/engine.io-client/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/socket.io-client/node_modules/socket.io-parser/package.json'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules/unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
            1 Reply Last reply Reply Quote 0
            • wendy2702
              wendy2702 last edited by

              Wenn du Node/NPM updates gemacht hast kann ein````
              reinstall.sh

              
Bei mir hat er allerdings gestern nach NPM Update und iobroker restart alle Adapter von alleine neu mit dem aktualisierten NPM installiert.
              1 Reply Last reply Reply Quote 0
              • fischi87
                fischi87 last edited by

                reinstall lässt sich aber nicht starten?

                hab jetzt alles von hand nach installiert. kommen zwar immer noch Fehler bei die adapter starten jetzt wenigstens schon mal.

                mich nerven die Fehler trotzdem wenn ich eine Instanz installieren möchte kommen immer noch die Fehler :evil:

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

                  Mir hat dieser Tipp von Mr.Lee geholfen

                  ` > npm i -g npm

                  (allerdings 2 mal…) `

                  Hatte danach NPM 5.7.1 drauf und alle Adapter haben sich nach iobroker restart von alleine mit NPM 5.7.1 neu installiert…. ohne Fehlermeldung.

                  Hatte wohl JS 1.2.7

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

                    @fischi87:

                    reinstall lässt sich aber nicht starten?

                    hab jetzt alles von hand nach installiert. kommen zwar immer noch Fehler bei die adapter starten jetzt wenigstens schon mal.

                    mich nerven die Fehler trotzdem wenn ich eine Instanz installieren möchte kommen immer noch die Fehler :evil: `

                    Was heißt nicht starten?

                    Rechte ändern mit

                    chmod -x reinstall.sh

                    Starten mit

                    ./reinstall.sh
````eventuell mit````
sudo
````davor
                    1 Reply Last reply Reply Quote 0
                    • fischi87
                      fischi87 last edited by

                      @wendy2702:

                      @fischi87:

                      reinstall lässt sich aber nicht starten?

                      hab jetzt alles von hand nach installiert. kommen zwar immer noch Fehler bei die adapter starten jetzt wenigstens schon mal.

                      mich nerven die Fehler trotzdem wenn ich eine Instanz installieren möchte kommen immer noch die Fehler :evil: `

                      Was heißt nicht starten?

                      Rechte ändern mit

                      chmod -x reinstall.sh

                      Starten mit

                      ./reinstall.sh
````eventuell mit````
sudo
````davor `

                      rechte sind bereits für jeden und auch ausführbar.

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

                        Meine Frage nach

                        > Was heißt nicht starten hast du leider nicht beantwortet.

                        Hast du ein log davon?

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

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        906
                        Online

                        31.1k
                        Users

                        78.4k
                        Topics

                        1.2m
                        Posts

                        3
                        13
                        1147
                        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