Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Fehlermeldung ERROR: Process exited with code 25

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Fehlermeldung ERROR: Process exited with code 25

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Denzel 0 last edited by

      Hallo, ich habe das Problem, dass ich beim Update von Adaptern aus der Adminseite den oben genannten Fehler erhalte.
      Das sieht dann wie folgt aus:

      $ iobroker upgrade vis-icontwo@0.98.0

      Update vis-icontwo from @0.97.3 to @0.98.0

      NPM version: 9.8.1

      Installing iobroker.vis-icontwo@0.98.0... (System call)

      npm ERR! code EBUSYnpm ERR! syscall renamenpm ERR! path C:\ioBroker\node_modules\iobroker.adminnpm ERR! dest C:\ioBroker\node_modules.iobroker.admin-GBn0lhRQnpm ERR! errno -4082npm ERR! EBUSY: resource busy or locked, rename 'C:\ioBroker\node_modules\iobroker.admin' -> 'C:\ioBroker\node_modules.iobroker.admin-GBn0lhRQ'npm ERR! A complete log of this run can be found in: C:\Windows\system32\config\systemprofile\AppData\Local\npm-cache_logs\2023-11-26T10_42_52_881Z-debug-0.log

      host.ioBroker Cannot install iobroker.vis-icontwo@0.98.0: 4294963214

      ERROR: Process exited with code 25

      Führe ich einen npm audit fix --force Befehl in der Console aus erhalte ich folgende Mitteilung:

      C:\ioBroker>npm audit fix --force
      npm WARN using --force Recommended protections disabled.
      npm WARN audit fix semver@5.3.0 node_modules/node-red-node-email/node_modules/semver
      npm WARN audit fix semver@5.3.0 is a bundled dependency of
      npm WARN audit fix semver@5.3.0 node-red-node-email@1.18.4 at node_modules/node-red-node-email
      npm WARN audit fix semver@5.3.0 It cannot be fixed automatically.
      npm WARN audit fix semver@5.3.0 Check for updates to the node-red-node-email package.
      npm WARN audit fix utf7@1.0.2 node_modules/node-red-node-email/node_modules/utf7
      npm WARN audit fix utf7@1.0.2 is a bundled dependency of
      npm WARN audit fix utf7@1.0.2 node-red-node-email@1.18.4 at node_modules/node-red-node-email
      npm WARN audit fix utf7@1.0.2 It cannot be fixed automatically.
      npm WARN audit fix utf7@1.0.2 Check for updates to the node-red-node-email package.
      npm WARN audit fix imap@0.8.19 node_modules/node-red-node-email/node_modules/imap
      npm WARN audit fix imap@0.8.19 is a bundled dependency of
      npm WARN audit fix imap@0.8.19 node-red-node-email@1.18.4 at node_modules/node-red-node-email
      npm WARN audit fix imap@0.8.19 It cannot be fixed automatically.
      npm WARN audit fix imap@0.8.19 Check for updates to the node-red-node-email package.
      npm WARN audit No fix available for iobroker.fronius-solarweb@*
      npm WARN audit Updating iobroker.homeconnect to 0.0.37, which is a SemVer major change.
      npm WARN audit Updating iobroker.ical to 1.13.0, which is a SemVer major change.
      npm WARN audit Updating iobroker.smartgarden to 0.5.0, which is a SemVer major change.
      npm WARN audit No fix available for iobroker.terminal@*
      npm WARN audit Updating iobroker.backitup to 0.2.7, which is a SemVer major change.
      npm WARN audit No fix available for iobroker.javascript@*
      npm WARN audit No fix available for iobroker.vw-connect@*
      npm WARN audit Updating iobroker.homee to 1.0.7, which is a SemVer major change.
      npm WARN audit Updating iobroker.bydbatt to 0.0.1, which is a SemVer major change.
      npm WARN audit Updating iobroker.hue to 0.6.0, which is a SemVer major change.
      npm WARN audit Updating iobroker.discovery to 0.4.0, which is a SemVer major change.
      npm WARN audit Updating iobroker.socketio to 6.5.8, which is a SemVer major change.
      npm WARN audit Updating iobroker.tuya to 2.0.4, which is a SemVer major change.
      npm WARN audit Updating iobroker.node-red to 1.2.0, which is a SemVer major change.
      npm WARN audit Updating iobroker.harmony to 1.1.0, which is a SemVer major change.
      npm WARN audit No fix available for iobroker.meross@*
      npm WARN audit Updating iobroker.js-controller to 1.5.3, which is a SemVer major change.
      npm WARN audit Updating iobroker.web to 5.2.2, which is a SemVer major change.
      npm WARN audit No fix available for iobroker.vis-inventwo@*
      npm WARN audit No fix available for iobroker.daikin-cloud@*
      npm ERR! code EBUSY
      npm ERR! syscall rename
      npm ERR! path C:\ioBroker\node_modules\iobroker.admin
      npm ERR! dest C:\ioBroker\node_modules.iobroker.admin-GBn0lhRQ
      npm ERR! errno -4082
      npm ERR! EBUSY: resource busy or locked, rename 'C:\ioBroker\node_modules\iobroker.admin' -> 'C:\ioBroker\node_modules.iobroker.admin-GBn0lhRQ'

      npm ERR! A complete log of this run can be found in: C:\Users\Andreas\AppData\Local\npm-cache_logs\2023-11-26T08_29_38_633Z-debug-0.log

      Habt Ihr eine Idee?

      Gruß Andreas

      Systemdata Windows 11
      Hardwaresystem: NUC
      Arbeitsspeicher: 24GB
      Festplattenart: SSD
      Betriebssystem: Windows
      Nodejs-Version: v18.18.2
      NPM-Version: 9.8.1
      Installationsart: Skript
      Image genutzt: nein
      Jensen 1 Reply Last reply Reply Quote 0
      • Jensen
        Jensen @Denzel 0 last edited by

        @denzel-0
        Wie sah' die Lösung des Problems aus?

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

          @jensen

          Jedenfalls NICHT

          Führe ich einen npm audit fix --force

          Finger weg von npm audit fix, insbesondere in der Kombination mit --force ist das tödlich.

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

            @thomas-braun
            Ist ja Windows, nicht so dein Ding, ich weiß, aber wo soll ich anfangen mit suchen?

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

              @jensen

              Lass es unter Linux laufen.
              Da wäre es vermutlich mit einem

              iob fix
              

              aus der Welt geschafft.

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

              Support us

              ioBroker
              Community Adapters
              Donate

              610
              Online

              31.6k
              Users

              79.6k
              Topics

              1.3m
              Posts

              3
              5
              318
              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