Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[robsdobs]

Hallo,

ich hatte IO Broker am laufen. Einige Pakete gab es in einer neuen Version. Ein Update auf der Weboberflache funktionierte irgendwie nicht.

Da habe ich "iobroker upgrade" ausgeführt um diese zu aktualisieren. Das ist mit einem Fehler abgebrochen und jetzt kommt folgendes:

root@GD-Server:/opt/iobroker# iobroker upgrade
module.js:340
    throw err;
          ^
Error: Cannot find module '/media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3

(Ich muss dazu sagen, bei mir ist das Verzeichniss "/opt/iobroker" (USB Stick) ein link auf "/media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker" (Festplatte).)

Also irgendwie ist die Installation zerschossen. Also habe ich versucht ioBroker neu zu installieren, was mir leider auch nicht gelingt.

root@GD-Server:/opt/iobroker# sudo npm install iobroker --unsafe-perm
npm ERR! not a package /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
npm ERR! addLocal Could not install /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
npm ERR! Linux 3.16.0-0.bpo.4-amd64
npm ERR! argv "node" "/usr/bin/npm" "install" "iobroker" "--unsafe-perm"
npm ERR! node v0.10.29
npm ERR! npm  v3.10.6
npm ERR! path /tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! enoent ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
npm ERR! enoent ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent 
npm ERR! Please include the following file with any support request:
npm ERR!     /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/npm-debug.log

Die Datei npm-debug.log beinhaltet folgendes:

! ````
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/bin/npm', 'install', 'iobroker', '--unsafe-perm' ]
2 info using npm@3.10.6
3 info using node@v0.10.29
4 verbose node symlink /usr/bin/node
5 silly loadCurrentTree Starting
6 silly install loadCurrentTree
7 silly install readLocalPackageData
8 silly fetchPackageMetaData iobroker
9 silly fetchOtherPackageData iobroker
10 silly cache add args [ 'iobroker', null ]
11 verbose cache add spec iobroker
12 silly cache add parsed spec { raw: 'iobroker',
12 silly cache add scope: null,
12 silly cache add escapedName: 'iobroker',
12 silly cache add name: null,
12 silly cache add rawSpec: 'iobroker',
12 silly cache add spec: '/media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker',
12 silly cache add type: 'local' }
13 silly addLocalTarball shasum (computed) 172d89ea6df6ab508c7b69dc0540b583db07e40c
14 verbose addTmpTarball /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker not in flight; adding
15 verbose correctMkdir /root/.npm correctMkdir not in flight; initializing
16 verbose addTmpTarball validating metadata from /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
17 verbose tar unpack /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
18 verbose tar unpacking to /tmp/npm-8408-d9447edb/unpack-d9997cf2
19 silly gentlyRm /tmp/npm-8408-d9447edb/unpack-d9997cf2 is being purged
20 verbose gentlyRm don't care about contents; nuking /tmp/npm-8408-d9447edb/unpack-d9997cf2
21 silly gunzTarPerm modes [ '755', '644' ]
22 error not a package /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
23 error addLocal Could not install /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker/iobroker
24 silly fetchPackageMetaData Error: ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
24 silly fetchPackageMetaData error for iobroker { [Error: ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json']
24 silly fetchPackageMetaData errno: 34,
24 silly fetchPackageMetaData code: 'ENOENT',
24 silly fetchPackageMetaData path: '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json' }
25 silly rollbackFailedOptional Starting
26 silly rollbackFailedOptional Finishing
27 silly runTopLevelLifecycles Starting
28 silly runTopLevelLifecycles Finishing
29 silly install printInstalled
30 verbose stack Error: ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
31 verbose cwd /media/1c31537f-0f75-428d-9228-7b54b469086c/iobroker
32 error Linux 3.16.0-0.bpo.4-amd64
33 error argv "node" "/usr/bin/npm" "install" "iobroker" "--unsafe-perm"
34 error node v0.10.29
35 error npm v3.10.6
36 error path /tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json
37 error code ENOENT
38 error errno 34
39 error enoent ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
40 error enoent ENOENT, open '/tmp/npm-8408-d9447edb/unpack-d9997cf2/package.json'
40 error enoent This is most likely not a problem with npm itself
40 error enoent and is related to npm not being able to find a file.
41 verbose exit [ 34, true ]

Das System ist ein x86 mit Openmediafault (debian wheezy).

Jetzt komme ich leider nicht weiter. Was kann ich machen?

Danke & Gruß

Robert

[Homoran]

Ich denke du hast eine korrupte Datei.

Bei deinen verbogenen Pfaden kann ich dir nicht helfen, aber mach mal dementsprechend

cd /opt/iobroker
iobroker stop
npm cache clean
npm install iobroker.js-controller
iobroker start

Viel Glück

Rainer

[robsdobs]

Danke, jetzt läuft wieder alles!

Auch die Updates über das Admin Gui funktionieren.

Besten Dank!