Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. Troubleshooting NodeJS update

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Troubleshooting NodeJS update

    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chu @Thomas Braun last edited by

      @thomas-braun

      hab die Anleitung befolgt, nur der ioBroker hat es nicht erkannt. alles commands von heute:

       894  apt-get update
        895  apt-get upgrade
        896  reboot
        897  iob stop
        898  sudo apt purge --autoremove nodejs* npm node-*
        899  curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
        900  sudo apt install -y nodejs
        901  sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
        902  type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
        903  iob fix
        904  iob start
        905  apt-get update
        906  apt-get dist-upgrade
        907  reboot
        908  sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
        909  type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
        910  env
        911  npm i iobroker.sma-em
        912  npm install -g npm@9.8.1
        913  reboot
        914  apt-get update
        915  history
      
      

      Ich hatte bereits (mehrfach, 896 907) neu gestartet, aber nicht gesehen das der ioBroker das nicht erkannt hat und erst nach nach dem update und anschließendem reboot die neue version erkannt hat. solange jetzt alles funktioniert werde ich es erstmal so lassen 😄

      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Chu last edited by

        @chu

        iob stop
        sudo apt update 
        sudo apt install --reinstall nodejs
        iob start
        

        setzt dich da wieder auf das richtige Gleis.

        1 Reply Last reply Reply Quote 0
        • M
          MatthiasPetersen last edited by Negalein

          Hi, ich habe nodejs & Co. gemäß der Anleitung https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18 aktualisiert und bin jetzt auf den folgenden Versionen unterwegs:

          /usr/bin/nodejs
          /usr/bin/node
          /usr/bin/npm
          /usr/bin/npx
          v18.17.1
          v18.17.1
          9.6.7
          9.6.7
          

          Nun habe ich ein Update auf die aktuellste Version des Admin-Adapters gemacht und bekomme im Log die Meldung:

          2023-08-27 12:50:21.214  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: node:internal/modules/cjs/loader:1080
          2023-08-27 12:50:21.214  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   throw err;
          2023-08-27 12:50:21.214  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   ^
          2023-08-27 12:50:21.215  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Error: Cannot find module '@iobroker/types'
          2023-08-27 12:50:21.215  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Require stack:
          2023-08-27 12:50:21.215  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.admin/node_modules/@iobroker/adapter-core/build/index.js
          2023-08-27 12:50:21.215  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.admin/main.js
          2023-08-27 12:50:21.215  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
          2023-08-27 12:50:21.216  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:922:27)
          2023-08-27 12:50:21.216  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1143:19)
          2023-08-27 12:50:21.216  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at require (node:internal/modules/cjs/helpers:121:18)
          2023-08-27 12:50:21.217  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/node_modules/@iobroker/adapte$
          2023-08-27 12:50:21.217  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1256:14)
          2023-08-27 12:50:21.217  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
          2023-08-27 12:50:21.218  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1119:32)
          2023-08-27 12:50:21.218  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:960:12)
          2023-08-27 12:50:21.218  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1143:19) {
          2023-08-27 12:50:21.218  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
          2023-08-27 12:50:21.218  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   requireStack: [
          2023-08-27 12:50:21.219  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.admin/node_modules/@iobroker/adapter-core/build/index.js',
          2023-08-27 12:50:21.219  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.admin/main.js'
          2023-08-27 12:50:21.219  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   ]
          2023-08-27 12:50:21.219  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: }
          2023-08-27 12:50:21.219  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Node.js v18.17.1
          

          auch ein Reboot hat leider keine Verbesserung gebracht.

          Habt Ihr eine Idee, woran es liegen könnte?

          Viele Grüße im Voraus
          Matthias

          crunchip 1 Reply Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @MatthiasPetersen last edited by

            @matthiaspetersen sagte in Troubleshooting NodeJS update:

            aktualisiert und bin jetzt auf den folgenden Versionen unterwegs:

            sicher?

            M 1 Reply Last reply Reply Quote 0
            • M
              MatthiasPetersen @crunchip last edited by

              @crunchip
              Wenn Du so fragst ... ich hoffe, dass ich auf den Versionen unterwegs bin. Die Daten kommen gemäß der Anleitung, wenn ich die Befehle

              sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
              type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v

              absetze. Dass ich auf nodejs 18.17.1 bin steht auch beim Log am Ende der Fehlermeldung.

              crunchip 1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @MatthiasPetersen last edited by

                @matthiaspetersen und iobroker war vorher auch gestoppt?
                Augabe von

                iob diag
                
                M 1 Reply Last reply Reply Quote 0
                • M
                  MatthiasPetersen @crunchip last edited by

                  @crunchip Den iobroker hatte ich vorher per iob stop gestoppt.

                  iob diag sieht bei mir wie folgt aus:

                  ======================= SUMMARY =======================
                  		     v.2023-04-16
                  
                  
                  Operatingsystem: 	Raspbian GNU/Linux 10 (buster)
                  Kernel: 		5.10.103-v7l+
                  Installation: 		Native
                  Timezone: 		Europe/Berlin (CEST, +0200)
                  User-ID: 		1000
                  X-Server: 		false
                  Boot Target: 		graphical.target
                  
                  Pending OS-Updates: 	0
                  Pending iob updates: 	4
                  
                  Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
                  			/usr/bin/node 		v18.17.1
                  			/usr/bin/npm 		9.6.7
                  			/usr/bin/npx 		9.6.7
                  
                  Recommended versions are nodejs 18.x.y and npm 9.x.y
                  Your nodejs installation is correct
                  
                  MEMORY: 
                                total        used        free      shared  buff/cache   available
                  Mem:           3.8G        1.2G        1.8G        8.0M        826M        2.5G
                  Swap:           99M          0B         99M
                  Total:         3.9G        1.2G        1.9G
                  
                  Active iob-Instances: 	28
                  Active repo(s): stable
                  
                  ioBroker Core: 		js-controller 		4.0.24
                  			admin 			6.8.0
                  
                  ioBroker Status: 	iobroker is running on this host.
                  
                  
                  Objects type: jsonl
                  States  type: redis
                  
                  Status admin and web instance:
                    system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                  + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                  
                  Objects: 		9681
                  States: 		10090
                  
                  Size of iob-Database:
                  
                  13M	/opt/iobroker/iobroker-data/objects.jsonl
                  7.9M	/opt/iobroker/iobroker-data/objects.json.migrated
                  7.9M	/opt/iobroker/iobroker-data/objects.json.bak.migrated
                  0	/opt/iobroker/iobroker-data/objects.json.broken
                  144K	/opt/iobroker/iobroker-data/states.json.bak
                  144K	/opt/iobroker/iobroker-data/states.json
                  
                  
                  
                  =================== END OF SUMMARY ====================
                  

                  Hilft Dir das Summary oder soll ich lieber den ganzen Report mal schicken?

                  crunchip 1 Reply Last reply Reply Quote 0
                  • crunchip
                    crunchip Forum Testing Most Active @MatthiasPetersen last edited by crunchip

                    @matthiaspetersen sagte in Troubleshooting NodeJS update:

                    10 (buster)

                    du fährst ein altes System
                    https://forum.iobroker.net/post/667685

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      MatthiasPetersen @crunchip last edited by

                      @crunchip said in Troubleshooting NodeJS update:

                      https://forum.iobroker.net/post/667685

                      @crunchip Ah, danke für den Hinweis. Ich hatte die ganze Zeit ein Problem mit nodejs & Co. vermutet. Ich mache mal dann mal das Update auf Bullseye und führe ich die Schritte von https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18 nochmal durch.

                      Danke Dir

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        MatthiasPetersen @MatthiasPetersen last edited by Negalein

                        @matthiaspetersen
                        Ich bin jetzt auf bullseye und habe die Installation von nodejs & Co. nochmal gemacht. Der Fehler ist aber leider der Gleiche.

                        Hier ist das Ergebnis von iob diag:

                        ======================= SUMMARY =======================
                        		     v.2023-04-16
                        
                        
                        Operatingsystem: 	Raspbian GNU/Linux 11 (bullseye)
                        Kernel: 		5.10.103-v7l+
                        Installation: 		Native
                        Timezone: 		Europe/Berlin (CEST, +0200)
                        User-ID: 		1000
                        X-Server: 		false
                        Boot Target: 		graphical.target
                        
                        Pending OS-Updates: 	0
                        Pending iob updates: 	4
                        
                        Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
                        			/usr/bin/node 		v18.17.1
                        			/usr/bin/npm 		9.6.7
                        			/usr/bin/npx 		9.6.7
                        
                        Recommended versions are nodejs 18.x.y and npm 9.x.y
                        Your nodejs installation is correct
                        
                        MEMORY: 
                                       total        used        free      shared  buff/cache   available
                        Mem:            3.8G        193M        2.4G        0.0K        1.2G        3.5G
                        Swap:            99M          0B         99M
                        Total:          3.9G        193M        2.5G
                        
                        Active iob-Instances: 	1
                        Active repo(s): stable
                        
                        ioBroker Core: 		js-controller 		4.0.24
                        			admin 			6.8.0
                        
                        ioBroker Status: 	iobroker is not running on this host.
                        
                        
                        Objects type: jsonl
                        States  type: redis
                        
                        Status admin and web instance:
                          system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                          system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                        
                        Objects: 		9683
                        States: 		10056
                        
                        Size of iob-Database:
                        
                        11M	/opt/iobroker/iobroker-data/objects.jsonl
                        7.9M	/opt/iobroker/iobroker-data/objects.json.migrated
                        7.9M	/opt/iobroker/iobroker-data/objects.json.bak.migrated
                        0	/opt/iobroker/iobroker-data/objects.json.broken
                        144K	/opt/iobroker/iobroker-data/states.json.bak
                        144K	/opt/iobroker/iobroker-data/states.json
                        
                        
                        
                        =================== END OF SUMMARY ====================
                        
                        crunchip 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @MatthiasPetersen last edited by

                          @matthiaspetersen sagte in Troubleshooting NodeJS update:

                          Der Fehler ist aber leider der Gleiche.

                          welcher?

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            MatthiasPetersen @crunchip last edited by

                            @crunchip Hier ist die erste Meldung aus dem Log (taucht insgesamt ja 3x auf, weil 3x ein rebuild versucht wird:

                            2023-08-27 15:02:30.658  - ^[[32minfo^[[39m: host.iobroker instance system.adapter.ping.0 started with pid 10838
                            2023-08-27 15:02:31.138  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: node:internal/modules/cjs/loader:1080
                            2023-08-27 15:02:31.139  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   throw err;
                            2023-08-27 15:02:31.140  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   ^
                            2023-08-27 15:02:31.140  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Error: Cannot find module '@iobroker/types'
                            2023-08-27 15:02:31.141  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Require stack:
                            2023-08-27 15:02:31.141  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.admin/node_modules/@iobroker/adapter-core/build/>
                            2023-08-27 15:02:31.142  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.admin/main.js
                            2023-08-27 15:02:31.142  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
                            2023-08-27 15:02:31.143  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:922:27)
                            2023-08-27 15:02:31.143  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1143:19)
                            2023-08-27 15:02:31.144  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at require (node:internal/modules/cjs/helpers:121:18)
                            2023-08-27 15:02:31.144  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/node_modules/@iob>
                            2023-08-27 15:02:31.144  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1256:14)
                            2023-08-27 15:02:31.145  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
                            2023-08-27 15:02:31.145  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1119:32)
                            2023-08-27 15:02:31.146  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:960:12)
                            2023-08-27 15:02:31.147  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1143:19) {
                            2023-08-27 15:02:31.147  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
                            2023-08-27 15:02:31.148  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   requireStack: [
                            2023-08-27 15:02:31.148  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.admin/node_modules/@iobroker/adapter-core/bui>
                            2023-08-27 15:02:31.149  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.admin/main.js'
                            2023-08-27 15:02:31.149  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]:   ]
                            2023-08-27 15:02:31.150  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: }
                            2023-08-27 15:02:31.150  - ^[[31merror^[[39m: host.iobroker Caught by controller[0]: Node.js v18.17.1
                            2023-08-27 15:02:31.151  - ^[[31merror^[[39m: host.iobroker instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                            2023-08-27 15:02:31.151  - ^[[32minfo^[[39m: host.iobroker Adapter system.adapter.admin.0 needs rebuild and will be restarted afterwards.
                            2023-08-27 15:02:31.152  - ^[[32minfo^[[39m: host.iobroker system.adapter.admin.0 will be rebuilt
                            2023-08-27 15:02:31.153  - ^[[33mwarn^[[39m: host.iobroker adapter "admin" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt
                            2023-08-27 15:02:31.154  - ^[[32minfo^[[39m: host.iobroker iobroker rebuild
                            
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @MatthiasPetersen last edited by

                              @matthiaspetersen

                              Deinstallier den admin und reinstallier den frisch.

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

                                @thomas-braun Wenn ich den Admin-Adapter per

                                iob del admin
                                

                                lösche, dann bekomme ich ihn nicht weg, weil da diverse andere Adapter (backitup, history, ical etc.) abhängig sind. Meinst Du ein iob del admin?

                                crunchip 1 Reply Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @MatthiasPetersen last edited by

                                  @matthiaspetersen probier es mit

                                  iobroker rebuild admin --install
                                  
                                  M 1 Reply Last reply Reply Quote 1
                                  • M
                                    MatthiasPetersen @crunchip last edited by

                                    @crunchip @Thomas-Braun Vielen lieben Dank für Eure Unterstützung und Eure schnellen Antworten. Das

                                    iobroker rebuild admin --install
                                    

                                    hat geholfen.

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      Tobi81 last edited by

                                      Hallo zusammen.

                                      Ich hab heute mein Debian Stretch auf Debian Buster (10) upgedatet und natürlich direkt auch nodejs auch direkt auf Version 18.

                                      Das habe ich bei meinem Master-System im Dockercontainer gemacht, sowie auf einem Raspbian Slave System.

                                      Auf dem Raspbian scheint alles gut verlaufen zu sein.

                                      Auf dem Master läuft auch ioBroker, jedoch kann ich keine Module updaten.

                                      Im Admin kommt beim ersten Updateversuch folgende Meldung:

                                      iobroker upgrade heatingcontrol@2.11.1 --debug
                                      
                                      Update heatingcontrol from @2.10.6 to @2.11.1
                                      
                                      host.iobroker Adapter "system.adapter.heatingcontrol.0" is stopped.
                                      
                                      NPM version: 9.6.7
                                      
                                      Installing iobroker.heatingcontrol@2.11.1... (System call)
                                      
                                      npm WARN skipping integrity check for git dependency ssh://git@github.com/noopkat/browser-serialport.git
                                      
                                      npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
                                      
                                      npm WARN deprecated jscs-preset-wikimedia@1.0.1: No longer maintained. We recomment migrating to ESLint with eslint-config-wikimedia.
                                      
                                      npm WARN deprecated topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                                      
                                      npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                                      
                                      npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                                      
                                      npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
                                      
                                      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                      
                                      npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                                      
                                      npm WARN deprecated jscs@3.0.7: JSCS has merged with ESLint! See - https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
                                      
                                      npm WARN deprecated joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                                      
                                      npm WARN deprecated hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                                      
                                      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
                                      
                                      npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
                                      
                                      npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
                                      
                                      npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
                                      
                                      npm WARN deprecated appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                                      
                                      npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
                                      
                                      npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
                                      
                                      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                                      
                                      npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
                                      
                                      npm WARN cleanup Failed to remove some directories [
                                      
                                      npm WARN cleanup syscall: 'rmdir',
                                      
                                      npm WARN cleanup path: '/opt/iobroker/node_modules/cpu-features'npm WARN cleanup }npm WARN cleanup ],npm WARN cleanup [npm WARN cleanup '/opt/iobroker/node_modules/cpu-features',npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {npm WARN cleanup errno: -39,npm WARN cleanup code: 'ENOTEMPTY',npm WARN cleanup syscall: 'rmdir',npm WARN cleanup path: '/opt/iobroker/node_modules/cpu-features'npm WARN cleanup }npm WARN cleanup ]npm WARN cleanup ]
                                      
                                      npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
                                      
                                      npm ERR! command failednpm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuildnpm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird betretennpm ERR! CXX(target) Release/obj.target/bindings/src/serialport.onpm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird verlassennpm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using node-gyp@9.3.1npm ERR! gyp info using node@18.17.1 | linux | x64npm ERR! gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/@serialport/bindings/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.17.1/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.17.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:78:69: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);npm ERR! ^~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:135:71: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);npm ERR! ^~~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:175:70: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);npm ERR! ^~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:215:70: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);npm ERR! ^~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:270:68: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);npm ERR! ^~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:314:68: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);npm ERR! ^~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’:npm ERR! ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:363:76: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);npm ERR! ^~~~~~~~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’:
                                      
                                      npm ERR! ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’
                                      
                                      npm ERR! results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:
                                      
                                      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:409:70: 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]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                      
                                      npm ERR! ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]npm ERR! SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {npm ERR! ^npm ERR! In file included from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1014:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]npm ERR! (node::addon_register_func) (regfunc), \npm ERR! ^npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1048:3: note: in expansion of macro ‘NODE_MODULE_X’npm ERR! NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)npm ERR! ^~~~~~~~~~~~~npm ERR! ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’npm ERR! NODE_MODULE(serialport, init);npm ERR! ^~~~~~~~~~~npm ERR! make: *** [bindings.target.mk:116: Release/obj.target/bindings/src/serialport.o] Fehler 1npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:514:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)npm ERR! gyp ERR! System Linux 5.15.108-1-pvenpm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindingsnpm ERR! gyp ERR! node -v v18.17.1npm ERR! gyp ERR! node-gyp -v v9.3.1npm ERR! gyp ERR! not ok
                                      
                                      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_02_01_266Z-debug-0.log
                                      
                                      Update "system.adapter.heatingcontrol.0"
                                      
                                      upload [4] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/heatingcontrol.png heatingcontrol.png image/png
                                      
                                      upload [3] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/img/info-big.png img/info-big.png image/png
                                      
                                      upload [2] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/index_m.html index_m.html text/html
                                      
                                      upload [1] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/style.css style.css text/css
                                      
                                      upload [0] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/words.js words.js application/javascript
                                      
                                      host.iobroker Adapter "system.adapter.heatingcontrol.0" is started
                                      
                                      Process exited with code 0
                                      

                                      Bei Updateversuchen weiterer Module ist die Ausgabe dann kürzer:

                                      $ iobroker upgrade ping@1.6.2 --debug
                                      
                                      Update ping from @1.5.3 to @1.6.2
                                      
                                      NPM version: 9.6.7
                                      
                                      Installing iobroker.ping@1.6.2... (System call)
                                      
                                      npm ERR! code ENOTEMPTYnpm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/cpu-featuresnpm ERR! dest /opt/iobroker/node_modules/.cpu-features-JirOBYx7npm ERR! errno -39
                                      
                                      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_16_17_169Z-debug-0.log
                                      
                                      host.iobroker Cannot install iobroker.ping@1.6.2: 217
                                      
                                      ERROR: Process exited with code 25
                                      

                                      Installiert ist mein System wie folgt:

                                      ======================= SUMMARY =======================
                                      		     v.2023-04-16
                                      
                                      
                                      Operatingsystem: 	Debian GNU/Linux 10 (buster)
                                      Kernel: 		5.15.108-1-pve
                                      Installation: 		lxc
                                      Failed to query server: Connection timed out
                                      Timezone: 		
                                      User-ID: 		1000
                                      X-Server: 		false
                                      Boot Target: 		graphical.target
                                      
                                      Pending OS-Updates: 	0
                                      Pending iob updates: 	12
                                      
                                      Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
                                      			/usr/bin/node 		v18.17.1
                                      			/usr/bin/npm 		9.6.7
                                      			/usr/bin/npx 		9.6.7
                                      
                                      Recommended versions are nodejs 18.x.y and npm 9.x.y
                                      Your nodejs installation is correct
                                      
                                      MEMORY: 
                                                    total        used        free      shared  buff/cache   available
                                      Mem:           4.1G        2.5G        775M        8.0M        778M        1.6G
                                      Swap:          4.1G        0.0K        4.1G
                                      Total:         8.2G        2.5G        4.9G
                                      
                                      Active iob-Instances: 	43
                                      Active repo(s): stable
                                      
                                      ioBroker Core: 		js-controller 		4.0.24
                                      			admin 			6.3.5
                                      
                                      ioBroker Status: 	iobroker is running on this host.
                                      
                                      
                                      Objects type: jsonl
                                      States  type: jsonl
                                      
                                      Status admin and web instance:
                                      + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                      + system.adapter.admin.1                  : admin                 : iobroker2                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                      + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                      
                                      Objects: 		14436
                                      States: 		12673
                                      
                                      Size of iob-Database:
                                      
                                      14M	/opt/iobroker/iobroker-data/objects.jsonl
                                      14M	/opt/iobroker/iobroker-data/objects.json.migrated
                                      14M	/opt/iobroker/iobroker-data/objects.json.bak.migrated
                                      14M	/opt/iobroker/iobroker-data/states.jsonl
                                      2.4M	/opt/iobroker/iobroker-data/states.json.migrated
                                      2.4M	/opt/iobroker/iobroker-data/states.json.bak.migrated
                                      
                                      
                                      *********************************************************************
                                      Some problems detected, please run iob fix and try to have them fixed
                                      *********************************************************************
                                      
                                      =================== END OF SUMMARY ====================
                                      

                                      iob fix habe ich natürlich schon oft ausprobiert.

                                      mikeal created this issue in request/request

                                      open Request’s Past, Present and Future #3142

                                      mikeal created this issue in request/request

                                      open Request’s Past, Present and Future #3142

                                      mikeal created this issue in request/request

                                      open Request’s Past, Present and Future #3142

                                      Qix- created this issue in visionmedia/debug

                                      closed ReDos Vulnerability Regression Visibility Notice #797

                                      crunchip DJMarc75 2 Replies Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Tobi81 last edited by crunchip

                                        @tobi81 sagte in Troubleshooting NodeJS update:

                                        ERROR: Process exited with code 25

                                        ist oben angepinnt bei NEWS

                                        1 Reply Last reply Reply Quote 0
                                        • DJMarc75
                                          DJMarc75 @Tobi81 last edited by

                                          @tobi81 sagte in Troubleshooting NodeJS update:

                                          hab heute mein Debian Stretch auf Debian Buster (10) upgedate

                                          von Tod auf Sterbebett quasi 😉

                                          Warum nicht auf Bullseye ? Welche dubiose Anleitung hast Du verwendet ?

                                          Und wie @crunchip schrieb, die Lösung ist angepinnt 😉

                                          crunchip 1 Reply Last reply Reply Quote 0
                                          • crunchip
                                            crunchip Forum Testing Most Active @DJMarc75 last edited by

                                            @djmarc75 sagte in Troubleshooting NodeJS update:

                                            Warum nicht auf Bullseye

                                            weil per update nicht überspringen kann

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            598
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            nodejs 18 nodejs update
                                            60
                                            495
                                            74684
                                            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