Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [How-to] Node.js ioBroker richtig updaten-2021/22 Edition

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    [How-to] Node.js ioBroker richtig updaten-2021/22 Edition

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

      @chrisdor

      Lösche den Adapter und installiere ihn neu !

      C 1 Reply Last reply Reply Quote 0
      • C
        Chrisdor @Glasfaser last edited by

        @glasfaser Habe ich auch schon drei mal versucht, funktioniert leider auch nicht?

        Glasfaser 2 Replies Last reply Reply Quote 0
        • Glasfaser
          Glasfaser @Chrisdor last edited by

          @chrisdor

          Danke für die Info , hast du nicht geschrieben !!

          C 1 Reply Last reply Reply Quote 0
          • C
            Chrisdor @Glasfaser last edited by

            @glasfaser sorry hatte ich vergessen

            1 Reply Last reply Reply Quote 0
            • Glasfaser
              Glasfaser @Chrisdor last edited by

              @chrisdor

              sudo -H -u iobroker npm cache clear --force

              Neustart ... was ist dann

              C 1 Reply Last reply Reply Quote 0
              • C
                Chrisdor @Glasfaser last edited by

                @glasfaser unverändert!

                2022-08-20 21:33:26.813 - info: host.e-server iobroker rebuild
2022-08-20 21:33:28.415 - info: host.e-server iobroker npm-rebuild: Rebuilding native modules ...
2022-08-20 21:34:55.322 - info: host.e-server iobroker npm-rebuild: rebuilt dependencies successfully
2022-08-20 21:34:55.369 - info: host.e-server iobroker npm-rebuild:
2022-08-20 21:34:55.371 - info: host.e-server iobroker npm-rebuild: Rebuilding native modules done
2022-08-20 21:34:56.385 - info: host.e-server iobroker npm-rebuild: exit 0
2022-08-20 21:34:56.750 - info: host.e-server instance system.adapter.klf200.0 started with pid 1450
2022-08-20 21:34:58.288 - error: host.e-server Caught by controller[0]: node:internal/modules/cjs/loader:959
2022-08-20 21:34:58.289 - error: host.e-server Caught by controller[0]: throw err;
2022-08-20 21:34:58.289 - error: host.e-server Caught by controller[0]: ^
2022-08-20 21:34:58.290 - error: host.e-server Caught by controller[0]: Error: Cannot find module 'node-schedule'
2022-08-20 21:34:58.290 - error: host.e-server Caught by controller[0]: Require stack:
2022-08-20 21:34:58.290 - error: host.e-server Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.klf200/build/main.js
2022-08-20 21:34:58.291 - error: host.e-server Caught by controller[0]: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
2022-08-20 21:34:58.291 - error: host.e-server Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:804:27)
2022-08-20 21:34:58.291 - error: host.e-server Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1028:19)
2022-08-20 21:34:58.292 - error: host.e-server Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
2022-08-20 21:34:58.292 - error: host.e-server Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.klf200/build/main.js:10:25)
2022-08-20 21:34:58.292 - error: host.e-server Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1126:14)
2022-08-20 21:34:58.293 - error: host.e-server Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
2022-08-20 21:34:58.293 - error: host.e-server Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1004:32)
2022-08-20 21:34:58.294 - error: host.e-server Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:839:12)
2022-08-20 21:34:58.294 - error: host.e-server Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
2022-08-20 21:34:58.294 - error: host.e-server Caught by controller[0]: code: 'MODULE_NOT_FOUND',
2022-08-20 21:34:58.295 - error: host.e-server Caught by controller[0]: requireStack: [ '/opt/iobroker/node_modules/iobroker.klf200/build/main.js' ]
2022-08-20 21:34:58.295 - error: host.e-server Caught by controller[0]: }
2022-08-20 21:34:58.295 - error: host.e-server instance system.adapter.klf200.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2022-08-20 21:34:58.296 - info: host.e-server Adapter system.adapter.klf200.0 needs rebuild and will be restarted afterwards.
2022-08-20 21:34:58.296 - info: host.e-server system.adapter.klf200.0 will be rebuilt
2022-08-20 21:34:58.297 - warn: host.e-server adapter "klf200" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt
2022-08-20 21:34:58.297 - info: host.e-server iobroker rebuild
2022-08-20 21:34:59.706 - info: host.e-server iobroker npm-rebuild: Rebuilding native modules ...
                Glasfaser 1 Reply Last reply Reply Quote 0
                • Glasfaser
                  Glasfaser @Chrisdor last edited by

                  @chrisdor

                  jetzt nochmal

                  cd /opt/iobroker/node_modules/iobroker.klf200/

npm install --omit=dev
                  C 1 Reply Last reply Reply Quote 0
                  • C
                    Chrisdor @Glasfaser last edited by

                    @glasfaser das selbe wie vorhin

                    Last login: Sat Aug 20 19:50:11 2022 from 192.168.178.57
e-server@e-server:~$ cd /opt/iobroker/node_modules/iobroker.klf200/
e-server@e-server:/opt/iobroker/node_modules/iobroker.klf200$ npm install --omit=dev
[sudo] password for e-server:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: iobroker.klf200@1.0.1
npm ERR! Found: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^5.0.0 || ^6.0.0" from @typescript-eslint/parser@2.34.0
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"^2.34.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^2.0.0" from @typescript-eslint/eslint-plugin@2.34.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^2.34.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-08-20T21_38_39_538Z-debug-0.log
e-server@e-server:/opt/iobroker/node_modules/iobroker.klf200$
                    Glasfaser 1 Reply Last reply Reply Quote 0
                    • Glasfaser
                      Glasfaser @Chrisdor last edited by

                      @chrisdor

                      iobroker del klf200

iobroker install klf200@1.0.1
                      C 1 Reply Last reply Reply Quote 0
                      • C
                        Chrisdor @Glasfaser last edited by

                        @glasfaser sehe jetzt unter Instanzen den Adapter nicht mehr!!

                        e-server@e-server:~$ iobroker del klf200
Delete adapter "klf200"
host.e-server Counted 1 meta of klf200
host.e-server Counted 1 adapter for klf200
host.e-server Counted 1 states (system.adapter.klf200.*) from states
host.e-server file klf200.admin deleted
host.e-server object klf200 deleted
host.e-server object klf200.admin deleted
host.e-server Deleting 2 object(s).
host.e-server Deleting 1 state(s).

removed 4 packages in 10s

90 packages are looking for funding
  run `npm fund` for details
e-server@e-server:~$ iobroker install klf200@1.0.1
NPM version: 8.15.0
Installing iobroker.klf200@1.0.1... (System call)

added 4 packages in 10s

90 packages are looking for funding
  run `npm fund` for details
host.e-server install adapter klf200@1.0.1
upload [4] klf200.admin /opt/iobroker/node_modules/iobroker.klf200/admin/admin.d.ts admin.d.ts video/mp2t
upload [3] klf200.admin /opt/iobroker/node_modules/iobroker.klf200/admin/index_m.html index_m.html text/html
upload [2] klf200.admin /opt/iobroker/node_modules/iobroker.klf200/admin/klf200.png klf200.png image/png
upload [1] klf200.admin /opt/iobroker/node_modules/iobroker.klf200/admin/style.css style.css text/css
upload [0] klf200.admin /opt/iobroker/node_modules/iobroker.klf200/admin/words.js words.js application/javascript
host.e-server object system.adapter.klf200 created/updated
e-server@e-server:~$
                        Glasfaser 1 Reply Last reply Reply Quote 0
                        • Glasfaser
                          Glasfaser @Chrisdor last edited by

                          @chrisdor sagte in [How-to] Node.js ioBroker richtig updaten-2021/22 Edition:

                          sehe jetzt unter Instanzen den Adapter nicht mehr!!

                          iobroker add klf200
                          C 1 Reply Last reply Reply Quote 0
                          • C
                            Chrisdor @Glasfaser last edited by

                            @glasfaser hat leider auch nicht geklappt

                            2022-08-20 21:53:06.714 - info: host.e-server instance system.adapter.klf200.0 started with pid 2473
2022-08-20 21:53:08.269 - error: host.e-server Caught by controller[0]: node:internal/modules/cjs/loader:959
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: throw err;
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: ^
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: Error: Cannot find module 'node-schedule'
2022-08-20 21:53:08.271 - error: host.e-server Caught by controller[0]: Require stack:
2022-08-20 21:53:08.271 - error: host.e-server Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.klf200/build/main.js
2022-08-20 21:53:08.271 - error: host.e-server Caught by controller[0]: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
2022-08-20 21:53:08.272 - error: host.e-server Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:804:27)
2022-08-20 21:53:08.272 - error: host.e-server Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1028:19)
2022-08-20 21:53:08.272 - error: host.e-server Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
2022-08-20 21:53:08.273 - error: host.e-server Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.klf200/build/main.js:10:25)
2022-08-20 21:53:08.273 - error: host.e-server Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1126:14)
2022-08-20 21:53:08.273 - error: host.e-server Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
2022-08-20 21:53:08.273 - error: host.e-server Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1004:32)
2022-08-20 21:53:08.274 - error: host.e-server Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:839:12)
2022-08-20 21:53:08.274 - error: host.e-server Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
2022-08-20 21:53:08.274 - error: host.e-server Caught by controller[0]: code: 'MODULE_NOT_FOUND',
2022-08-20 21:53:08.275 - error: host.e-server Caught by controller[0]: requireStack: [ '/opt/iobroker/node_modules/iobroker.klf200/build/main.js' ]
2022-08-20 21:53:08.275 - error: host.e-server Caught by controller[0]: }
2022-08-20 21:53:08.275 - error: host.e-server instance system.adapter.klf200.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2022-08-20 21:53:08.276 - info: host.e-server Adapter system.adapter.klf200.0 needs rebuild and will be restarted afterwards.
2022-08-20 21:53:08.276 - info: host.e-server system.adapter.klf200.0 will be rebuilt
2022-08-20 21:53:08.278 - warn: host.e-server adapter "klf200" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt
2022-08-20 21:53:08.278 - info: host.e-server iobroker rebuild
2022-08-20 21:53:09.677 - info: host.e-server iobroker npm-rebuild: Rebuilding native modules ...
                            SBorg 1 Reply Last reply Reply Quote 0
                            • Glasfaser
                              Glasfaser last edited by

                              @chrisdor

                              Sorry keine Idee mehr .. warum dieser Adapter zickt .

                              C 1 Reply Last reply Reply Quote 0
                              • C
                                Chrisdor @Glasfaser last edited by

                                @glasfaser ok, aber danke für deine Bemühungen!

                                1 Reply Last reply Reply Quote 0
                                • SBorg
                                  SBorg Forum Testing Most Active @Chrisdor last edited by

                                  @chrisdor sagte in [How-to] Node.js ioBroker richtig updaten-2021/22 Edition:

                                  @glasfaser hat leider auch nicht geklappt

                                  2022-08-20 21:53:08.269 - error: host.e-server Caught by controller[0]: node:internal/modules/cjs/loader:959
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: throw err;
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: ^
2022-08-20 21:53:08.270 - error: host.e-server Caught by controller[0]: Error: Cannot find module 'node-schedule'
2022-08-20 21:53:08.271 - error: host.e-server Caught by controller[0]: Require stack:
2022-08-20 21:53:08.271 - error: host.e-server Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.klf200/build/main.js

                                  Was liefert denn ein npm list|grep node ?
                                  Taucht da node-schedule auf? Sonst versuche mal ein npm install node-schedule

                                  Bild 004.png

                                  C 1 Reply Last reply Reply Quote 0
                                  • C
                                    Chrisdor @SBorg last edited by

                                    @sborg das wars jetzt funktioniert es! Danke, Danke!!!

                                    e-server@e-server:/opt/iobroker$ npm list|grep node
[sudo] password for e-server:
├── node-inspect@2.0.0 extraneous
e-server@e-server:/opt/iobroker$ npm install node-schedule

added 1 package, removed 645 packages, and changed 1 package in 17s

90 packages are looking for funding
  run `npm fund` for details
e-server@e-server:/opt/iobroker$ npm list|grep node
└── node-schedule@2.1.0
e-server@e-server:/opt/iobroker$

                                    Hab jetzt noch einen Master und einen zweiten Slave, da kommt node-schedule auch nicht vor. Aber alle installierten Adapter laufen problemlos bzw. Iobroker selbst auch! Sollt ich das auch nach installieren?

                                    Last login: Sat Aug 20 18:48:31 2022 from 192.168.178.57
c-server@c-server:~$ cd /opt/iobroker
c-server@c-server:/opt/iobroker$ npm list|grep node
[sudo] password for c-server:
c-server@c-server:/opt/iobroker$ npm list|grep node
c-server@c-server:/opt/iobroker$


                                    Last login: Sun Aug 21 13:44:13 2022 from 192.168.178.57
d-server@d-server:~$ cd /opt/iobroker
d-server@d-server:/opt/iobroker$ npm list|grep node
[sudo] password for d-server:
├── node-inspect@2.0.0 extraneous
d-server@d-server:/opt/iobroker$
                                    SBorg 1 Reply Last reply Reply Quote 0
                                    • SBorg
                                      SBorg Forum Testing Most Active @Chrisdor last edited by

                                      @chrisdor sagte in [How-to] Node.js ioBroker richtig updaten-2021/22 Edition:

                                      Hab jetzt noch einen Master und einen zweiten Slave, da kommt node-schedule auch nicht vor. Aber alle installierten Adapter laufen problemlos bzw. Iobroker selbst auch! Sollt ich das auch nach installieren?

                                      Nein, das wäre nur Ressourcenverschwendung. Falls mal ein Adapter auf einem System den braucht, meldet er sich schon (siehe "error" in deinen Logs von oben). Normalerweise werden die Dependencies aber auch vom Adapter aufgelöst und nachinstalliert.
                                      Fährst ja auch nicht das ganze Jahr mit angehängtem Wohnwagen rum, nur weil du ihn vielleicht mal 2 Wochen im Jahr brauchst 😉

                                      C 1 Reply Last reply Reply Quote 0
                                      • C
                                        Chrisdor @SBorg last edited by

                                        @sborg sagte in [How-to] Node.js ioBroker richtig updaten-2021/22 Edition:

                                        Ok, verstehe!! Danke nochmal.

                                        Fährst ja auch nicht das ganze Jahr mit angehängtem Wohnwagen rum, nur weil du ihn vielleicht mal 2 Wochen im Jahr brauchst 😉

                                        Da hast du natürlich recht!! :😁

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          Frank06347 last edited by

                                          Hallo,
                                          ich habe auf die empfohlene Version Node.js 16.x ein Update gemacht.
                                          Jetzt wird folgendes in der Übersicht angezeigt:
                                          84e91a14-67eb-4062-af22-a5e5130d9b33-grafik.png
                                          Ist das so richtig?
                                          Welche NPM Version wird empfohlen?
                                          Muss ich mich um die NPM-Version kümmern? ... oder kommt die automatisch durch Node.js?
                                          Wo finde ich die verfügbaren Updates (siehe Screeshot)?

                                          Viele Grüße
                                          Frank

                                          Diginix Homoran 2 Replies Last reply Reply Quote 0
                                          • Diginix
                                            Diginix @Frank06347 last edited by

                                            @frank06347 Das passt so. NPM nicht manuell updaten, kommt passend mit und zur nodejs Ver.

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

                                            Support us

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

                                            823
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            97
                                            812
                                            319967
                                            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