Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update

    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

    Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update

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

      @surfer09 sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

      @apollon77 Den Tipp hatte ich auch schon bekommen, brachte aber auch nichts.

      Mal Windows rebootet? Virenscanner deaktiviert bzw Verzeichnis ausgenommen?

      1 Reply Last reply Reply Quote 0
      • S
        Soldierofoc last edited by Soldierofoc

        Möchte mich an diesen Thread (wenn i.O.?) dran hängen, da es doch ziemlich ähnlich ist (wenn auch auf Ubuntu, anstatt Windows).
        Leider weiß ich aktuell nicht mehr weiter. Habe zur Sicherheit, bevor ich angefangen habe, heute morgen ein aktuelles Backup gezogen (zum Glück).

        Was könnte ich nun noch tun? Ich wäre über eure Hilfe sehr, sehr dankbar.

        Node.js: v16.15.1
        NPM: 8.11.0

        Ubuntu 20.04LTS

        Habe von Node.js 14 auf eben 16.15.1 via Anleitung geupgraded.
        Alle Adapter laufen auch soweit. Nur erhalte ich nun auch, wie hier schon erwähnt, beim Update von Adaptern oder bei Neuinstallation von Adapter immer die gleiche Meldung:

        $ iobroker add heizoel auto --host Server
        
        NPM version: 8.11.0
        
        Installing iobroker.heizoel@1.0.3... (System call)
        
        host.Server Cannot install iobroker.heizoel@1.0.3: 128
        
        ERROR: Process exited with code 25
        

        Habe dann unter anderem den iobroker-fix versucht, welcher ohne Error-Messages durchgelaufen ist.
        Ebenfalls dann noch npm rebuild - ohne Erfolg.

        Wenn ich nun "npm ls" ausführe, erhalte ich (sehr) unschöne Meldungen
        Unter anderem folgende:

        UNMET DEPENDENCY iobroker.ring@2.0.0-beta.3

        --> Ring, Yeelight, Boschebike habe ich aber alle bereits deinstalliert gehabt.

        Jene machen mir am meisten Sorgen:

        npm ERR! code ELSPROBLEMS
        npm ERR! extraneous........

        iobroker.inst@3.0.0 /opt/iobroker
        ├── @homebridge/camera-utils@2.0.4 extraneous
        ├── @homebridge/plugin-ui-utils@0.0.19 extraneous
        ├── @types/caseless@0.12.2 extraneous
        ├── @types/request@2.48.8 extraneous
        ├── @types/socket.io-client@1.4.36 extraneous
        ├── @types/tough-cookie@4.0.2 extraneous
        ├── array-find-index@1.0.2 extraneous
        ├── basic-auth@2.0.1 extraneous
        ├── binary-data@0.6.0 extraneous
        ├── body-parser@1.19.1 extraneous
        ├── buffer-xor@2.0.2 extraneous
        ├── bytes@3.1.1 extraneous
        ├── clone-deep@4.0.1 extraneous
        ├── coffee-compiler@0.3.2 extraneous
        ├── coffee-script@1.12.7 extraneous
        ├── colors@1.4.0 extraneous
        ├── currently-unhandled@0.4.1 extraneous
        ├── decode-uri-component@0.2.0 extraneous
        ├── destroy@1.0.4 extraneous
        ├── dotenv@8.6.0 extraneous
        ├── esm@3.2.25 extraneous
        ├── events@3.3.0 extraneous
        ├── express@4.17.2 extraneous
        ├── ffmpeg-for-homebridge@0.0.9 extraneous
        ├── filter-obj@1.1.0 extraneous
        ├── finalhandler@1.1.2 extraneous
        ├── generate-function@2.3.1 extraneous
        ├── http-errors@1.8.1 extraneous
        ├── http-headers@1.2.0 extraneous
        ├── http2-wrapper@1.0.3 extraneous
        ├── iobroker-object-helper@0.0.1 extraneous (git+ssh://git@github.com/gaudes/iobroker-object-helper.git#3918c20736ef758d3c3937546c74055baf431cad)
        ├── iobroker.admin@6.0.8
        ├── iobroker.backitup@2.4.9
        ├── UNMET DEPENDENCY iobroker.boschebike@github:gaudes/ioBroker.boschebike#caab76421a131da61a7a8bbb8cd07bad28711e3e
        ├── iobroker.deconz@2.0.5
        ├── iobroker.denon@1.13.4
        ├── iobroker.device-reminder@1.2.9
        ├── iobroker.discovery@3.0.5
        ├── iobroker.enigma2@1.3.2 (git+ssh://git@github.com/Matten-Matten/ioBroker.enigma2.git#9d3d3b7f884e7bd309db9a1c1984b69fb0528e17)
        ├── iobroker.feiertage@1.1.0
        ├── iobroker.harmony@1.2.2
        ├── iobroker.history@2.1.4
        ├── iobroker.hm-rega@3.0.40
        ├── iobroker.hm-rpc@1.15.12
        ├── iobroker.homepilot20@0.0.20 (git+ssh://git@github.com/homecineplexx/ioBroker.homepilot20.git#50c148dbb4533998d206592a1cc51d62b7ec2ad9)
        ├── iobroker.hue@3.7.0
        ├── iobroker.ical@1.13.0
        ├── iobroker.icons-icons8@0.0.1
        ├── iobroker.icons-mfd-png@1.1.0
        ├── iobroker.influxdb@3.1.5
        ├── iobroker.info@1.9.19
        ├── iobroker.iot@1.11.7
        ├── iobroker.javascript@5.7.0
        ├── iobroker.js-controller@4.0.23
        ├── iobroker.lgtv@1.1.10
        ├── iobroker.linux-control@1.1.5
        ├── iobroker.mihome-airpurifier@0.1.8
        ├── iobroker.mihome-vacuum@3.4.1
        ├── iobroker.miio@0.0.13
        ├── iobroker.net-tools@0.2.0
        ├── iobroker.octoprint@4.0.0
        ├── UNMET DEPENDENCY iobroker.parcel@0.0.13
        ├── iobroker.pi-hole@1.3.4
        ├── iobroker.ping@1.5.3
        ├── UNMET DEPENDENCY iobroker.ring@2.0.0-beta.3
        ├── iobroker.scenes@2.3.9
        ├── iobroker.senec@1.3.7
        ├── iobroker.simple-api@2.7.0
        ├── iobroker.smartgarden@2.0.0
        ├── iobroker.snmp@1.0.0
        ├── iobroker.socketio@6.1.7
        ├── iobroker.sonoff@2.5.1
        ├── iobroker.sonos@2.2.2
        ├── iobroker.telegram@1.13.0
        ├── iobroker.tradfri@3.1.3
        ├── iobroker.trashschedule@2.0.3
        ├── iobroker.tvprogram@1.1.2
        ├── iobroker.unifi-protect@0.0.12
        ├── iobroker.unifi@0.6.1
        ├── iobroker.viessmannapi@2.0.9
        ├── iobroker.vis-colorpicker@1.2.0
        ├── iobroker.vis-fancyswitch@1.1.0
        ├── iobroker.vis-google-fonts@1.0.3
        ├── iobroker.vis-hqwidgets@1.2.0
        ├── iobroker.vis-icontwo@0.87.0
        ├── iobroker.vis-material-webfont@0.0.3
        ├── iobroker.vis-materialdesign@0.5.9
        ├── iobroker.vis-timeandweather@1.1.7
        ├── iobroker.vis-weather@2.5.5
        ├── iobroker.vis@1.4.15
        ├── iobroker.vofo-speedtest@0.0.13
        ├── iobroker.web-speedy@0.2.0
        ├── iobroker.web@5.2.3
        ├── iobroker.wled@0.6.7
        ├── iobroker.ws@2.1.2
        ├── UNMET DEPENDENCY iobroker.yeelight-2@1.2.1
        ├── ip2buf@2.0.0 extraneous
        ├── is-property@1.0.2 extraneous
        ├── is-ssh@1.3.3 extraneous
        ├── is-stun@2.0.0 extraneous
        ├── json-parse-better-errors@1.0.2 extraneous
        ├── jsonata@1.8.6 extraneous
        ├── load-json-file@4.0.0 extraneous
        ├── loud-rejection@1.6.0 extraneous
        ├── next-line@1.1.0 extraneous
        ├── node-inspect@2.0.0 extraneous
        ├── on-finished@2.3.0 extraneous
        ├── parse-path@4.0.3 extraneous
        ├── parse-url@5.0.7 extraneous
        ├── pick-port@1.0.0 extraneous
        ├── picocolors@1.0.0 extraneous
        ├── pify@3.0.0 extraneous
        ├── protocols@1.4.8 extraneous
        ├── query-string@6.14.1 extraneous
        ├── raw-body@2.4.2 extraneous
        ├── resolve-alpn@1.2.1 extraneous
        ├── ring-client-api@9.24.0 extraneous
        ├── rtsp-server@1.2.2 extraneous
        ├── rtsp-stream@1.0.0 extraneous
        ├── rtsp-streaming-server@2.0.6 extraneous
        ├── sdp@3.0.3 extraneous
        ├── send@0.17.2 extraneous
        ├── serve-static@1.14.2 extraneous
        ├── shallow-clone@3.0.1 extraneous
        ├── split-on-first@1.1.0 extraneous
        ├── statuses@1.5.0 extraneous
        ├── strict-uri-encode@2.0.0 extraneous
        ├── strip-lines@1.0.1 extraneous
        ├── suncalc2@1.8.1 extraneous
        ├── turbo-crc32@1.0.1 extraneous
        ├── typescript@4.6.4 extraneous
        ├── virtual-tsc@0.6.2 extraneous
        └── vm2@3.9.9 extraneous
        
        npm ERR! code ELSPROBLEMS
        npm ERR! extraneous: @homebridge/camera-utils@2.0.4 /opt/iobroker/node_modules/@homebridge/camera-utils
        npm ERR! extraneous: @homebridge/plugin-ui-utils@0.0.19 /opt/iobroker/node_modules/@homebridge/plugin-ui-utils
        npm ERR! extraneous: @types/caseless@0.12.2 /opt/iobroker/node_modules/@types/caseless
        npm ERR! extraneous: @types/request@2.48.8 /opt/iobroker/node_modules/@types/request
        npm ERR! extraneous: @types/socket.io-client@1.4.36 /opt/iobroker/node_modules/@types/socket.io-client
        npm ERR! extraneous: @types/tough-cookie@4.0.2 /opt/iobroker/node_modules/@types/tough-cookie
        npm ERR! extraneous: array-find-index@1.0.2 /opt/iobroker/node_modules/array-find-index
        npm ERR! extraneous: basic-auth@2.0.1 /opt/iobroker/node_modules/basic-auth
        npm ERR! extraneous: binary-data@0.6.0 /opt/iobroker/node_modules/binary-data
        npm ERR! extraneous: body-parser@1.19.1 /opt/iobroker/node_modules/body-parser
        npm ERR! extraneous: buffer-xor@2.0.2 /opt/iobroker/node_modules/buffer-xor
        npm ERR! extraneous: bytes@3.1.1 /opt/iobroker/node_modules/bytes
        npm ERR! extraneous: clone-deep@4.0.1 /opt/iobroker/node_modules/clone-deep
        npm ERR! extraneous: coffee-compiler@0.3.2 /opt/iobroker/node_modules/coffee-compiler
        npm ERR! extraneous: coffee-script@1.12.7 /opt/iobroker/node_modules/coffee-script
        npm ERR! extraneous: colors@1.4.0 /opt/iobroker/node_modules/colors
        npm ERR! extraneous: currently-unhandled@0.4.1 /opt/iobroker/node_modules/currently-unhandled
        npm ERR! extraneous: decode-uri-component@0.2.0 /opt/iobroker/node_modules/decode-uri-component
        npm ERR! extraneous: destroy@1.0.4 /opt/iobroker/node_modules/destroy
        npm ERR! extraneous: dotenv@8.6.0 /opt/iobroker/node_modules/dotenv
        npm ERR! extraneous: esm@3.2.25 /opt/iobroker/node_modules/esm
        npm ERR! extraneous: events@3.3.0 /opt/iobroker/node_modules/events
        npm ERR! extraneous: express@4.17.2 /opt/iobroker/node_modules/express
        npm ERR! extraneous: ffmpeg-for-homebridge@0.0.9 /opt/iobroker/node_modules/ffmpeg-for-homebridge
        npm ERR! extraneous: filter-obj@1.1.0 /opt/iobroker/node_modules/filter-obj
        npm ERR! extraneous: finalhandler@1.1.2 /opt/iobroker/node_modules/finalhandler
        npm ERR! extraneous: generate-function@2.3.1 /opt/iobroker/node_modules/generate-function
        npm ERR! extraneous: http-errors@1.8.1 /opt/iobroker/node_modules/http-errors
        npm ERR! extraneous: http-headers@1.2.0 /opt/iobroker/node_modules/http-headers
        npm ERR! extraneous: http2-wrapper@1.0.3 /opt/iobroker/node_modules/http2-wrapper
        npm ERR! extraneous: iobroker-object-helper@0.0.1 /opt/iobroker/node_modules/iobroker-object-helper
        npm ERR! missing: iobroker.boschebike@github:gaudes/ioBroker.boschebike#caab76421a131da61a7a8bbb8cd07bad28711e3e, required by iobroker.inst@3.0.0
        npm ERR! missing: iobroker.parcel@0.0.13, required by iobroker.inst@3.0.0
        npm ERR! missing: iobroker.ring@2.0.0-beta.3, required by iobroker.inst@3.0.0
        npm ERR! missing: iobroker.yeelight-2@1.2.1, required by iobroker.inst@3.0.0
        npm ERR! extraneous: ip2buf@2.0.0 /opt/iobroker/node_modules/ip2buf
        npm ERR! extraneous: is-property@1.0.2 /opt/iobroker/node_modules/is-property
        npm ERR! extraneous: is-ssh@1.3.3 /opt/iobroker/node_modules/is-ssh
        npm ERR! extraneous: is-stun@2.0.0 /opt/iobroker/node_modules/is-stun
        npm ERR! extraneous: json-parse-better-errors@1.0.2 /opt/iobroker/node_modules/json-parse-better-errors
        npm ERR! extraneous: jsonata@1.8.6 /opt/iobroker/node_modules/jsonata
        npm ERR! extraneous: load-json-file@4.0.0 /opt/iobroker/node_modules/load-json-file
        npm ERR! extraneous: loud-rejection@1.6.0 /opt/iobroker/node_modules/loud-rejection
        npm ERR! extraneous: next-line@1.1.0 /opt/iobroker/node_modules/next-line
        npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect
        npm ERR! extraneous: on-finished@2.3.0 /opt/iobroker/node_modules/on-finished
        npm ERR! extraneous: parse-path@4.0.3 /opt/iobroker/node_modules/parse-path
        npm ERR! extraneous: parse-url@5.0.7 /opt/iobroker/node_modules/parse-url
        npm ERR! extraneous: pick-port@1.0.0 /opt/iobroker/node_modules/pick-port
        npm ERR! extraneous: picocolors@1.0.0 /opt/iobroker/node_modules/picocolors
        npm ERR! extraneous: pify@3.0.0 /opt/iobroker/node_modules/pify
        npm ERR! extraneous: protocols@1.4.8 /opt/iobroker/node_modules/protocols
        npm ERR! extraneous: query-string@6.14.1 /opt/iobroker/node_modules/query-string
        npm ERR! extraneous: raw-body@2.4.2 /opt/iobroker/node_modules/raw-body
        npm ERR! extraneous: resolve-alpn@1.2.1 /opt/iobroker/node_modules/resolve-alpn
        npm ERR! extraneous: ring-client-api@9.24.0 /opt/iobroker/node_modules/ring-client-api
        npm ERR! extraneous: rtsp-server@1.2.2 /opt/iobroker/node_modules/rtsp-server
        npm ERR! extraneous: rtsp-stream@1.0.0 /opt/iobroker/node_modules/rtsp-stream
        npm ERR! extraneous: rtsp-streaming-server@2.0.6 /opt/iobroker/node_modules/rtsp-streaming-server
        npm ERR! extraneous: sdp@3.0.3 /opt/iobroker/node_modules/sdp
        npm ERR! extraneous: send@0.17.2 /opt/iobroker/node_modules/send
        npm ERR! extraneous: serve-static@1.14.2 /opt/iobroker/node_modules/serve-static
        npm ERR! extraneous: shallow-clone@3.0.1 /opt/iobroker/node_modules/shallow-clone
        npm ERR! extraneous: split-on-first@1.1.0 /opt/iobroker/node_modules/split-on-first
        npm ERR! extraneous: statuses@1.5.0 /opt/iobroker/node_modules/statuses
        npm ERR! extraneous: strict-uri-encode@2.0.0 /opt/iobroker/node_modules/strict-uri-encode
        npm ERR! extraneous: strip-lines@1.0.1 /opt/iobroker/node_modules/strip-lines
        npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2
        npm ERR! extraneous: turbo-crc32@1.0.1 /opt/iobroker/node_modules/turbo-crc32
        npm ERR! extraneous: typescript@4.6.4 /opt/iobroker/node_modules/typescript
        npm ERR! extraneous: virtual-tsc@0.6.2 /opt/iobroker/node_modules/virtual-tsc
        npm ERR! extraneous: vm2@3.9.9 /opt/iobroker/node_modules/vm2
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/iobroker/.npm/_logs/2022-06-22T09_37_19_239Z-debug-0.log
        
        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @Soldierofoc last edited by apollon77

          @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

          iobroker add heizoel auto --host Server

          Naja ... also mit den Infos von "dem Thread wo Du dich angehängt hast" hätte ich erwartet das Du gleich die Ausgabe von `iobroker add heizoel auto --host Server --debug´ postest 😉

          1 Reply Last reply Reply Quote 0
          • S
            Soldierofoc last edited by Soldierofoc

            Sorry, bin noch nicht so im Thema drin 🙂 Danke für den Hinweis. Hier mit Debug:

            
            server@Server:/opt/iobroker$ iobroker add heizoel auto --host Server --debug
            NPM version: 8.11.0
            Installing iobroker.heizoel@1.0.3... (System call)
            npm WARN old lockfile
            npm WARN old lockfile The package-lock.json file was created with an old version of npm,
            npm WARN old lockfile so supplemental metadata must be fetched from the registry.
            npm WARN old lockfile
            npm WARN old lockfile This is a one-time fix-up, please be patient...
            npm WARN old lockfile
            npm WARN old lockfile Error: An unknown git error occurred
            npm WARN old lockfile     at makeError (/usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
            npm WARN old lockfile     at /usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
            npm WARN old lockfile     at runMicrotasks (<anonymous>)
            npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5)
            npm WARN old lockfile  Could not fetch metadata for iobroker.boschebike@git+ssh://git@github.com/gaudes/ioBroker.boschebike.git#caab76421a131da61a7a8bbb8cd07bad28711e3e GitUnknownError: An unknown git error occurred
            npm WARN old lockfile     at makeError (/usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
            npm WARN old lockfile     at /usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
            npm WARN old lockfile     at runMicrotasks (<anonymous>)
            npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
            npm WARN old lockfile   cmd: 'git',
            npm WARN old lockfile   args: [
            npm WARN old lockfile     '--no-replace-objects',
            npm WARN old lockfile     'ls-remote',
            npm WARN old lockfile     'ssh://git@github.com/gaudes/ioBroker.boschebike.git'
            npm WARN old lockfile   ],
            npm WARN old lockfile   code: 128,
            npm WARN old lockfile   signal: null,
            npm WARN old lockfile   stdout: '',
            npm WARN old lockfile   stderr: 'git@github.com: Permission denied (publickey).\r\n' +
            npm WARN old lockfile     'fatal: Konnte nicht vom Remote-Repository lesen.\n' +
            npm WARN old lockfile     '\n' +
            npm WARN old lockfile     'Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen\n' +
            npm WARN old lockfile     'und das Repository existiert.\n'
            npm WARN old lockfile }
            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 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 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 circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
            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 ERR! code 128
            npm ERR! An unknown git error occurred
            npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/gaudes/ioBroker.boschebike.git
            npm ERR! git@github.com: Permission denied (publickey).
            npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.
            npm ERR!
            npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen
            npm ERR! und das Repository existiert.
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/iobroker/.npm/_logs/2022-06-22T09_50_12_054Z-debug-0.log
            host.Server Cannot install iobroker.heizoel@1.0.3: 128
            
            

            Wiederum der Inhalt der der Debug-0.log:

            0 verbose cli /usr/local/bin/node /usr/local/bin/npm
            1 info using npm@8.11.0
            2 info using node@v16.15.1
            3 timing npm:load:whichnode Completed in 0ms
            4 timing config:load:defaults Completed in 1ms
            5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 1ms
            6 timing config:load:builtin Completed in 1ms
            7 timing config:load:cli Completed in 3ms
            8 timing config:load:env Completed in 0ms
            9 timing config:load:file:/opt/iobroker/.npmrc Completed in 1ms
            10 timing config:load:project Completed in 8ms
            11 timing config:load:file:/home/iobroker/.npmrc Completed in 0ms
            12 timing config:load:user Completed in 0ms
            13 timing config:load:file:/usr/local/etc/npmrc Completed in 0ms
            14 timing config:load:global Completed in 0ms
            15 timing config:load:validate Completed in 0ms
            16 timing config:load:credentials Completed in 1ms
            17 timing config:load:setEnvs Completed in 0ms
            18 timing config:load Completed in 15ms
            19 timing npm:load:configload Completed in 15ms
            20 timing npm:load:mkdirpcache Completed in 1ms
            21 timing npm:load:mkdirplogs Completed in 0ms
            22 verbose title npm install iobroker.heizoel@1.0.3
            23 verbose argv "install" "--save-exact" "iobroker.heizoel@1.0.3"
            24 timing npm:load:setTitle Completed in 1ms
            25 timing config:load:flatten Completed in 2ms
            26 timing npm:load:display Completed in 3ms
            27 verbose logfile logs-max:10 dir:/home/iobroker/.npm/_logs
            28 verbose logfile /home/iobroker/.npm/_logs/2022-06-22T09_50_12_054Z-debug-0.log
            29 timing npm:load:logFile Completed in 3ms
            30 timing npm:load:timers Completed in 0ms
            31 timing npm:load:configScope Completed in 0ms
            32 timing npm:load Completed in 24ms
            33 timing arborist:ctor Completed in 1ms
            34 silly logfile start cleaning logs, removing 2 files
            35 silly logfile done cleaning log files
            36 timing idealTree:init Completed in 849ms
            37 warn old lockfile
            37 warn old lockfile The package-lock.json file was created with an old version of npm,
            37 warn old lockfile so supplemental metadata must be fetched from the registry.
            37 warn old lockfile
            37 warn old lockfile This is a one-time fix-up, please be patient...
            37 warn old lockfile
            38 silly inflate node_modules/@alcalzone/esbuild-register
            39 silly inflate node_modules/@alcalzone/jsonl-db
            40 silly inflate node_modules/@alcalzone/pak
            41 silly inflate node_modules/@alcalzone/pak/node_modules/fs-extra
            42 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules
            43 http fetch GET 200 https://registry.npmjs.org/fs-extra 1212ms (cache revalidated)
            44 silly inflate node_modules/@apollon/iobroker-tools
            45 http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fjsonl-db 1236ms (cache revalidated)
            46 silly inflate node_modules/@babel/code-frame
            47 http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fesbuild-register 1241ms (cache revalidated)
            48 silly inflate node_modules/@babel/helper-validator-identifier
            49 http fetch GET 200 https://registry.npmjs.org/@babel%2fhelper-validator-identifier 61ms (cache revalidated)
            50 silly inflate node_modules/@babel/highlight
            51 http fetch GET 200 https://registry.npmjs.org/@babel%2fcode-frame 75ms (cache revalidated)
            52 silly inflate node_modules/@babel/highlight/node_modules/ansi-styles
            53 http fetch GET 200 https://registry.npmjs.org/@apollon%2fiobroker-tools 118ms (cache revalidated)
            54 silly inflate node_modules/@babel/highlight/node_modules/chalk
            55 http fetch GET 200 https://registry.npmjs.org/ansi-styles 43ms (cache revalidated)
            56 silly inflate node_modules/@babel/highlight/node_modules/escape-string-regexp
            57 http fetch GET 200 https://registry.npmjs.org/@babel%2fhighlight 68ms (cache revalidated)
            58 silly inflate node_modules/@babel/highlight/node_modules/has-flag
            59 http fetch GET 200 https://registry.npmjs.org/chalk 44ms (cache revalidated)
            60 silly inflate node_modules/@babel/highlight/node_modules/supports-color
            61 http fetch GET 200 https://registry.npmjs.org/escape-string-regexp 37ms (cache revalidated)
            62 silly inflate node_modules/@colors/colors
            63 http fetch GET 200 https://registry.npmjs.org/has-flag 51ms (cache revalidated)
            64 silly inflate node_modules/@dabh/diagnostics
            65 http fetch GET 200 https://registry.npmjs.org/supports-color 59ms (cache revalidated)
            66 silly inflate node_modules/@datalust/winston-seq
            67 http fetch GET 200 https://registry.npmjs.org/@colors%2fcolors 67ms (cache revalidated)
            68 silly inflate node_modules/@googleapis/drive
            "2022-06-22T09_50_12_054Z-debug-0.log" 5071 lines, 381287 characters
            
            
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Soldierofoc last edited by

              @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

              /usr/local/bin/node

              Vermutlich nodejs auch noch falsch installiert.
              Schau in meiner Signatur wie es richtig geht.
              Wie hast du node16 installiert?

              S 1 Reply Last reply Reply Quote 0
              • S
                Soldierofoc last edited by

                Nach dieser Anleitung hier & eben durch Node16 ersetzt:

                https://forum.iobroker.net/topic/22867/how-to-node-js-für-iobroker-richtig-updaten

                curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
                sudo apt-get install -y nodejs

                1 Reply Last reply Reply Quote 0
                • S
                  Soldierofoc @Thomas Braun last edited by Soldierofoc

                  @thomas-braun
                  Habe deine Signatur geprüft (anbei - Top Anleitung!):

                  ich erhalte nun folgendes:

                   uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                  x86_64
                  /usr/bin/nodejs
                  /usr/local/bin/node
                  /usr/local/bin/npm
                  v16.15.1
                  v16.15.1
                  8.11.0
                  server
                  
                  

                  lt. deiner Anleitung habe ich nun:

                  sudo rm /usr/local/bin/node
                  sudo rm /usr/local/bin/npm

                  ausgefügrt und anschließend mit:

                  sudo apt install nodejs --reinstall

                  neu aufgebaut + Reboot. Nun schaut es wie folgt aus:

                  x86_64
                  /usr/bin/nodejs
                  /usr/bin/node
                  /usr/bin/npm
                  v16.15.1
                  v16.15.1
                  8.11.0
                  server
                  
                  

                  Der Fehler bei der Installation ist leider der gleiche geblieben. Siehe:

                   iobroker add heizoel auto --host Server --debug
                  NPM version: 8.11.0
                  Installing iobroker.heizoel@1.0.3... (System call)
                  npm WARN old lockfile
                  npm WARN old lockfile The package-lock.json file was created with an old version of npm,
                  npm WARN old lockfile so supplemental metadata must be fetched from the registry.
                  npm WARN old lockfile
                  npm WARN old lockfile This is a one-time fix-up, please be patient...
                  npm WARN old lockfile
                  npm WARN old lockfile Error: An unknown git error occurred
                  npm WARN old lockfile     at makeError (/usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
                  npm WARN old lockfile     at /usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
                  npm WARN old lockfile     at runMicrotasks (<anonymous>)
                  npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5)
                  npm WARN old lockfile  Could not fetch metadata for iobroker.boschebike@git+ssh://git@github.com/gaudes/ioBroker.boschebike.git#caab76421a131da61a7a8bbb8cd07bad28711e3e GitUnknownError: An unknown git error occurred
                  npm WARN old lockfile     at makeError (/usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
                  npm WARN old lockfile     at /usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
                  npm WARN old lockfile     at runMicrotasks (<anonymous>)
                  npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
                  npm WARN old lockfile   cmd: 'git',
                  npm WARN old lockfile   args: [
                  npm WARN old lockfile     '--no-replace-objects',
                  npm WARN old lockfile     'ls-remote',
                  npm WARN old lockfile     'ssh://git@github.com/gaudes/ioBroker.boschebike.git'
                  npm WARN old lockfile   ],
                  npm WARN old lockfile   code: 128,
                  npm WARN old lockfile   signal: null,
                  npm WARN old lockfile   stdout: '',
                  npm WARN old lockfile   stderr: 'git@github.com: Permission denied (publickey).\r\n' +
                  npm WARN old lockfile     'fatal: Konnte nicht vom Remote-Repository lesen.\n' +
                  npm WARN old lockfile     '\n' +
                  npm WARN old lockfile     'Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen\n' +
                  npm WARN old lockfile     'und das Repository existiert.\n'
                  npm WARN old lockfile }
                  
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Soldierofoc last edited by

                    @soldierofoc

                    Kannst du mir aber mal sagen wie du vorgegangen bist bei deiner Installation von nodjs16?

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      Soldierofoc @Thomas Braun last edited by Soldierofoc

                      @thomas-braun

                      cd /opt/iobroker
                      iobroker stop
                      curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
                      sudo apt-get install -y nodejs
                      curl -sL https://iobroker.net/fix.sh | bash -
                      iobroker start

                      und als es dann Probleme mit den Updates/Installation gab:

                      npm rebuild

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

                        @soldierofoc

                        Ich meine, wie es zur Installation in /usr/local/bin gekommen ist.
                        Das Paket aus nodesource kommt immer in den richtigen Pfad, die sind da nämlich fix drin.

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          Soldierofoc @Thomas Braun last edited by Soldierofoc

                          @thomas-braun
                          Ehrlich gesagt habe ich keine Ahnung wie es dazu gekommen ist. Bin damals beim Wechsel von 12.X auf 14.X gleich vorgegangen, ohne Probleme. Und nun das...

                          Habe gerade meine Statements durchgeschaut, welche ich abgesetzt habe. An einer Stelle hatte ich tatsächlich eine Abweichung zu meiner oben genannten Aussage!

                          Anstatt:

                          curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -

                          habe ich genutzt:

                          curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash - sudo apt install -y nodejs

                          Wobei ich nicht weiß (wie gesagt, bin hier kein Crack sondern gehe eher nach den Anleitungen vor), ob das Probleme bereiten könnte?

                          Wie gesagt besteht aber nun, trotz korrektem Pfad, das Problem weiterhin

                          Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Soldierofoc last edited by

                            @soldierofoc

                            Setz den Adapter heizoel mal ordentlich in ein Repo rein, nicht als github-Installation:

                            heizoel
                            github:	1.0.3
                            latest:	1.0.3 for 4 months
                            stable:	1.0.3 for 4 months
                            
                            1 Reply Last reply Reply Quote 0
                            • Homoran
                              Homoran Global Moderator Administrators @Soldierofoc last edited by

                              @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                              Bin damals beim Wechsel von 12.X auf 14.X gleich vorgegangen

                              dann war 12 vielleicht schon falsch?!?

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                Soldierofoc @Homoran last edited by

                                @homoran
                                Möchte hier nichts ausschließen, aber ich hatte mit Version 14 nun Monatelang keinerlei Probleme, auch nicht bei Updates und neuen Adaptern?

                                @thomas-braun
                                Ich weiß ich stelle mich zum Teil saublöd an. Aber wie füge ich heizoel dennin ein Repository ein? Ich war der Ansicht, dass dies bereits im Stable und Beta-Repository mit drin ist?

                                Homoran 1 Reply Last reply Reply Quote 0
                                • Homoran
                                  Homoran Global Moderator Administrators @Soldierofoc last edited by

                                  @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                                  dass dies bereits im Stable und Beta-Repository mit drin ist?

                                  dann mach darüber mal ein up oder downgrade

                                  @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                                  gehe eher nach den Anleitungen vor

                                  und duese Anleitung, fie zur Installation in /local/ führt, suchen wir!

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    Soldierofoc @Homoran last edited by Soldierofoc

                                    @homoran
                                    Ich möchte ja den Adapter überhaupt erst installieren, kein Up-/Downgrade? Und hier erhalte ich ebenfalls die oben gezeigte Fehlermeldung.

                                    Habe nun nochmals mein Vorgehen von heute Früh versucht zu rekonstruieren. Da ich nur die beiden Websites besucht habe, kommen diese nur als Anleitung in Frage:

                                    https://forum.iobroker.net/topic/44566/how-to-node-js-iobroker-richtig-updaten-2021-22-edition
                                    https://www.elzershark.com/forum/index.php?thread/110-upgrade-node-xx-xx-z-b-12-x-zu-node-14-x-für-iobroker/

                                    Einen Verweis auf /local/ finde ich hier nicht bzw. den Pfad.

                                    Kann es sein, dass falls ich:

                                    cd /opt/iobroker
                                    

                                    vergessen hätte, es zu dem Problem gekommen sein könnte?

                                    Trotz alledem - habt ihr einen Ansatz, wie ich die Kuh wieder vom Eis bekommen könnte?
                                    Die Pfad-Thematik habe ich ja, wie oben beschrieben, nun gefixt...?

                                    Homoran 1 Reply Last reply Reply Quote 0
                                    • Homoran
                                      Homoran Global Moderator Administrators @Soldierofoc last edited by

                                      @soldierofoc sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                                      Da ich nur die beiden Websites besucht habe, kommen diese nur als Anleitung in Frage:

                                      unsere ist ok, der Hai ist für nict ganz konforme Dinge (um es vorsichtig zu formulieren) bekannt

                                      S 1 Reply Last reply Reply Quote 1
                                      • S
                                        Soldierofoc @Homoran last edited by

                                        @homoran
                                        In Ordnung...wenn ich mir meine Statements durchschaue in der Console, dann sollte ich aber tatsächlich eure Anleitung herangezogen haben (als erste Möglichkeit).
                                        Die elzershark-Website bzw. Anleitung habe ich dann erst genutzt, als die oben genannte Thematik aufgetreten ist und ich bzgl. Fix/NPM Rebuild geschaut hatte.

                                        Wenn ich das (mit meinem Laien-Wissen) richtig deute, dann sollte doch "nur" noch npm Probleme machen bzw. package-log.json?
                                        Weshalb da noch der boschebike-Adapter drin auftaucht, welchen ich nur sehr kurz einmal installiert hatte, erschließt sich mir hier auch nicht wirklich?

                                        Installing iobroker.heizoel@1.0.3... (System call)
                                        npm WARN old lockfile
                                        npm WARN old lockfile The package-lock.json file was created with an old version of npm,
                                        npm WARN old lockfile so supplemental metadata must be fetched from the registry.
                                        npm WARN old lockfile
                                        npm WARN old lockfile This is a one-time fix-up, please be patient...
                                        npm WARN old lockfile
                                        npm WARN old lockfile Error: An unknown git error occurred
                                        npm WARN old lockfile     at makeError (/usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
                                        npm WARN old lockfile     at /usr/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
                                        npm WARN old lockfile     at runMicrotasks (<anonymous>)
                                        npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                        npm WARN old lockfile  Could not fetch metadata for iobroker.boschebike@git+ssh://git@github.com/gaudes/ioBroker.boschebike.git#caab76421a131da61a7a8bbb8cd07bad28711e3e GitUnknownError: An unknown git error occurred
                                        
                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active last edited by

                                          @homoran sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                                          unsere ist ok, der Hai ist für nict ganz konforme Dinge (um es vorsichtig zu formulieren) bekannt

                                          Wenn ich alleine schon die 3 und 4 Zeile aus dem Krampf lese...

                                          sudo npm cache verify
                                          sudo chown -R iobroker /opt/iobroker
                                          

                                          Das ist Schwachsinn im Quadrat. Da wundert es mich auch nicht weiter, wenn der Rest dann komplett in die Hose geht.

                                          1 Reply Last reply Reply Quote 1
                                          • S
                                            Soldierofoc last edited by

                                            @thomas-braun said in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:

                                            npm cache verify

                                            Dann habe ich schön in die Sche*** gegriffen.
                                            Habe ich irgendeine Möglichkeit das nun noch glatt zu ziehen?

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            937
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            errormeldung nodejs 16.15.1
                                            15
                                            169
                                            15718
                                            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