Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. [How-to] Node.js ioBroker richtig updaten-2021/22 Edition

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    496

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

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

Scheduled Pinned Locked Moved ioBroker Allgemein
812 Posts 97 Posters 388.5k Views 83 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • GlasfaserG Glasfaser

    @chrisdor

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

    C Offline
    C Offline
    Chrisdor
    wrote on last edited by
    #713

    @glasfaser sorry hatte ich vergessen

    1 Reply Last reply
    0
    • C Chrisdor

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

      GlasfaserG Offline
      GlasfaserG Offline
      Glasfaser
      wrote on last edited by
      #714

      @chrisdor

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

      Neustart ... was ist dann

      Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

      C 1 Reply Last reply
      0
      • GlasfaserG Glasfaser

        @chrisdor

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

        Neustart ... was ist dann

        C Offline
        C Offline
        Chrisdor
        wrote on last edited by
        #715

        @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 ...
        
        
        GlasfaserG 1 Reply Last reply
        0
        • C Chrisdor

          @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 ...
          
          
          GlasfaserG Offline
          GlasfaserG Offline
          Glasfaser
          wrote on last edited by
          #716

          @chrisdor

          jetzt nochmal

          cd /opt/iobroker/node_modules/iobroker.klf200/
          
          npm install --omit=dev
          

          Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

          C 1 Reply Last reply
          0
          • GlasfaserG Glasfaser

            @chrisdor

            jetzt nochmal

            cd /opt/iobroker/node_modules/iobroker.klf200/
            
            npm install --omit=dev
            
            C Offline
            C Offline
            Chrisdor
            wrote on last edited by
            #717

            @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$
            
            
            GlasfaserG 1 Reply Last reply
            0
            • C Chrisdor

              @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$
              
              
              GlasfaserG Offline
              GlasfaserG Offline
              Glasfaser
              wrote on last edited by
              #718

              @chrisdor

              iobroker del klf200
              
              iobroker install klf200@1.0.1
              

              Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

              C 1 Reply Last reply
              0
              • GlasfaserG Glasfaser

                @chrisdor

                iobroker del klf200
                
                iobroker install klf200@1.0.1
                
                C Offline
                C Offline
                Chrisdor
                wrote on last edited by
                #719

                @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:~$
                
                
                GlasfaserG 1 Reply Last reply
                0
                • C Chrisdor

                  @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:~$
                  
                  
                  GlasfaserG Offline
                  GlasfaserG Offline
                  Glasfaser
                  wrote on last edited by
                  #720

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

                  sehe jetzt unter Instanzen den Adapter nicht mehr!!

                  iobroker add klf200
                  

                  Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                  C 1 Reply Last reply
                  0
                  • GlasfaserG Glasfaser

                    @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 Offline
                    C Offline
                    Chrisdor
                    wrote on last edited by
                    #721

                    @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 ...
                    
                    
                    SBorgS 1 Reply Last reply
                    0
                    • GlasfaserG Offline
                      GlasfaserG Offline
                      Glasfaser
                      wrote on last edited by
                      #722

                      @chrisdor

                      Sorry keine Idee mehr .. warum dieser Adapter zickt .

                      Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                      C 1 Reply Last reply
                      0
                      • GlasfaserG Glasfaser

                        @chrisdor

                        Sorry keine Idee mehr .. warum dieser Adapter zickt .

                        C Offline
                        C Offline
                        Chrisdor
                        wrote on last edited by
                        #723

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

                        1 Reply Last reply
                        0
                        • C Chrisdor

                          @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 ...
                          
                          
                          SBorgS Offline
                          SBorgS Offline
                          SBorg
                          Forum Testing Most Active
                          wrote on last edited by
                          #724

                          @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

                          LG SBorg ( SBorg auf GitHub)
                          Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation

                          C 1 Reply Last reply
                          0
                          • SBorgS SBorg

                            @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 Offline
                            C Offline
                            Chrisdor
                            wrote on last edited by
                            #725

                            @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$
                            
                            
                            SBorgS 1 Reply Last reply
                            0
                            • C Chrisdor

                              @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$
                              
                              
                              SBorgS Offline
                              SBorgS Offline
                              SBorg
                              Forum Testing Most Active
                              wrote on last edited by
                              #726

                              @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 ;)

                              LG SBorg ( SBorg auf GitHub)
                              Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation

                              C 1 Reply Last reply
                              0
                              • SBorgS SBorg

                                @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 Offline
                                C Offline
                                Chrisdor
                                wrote on last edited by
                                #727

                                @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!! ::grin:

                                1 Reply Last reply
                                0
                                • F Offline
                                  F Offline
                                  Frank06347
                                  wrote on last edited by
                                  #728

                                  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

                                  DiginixD HomoranH 2 Replies Last reply
                                  0
                                  • F Frank06347

                                    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

                                    DiginixD Offline
                                    DiginixD Offline
                                    Diginix
                                    wrote on last edited by
                                    #729

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

                                    ..:: So long! Tom ::..

                                    NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                                    1 Reply Last reply
                                    1
                                    • F Frank06347

                                      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

                                      HomoranH Offline
                                      HomoranH Offline
                                      Homoran
                                      Global Moderator Administrators
                                      wrote on last edited by
                                      #730

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

                                      Ist das so richtig?

                                      ja!
                                      https://forum.iobroker.net/post/848055

                                      kein Support per PN! - Fragen im Forum stellen -
                                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                      Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                      F 1 Reply Last reply
                                      1
                                      • HomoranH Homoran

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

                                        Ist das so richtig?

                                        ja!
                                        https://forum.iobroker.net/post/848055

                                        F Offline
                                        F Offline
                                        Frank06347
                                        wrote on last edited by
                                        #731

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

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

                                        Ist das so richtig?

                                        ja!
                                        https://forum.iobroker.net/post/848055

                                        Alles klar ... Fehler im Admin .... vielen Dank für schnelle Antwort!
                                        Viele Grüße
                                        Frank

                                        GlasfaserG 1 Reply Last reply
                                        0
                                        • F Frank06347

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

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

                                          Ist das so richtig?

                                          ja!
                                          https://forum.iobroker.net/post/848055

                                          Alles klar ... Fehler im Admin .... vielen Dank für schnelle Antwort!
                                          Viele Grüße
                                          Frank

                                          GlasfaserG Offline
                                          GlasfaserG Offline
                                          Glasfaser
                                          wrote on last edited by
                                          #732

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

                                          Alles klar ... Fehler im Admin ....

                                          Nur zur Klärung , das ist kein Fehler vom ADMIN !

                                          Deshalb habe ich hier :

                                          ... es soll nur verhindert werden : "verleitet nur zu unnötigen Installations/Upgrade-Versuchen."

                                          https://github.com/ioBroker/ioBroker.admin/issues/1663

                                          Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                          1 Reply Last reply
                                          2
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

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

                                          264

                                          Online

                                          32.7k

                                          Users

                                          82.5k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe