Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. npm ERR! Cannot read properties of null (reading 'parent')

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    npm ERR! Cannot read properties of null (reading 'parent')

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

      Hey!
      bekomme beim Updaten oder Installieren jeglicher Adapter folgendes:

      npm ERR! Cannot read properties of null (reading 'parent')
      npm ERR! A complete log of this run can be found in:
      npm ERR! /home/iobroker/.npm/_logs/2023-02-13T10_18_21_988Z-debug-0.log
      

      log von oben erzählt folgendes:

      37 timing idealTree Completed in 4838ms
      38 timing command:install Completed in 4859ms
      39 verbose stack TypeError: Cannot read properties of null (reading 'parent')
      39 verbose stack at Arborist.[resolveLinks] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:229:24)
      39 verbose stack at Arborist.[loadFromShrinkwrap] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:103:29)
      39 verbose stack at Arborist.loadVirtual (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:75:35)
      39 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:208:7)
      39 verbose stack at async Promise.all (index 1)
      39 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:154:5)
      39 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:145:5)
      39 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli.js:78:5)
      40 verbose cwd /opt/iobroker
      41 verbose Linux 5.15.84-v8+
      42 verbose node v16.19.0
      43 verbose npm v8.19.3
      44 error Cannot read properties of null (reading 'parent')
      45 verbose exit 1
      

      jemand ne idee?

      Pi4 4GB
      latest repo
      Node.js: v16.19.0
      NPM: v8.19.3
      ee5fd848-2f8e-4b3f-8efa-7c20b7bb74b9-image.png

      google, wie hier die suche hat bisher nichts ergeben
      iob fix und neustart ebenfalls nicht.

      vielen dank!

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

        Was kommt denn dabei:

        sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
        
        uname -m && type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
        
        
        B 1 Reply Last reply Reply Quote 0
        • B
          backfisch88 @wendy2702 last edited by backfisch88

          aarch64
          /usr/bin/nodejs
          /usr/bin/node
          /usr/bin/npm
          /usr/bin/npx
          v16.19.0
          v16.19.0
          8.19.3
          8.19.3
          4.0.24
          pi
          pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
          tty
          /home/pi
          Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:2 http://deb.debian.org/debian bullseye InRelease
          Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
          Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
          Get:5 https://repos.influxdata.com/debian stretch InRelease [7,021 B]
          Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
          Err:5 https://repos.influxdata.com/debian stretch InRelease
            The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          Fetched 7,021 B in 2s (3,346 B/s)
          Reading package lists... Done
          Building dependency tree... Done
          Reading state information... Done
          26 packages can be upgraded. Run 'apt list --upgradable' to see them.
          W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          W: Failed to fetch https://repos.influxdata.com/debian/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          W: Some index files failed to download. They have been ignored, or old ones used instead.
          nodejs:
            Installed: 16.19.0-deb-1nodesource1
            Candidate: 16.19.0-deb-1nodesource1
            Version table:
           *** 16.19.0-deb-1nodesource1 500
                  500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
                  100 /var/lib/dpkg/status
               12.22.12~dfsg-1~deb11u3 500
                  500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
               12.22.5~dfsg-2~11u1 500
                  500 http://deb.debian.org/debian bullseye/main arm64 Packages
          
          wendy2702 B 2 Replies Last reply Reply Quote 0
          • wendy2702
            wendy2702 @backfisch88 last edited by

            @backfisch88 sagte in npm ERR! Cannot read properties of null (reading 'parent'):

            Get:5 https://repos.influxdata.com/debian stretch InRelease [7,021 B]

            Hat vielleicht nicht direkt was mit deinem Problem zu tun, solltest du aber mal anpassen.

            kannst du noch die Ausgabe von

            iob diag
            

            zeigen

            1 Reply Last reply Reply Quote 0
            • B
              backfisch88 @backfisch88 last edited by backfisch88

              war natürlich Käse... hier nochmal das richtige

              ======================= SUMMARY =======================
                                   v.2023-01-02
              
              
              Operatingsystem:        Debian GNU/Linux 11 (bullseye)
              Installation:           Native
              Timezone:               Europe/Berlin
              User-ID:                1000
              X-Server:               false
              Boot Target:            multi-user.target
              
              Pending OS-Updates:     23
              
              Nodejs-Installation:    /usr/bin/nodejs         v16.19.0
                                      /usr/bin/node           v16.19.0
                                      /usr/bin/npm            8.19.3
                                      /usr/bin/npx            8.19.3
              
              ioBroker Core:          js-controller           4.0.24
                                      admin                   6.3.6
              
              ioBroker Status:        iobroker is running on this host.
              
              
              Objects type: jsonl
              States  type: redis
              
              Status admin:
              + system.adapter.admin.0                  : admin                 : IOBroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
              
              Pending iob updates:    1
              
              Active repo(s): Beta (latest)
              
              Objects:                43953
              States:                 36034
              
              Size of iob-Database:
              
              42M     /opt/iobroker/iobroker-data/objects.jsonl
              44K     /opt/iobroker/iobroker-data/states.jsonl
              
              
              =================== END OF SUMMARY ====================
              
              Glasfaser 1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @backfisch88 last edited by

                @backfisch88

                Mhh .. 🙄

                da stand doch vorhin mehr
                und du bist tief als BETA Tester unterwegs auch mit dem Alpha VIS 2 !?

                Mache mal :

                iobroker upload all
                npm prune
                sudo reboot
                

                dann

                iobroker upgrade tankerkoenig --debug
                
                B 1 Reply Last reply Reply Quote 0
                • B
                  backfisch88 @Glasfaser last edited by backfisch88

                  @glasfaser ja das war der log zwischendrin war nicht fertig gelaufen. Das ist der Bericht.

                  ne kein VIS2.
                  Bin auch der Meinung, dass vorgestern das updaten noch ging... habe in der Zeit aber auch nichts gemacht...

                  iobroker upgrade tankerkoenig --debug
                  
                  This upgrade of "tankerkoenig" will introduce the following changes:
                  ==========================================================================
                  -> 3.3.7:
                  added difference to jsonTable #116
                  added a log message for the error `parameter error`
                  set the name length to 34 characters
                  Added verification if the api key is encrypted
                  updated the Dependencies
                  ==========================================================================
                  
                  Would you like to upgrade tankerkoenig from @3.3.6 to @3.3.7 now? [(y)es, (n)o]: y
                  Update tankerkoenig from @3.3.6 to @3.3.7
                  host.IOBroker Adapter "system.adapter.tankerkoenig.0" is stopped.
                  host.IOBroker Adapter "system.adapter.tankerkoenig.1" is stopped.
                  NPM version: 8.19.3
                  Installing iobroker.tankerkoenig@3.3.7... (System call)
                  npm ERR! Cannot read properties of null (reading 'parent')
                  
                  npm ERR! A complete log of this run can be found in:
                  npm ERR!     /home/iobroker/.npm/_logs/2023-02-13T11_50_32_017Z-debug-0.log
                  upload [4] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/build/index.js build/index.js application/javascript
                  upload [3] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/build/index.js.map build/index.js.map application/json
                  upload [2] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/index_m.html index_m.html text/html
                  upload [1] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/style.css style.css text/css
                  upload [0] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/tankerkoenig.png tankerkoenig.png image/png
                  host.IOBroker Adapter "system.adapter.tankerkoenig.0" is started
                  host.IOBroker Adapter "system.adapter.tankerkoenig.1" is started
                  
                  

                  der log

                  0 verbose cli /usr/bin/node /usr/bin/npm
                  1 info using npm@8.19.3
                  2 info using node@v16.19.0
                  3 timing npm:load:whichnode Completed in 1ms
                  4 timing config:load:defaults Completed in 8ms
                  5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 3ms
                  6 timing config:load:builtin Completed in 5ms
                  7 timing config:load:cli Completed in 25ms
                  8 timing config:load:env Completed in 1ms
                  9 timing config:load:file:/opt/iobroker/.npmrc Completed in 31ms
                  10 timing config:load:project Completed in 48ms
                  11 timing config:load:file:/home/iobroker/.npmrc Completed in 1ms
                  12 timing config:load:user Completed in 2ms
                  13 timing config:load:file:/usr/etc/npmrc Completed in 0ms
                  14 timing config:load:global Completed in 1ms
                  15 timing config:load:validate Completed in 1ms
                  16 timing config:load:credentials Completed in 6ms
                  17 timing config:load:setEnvs Completed in 5ms
                  18 timing config:load Completed in 108ms
                  19 timing npm:load:configload Completed in 109ms
                  20 timing npm:load:mkdirpcache Completed in 4ms
                  21 timing npm:load:mkdirplogs Completed in 7ms
                  22 verbose title npm install iobroker.tankerkoenig@3.3.7
                  23 verbose argv "install" "--save-exact" "iobroker.tankerkoenig@3.3.7"
                  24 timing npm:load:setTitle Completed in 9ms
                  25 timing config:load:flatten Completed in 17ms
                  26 timing npm:load:display Completed in 22ms
                  27 verbose logfile logs-max:10 dir:/home/iobroker/.npm/_logs
                  28 verbose logfile /home/iobroker/.npm/_logs/2023-02-13T11_50_32_017Z-debug-0.log
                  29 timing npm:load:logFile Completed in 36ms
                  30 timing npm:load:timers Completed in 0ms
                  31 timing npm:load:configScope Completed in 0ms
                  32 timing npm:load Completed in 194ms
                  33 timing arborist:ctor Completed in 7ms
                  34 silly logfile start cleaning logs, removing 4 files
                  35 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules
                  36 silly logfile done cleaning log files
                  37 timing idealTree Completed in 8644ms
                  38 timing command:install Completed in 8682ms
                  39 verbose stack TypeError: Cannot read properties of null (reading 'parent')
                  39 verbose stack     at Arborist.[resolveLinks] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:229:24)
                  39 verbose stack     at Arborist.[loadFromShrinkwrap] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:103:29)
                  39 verbose stack     at Arborist.loadVirtual (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:75:35)
                  39 verbose stack     at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:208:7)
                  39 verbose stack     at async Promise.all (index 1)
                  39 verbose stack     at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:154:5)
                  39 verbose stack     at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:145:5)
                  39 verbose stack     at async module.exports (/usr/lib/node_modules/npm/lib/cli.js:78:5)
                  40 verbose cwd /opt/iobroker
                  41 verbose Linux 5.15.84-v8+
                  42 verbose node v16.19.0
                  43 verbose npm  v8.19.3
                  44 error Cannot read properties of null (reading 'parent')
                  45 verbose exit 1
                  46 timing npm Completed in 10677ms
                  47 verbose unfinished npm timer reify 1676289034004
                  48 verbose unfinished npm timer reify:loadTrees 1676289034023
                  49 verbose unfinished npm timer idealTree:init 1676289034027
                  50 verbose code 1
                  51 error A complete log of this run can be found in:
                  51 error     /home/iobroker/.npm/_logs/2023-02-13T11_50_32_017Z-debug-0.log
                  
                  
                  Glasfaser 3 Replies Last reply Reply Quote 0
                  • Glasfaser
                    Glasfaser @backfisch88 last edited by

                    @backfisch88 sagte in npm ERR! Cannot read properties of null (reading 'parent'):

                    35 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules

                    hast du ein NodeJS upgrade mal gemacht !?

                    versuche mal :

                    cd /opt/iobroker/node_modules
                    npm install --omit=dev
                    sudo reboot
                    

                    Ich habe keine Ahnung was das ist 'parent' , auf was es sich bezieht ...

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

                      @glasfaser

                      cd /opt/iobroker/node_modules
                      npm install --omit=dev
                      npm ERR! Cannot read properties of null (reading 'parent')
                      
                      npm ERR! A complete log of this run can be found in:
                      npm ERR!     /home/iobroker/.npm/_logs/2023-02-13T12_02_04_657Z-debug-0.log
                      

                      😐 das ist gut

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

                        @backfisch88 sagte in npm ERR! Cannot read properties of null (reading 'parent'):

                        failed to load node_modules/.package-lock.json out of date

                        dann ...

                        rm /opt/iobroker/node_modules/.package-lock.json
                        rm /opt/iobroker/node_modules/iobroker.javascript/node_modules/.package-lock.json
                        rm /opt/iobroker/package-lock.json
                        iob rebuild
                        
                        B Thomas Braun 2 Replies Last reply Reply Quote 1
                        • wendy2702
                          wendy2702 @backfisch88 last edited by

                          @backfisch88 sagte in npm ERR! Cannot read properties of null (reading 'parent'):

                          2023-02-13T12_02_04

                          Mal so zwischendurch gefragt:

                          Stimmen deine Zeiteinstellungen?

                          1 Reply Last reply Reply Quote 0
                          • B
                            backfisch88 last edited by

                            @wendy2702 ja stimmen 🙂

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

                              @backfisch88 Wieso dann im log eine Stunde hinter der Zeit oder steht der nicht in Deutschland bzw. in der gleichen Zeitzone?

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

                                @glasfaser also das läuft durch.... und der

                                iobroker upgrade tankerkoenig --debug
                                

                                scheint auch zu klappen... aus Interesse... was war es jetzt? 😄

                                1 Reply Last reply Reply Quote 0
                                • B
                                  backfisch88 @wendy2702 last edited by

                                  @wendy2702 said in npm ERR! Cannot read properties of null (reading 'parent'):

                                  nn im log eine Stunde hinter der Zeit oder steht der nicht in Deutschland bzw. in der gleichen Zeitzone

                                  das ist ne >hervorragende Frage... kann das eventuell mit der Sommer /Winterzeit zusammen hängen?

                                  
                                  pi@IOBroker:~ $ date
                                  Mon 13 Feb 13:17:47 CET 2023
                                  
                                  
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Glasfaser last edited by

                                    @glasfaser

                                    Ich überlege, ob die vier Zeilen nicht auch was für den iob fix wären.
                                    Hat bei mir gestern in etwas anderem Zusammenhang auch geholfen.

                                    Glasfaser 2 Replies Last reply Reply Quote 1
                                    • Glasfaser
                                      Glasfaser @Thomas Braun last edited by

                                      @thomas-braun sagte in npm ERR! Cannot read properties of null (reading 'parent'):

                                      Hat bei mir gestern in etwas anderem Zusammenhang auch geholfen.

                                      Ja ... ich weiß ...
                                      Bei Github war ich auch kurz dabei nur konnte ich diesen ( Fehler ) nicht simulieren

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

                                        @Thomas-Braun

                                        verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules

                                        Man sollte beobachten , bzw. ist mir schon öfters auch schon aufgefallen , das diese Meldung bei vielen erscheint !?

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

                                          @glasfaser sagte in npm ERR! Cannot read properties of null (reading 'parent'):

                                          Man sollte beobachten , bzw. ist mir schon öfters auch schon aufgefallen , das diese Meldung bei vielen erscheint !?

                                          Ja, das Format hat sich bei aktuelleren npm-Versionen geändert. Sollte eigentlich automatisch umgestellt werden, funktioniert aber offenbar nicht immer einwandfrei. Mit frischen package*-Files geht es dann.

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            backfisch88 @Thomas Braun last edited by

                                            @Glasfaser

                                            @glasfaser
                                            der Adapter ist jetzt geupdated.. Hab mal zum test einfach n neuen Adapter installiert... das dauert ewig und es geht nix voran
                                            dann kommt irgendwann

                                            npm WARN skipping integrity check for git dependency ssh://git@github.com/Newan/ioBroker.yahoo-stock-market.git
                                            
                                            npm WARN skipping integrity check for git dependency ssh://git@github.com/Steiger04/ioBroker.radar-trap2.git
                                            
                                            npm WARN skipping integrity check for git dependency ssh://git@github.com/excal-foley/ioBroker.blockly-plus.git
                                            

                                            sind alles Adapter aus github (nicht in der offiziellen list)

                                            das geht dann aber irgendwann und dann kommt bei jedem update aber wieder der gleiche Fehler

                                            Glasfaser 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            920
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            37
                                            1741
                                            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