Beta-Test js-controller 2.2.x GitHub

Chaot · iobroker.2019-12-30.zip

@apollon77 Ich habe eine Fehlermeldung aus Proxmox.
Aber ich denke mal das hat nichts mit der Controler Version zu tun sondern mit dem Adapter:

host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.112	error	Caught by controller[2]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: TypeError: Cannot read property 'name' of undefined
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[1]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: TypeError: Cannot read property 'name' of undefined
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.105	error	Caught by controller[0]: TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.543	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.543	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.543	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.543	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.543	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.543	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.542	error	(684) uncaught exception: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.530	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.530	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.530	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.530	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.530	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.530	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.530	error	(684) uncaught exception: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.525	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.525	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.525	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.525	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.525	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.525	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.500	error	(684) uncaught exception: Cannot read property 'name' of undefined

Ansonsten alles ohne weitere Fehlermeldungen.
Version 2.2.4 seit gestern kurz nach Veröffentlichung

Einstein67

@apollon77 said in Beta-Test js-controller 2.2.x GitHub:

Bedeutet: Bitte Adapter Löschen neu testen. Sollte jetzt tun.

Bei mir immer noch das selbe verhalten wie bei 2.2.2

Nach dem (laut Log fehlerlosen) löschen von Adapter oder Instanz wird die dazugehörige Konfigseite geöffnet, und die Instanz ist immer noch da ...

crunchip

@Chaot kommt vom Adapter, kämpfe schon länger damit herum
https://github.com/iobroker-community-adapters/ioBroker.proxmox/issues/35

Chaot

@crunchip Danke. Das habe ich mir schon fast gedacht.
Vermutlich lag das daran das Proxmox genau zu der Zeit das Backup der PVE gemacht hat. Ich habe jetzt das Requestintevall mal von 30 auf 120 Sekunden gesetzt und werde mal abwarten ob es nochmal kommt.
Falls ja, werde ich mich mal bei dir anhängen.

lonsimbt

Die 2.2.4 läuft bei mir unauffällig keine Probleme oder Fehler im Log.

@crunchip : Die Probleme mit dem proxmox-Adapter (0.5.1) treten bei mir nicht auf.

Gruß Marco

Chaot

@apollon77 Mir fällt eine Besonderheit auf.
Ich habe an einem Raspi einen Touchscreen hängen der auf VIS zugreift.
Seit gestern fällt mir auf das der Browser zwischendurch einen Timeout beim Zugriff auf die Webseite bringt.
Das war vorher nicht so.

Kann ich von der Version auf 2.1.1 zurück mit dem vorhandenen Admin V3.7.5 oder geht dann der Admin flöten?

apollon77

@Chaot bitte issue bei proxmox anlegen. Kann es sein das du nen proxmox node rebooten hast?

apollon77

@Einstein67 wie sieht das log jetzt aus? Dann bitte issue reopen. Muss ich mir wohl ansehen

apollon77

@Chaot an sich sollte keine Änderung in der 2.2 zu so einem Effekt führen. Was genau sind timeouts? Der Browser redet mit dem Web Adapter. Gibts im log irgendwas?

Admin 3.7.5 sollte mit 2.1.1 tun soweit ich gelesen habe.

Einstein67

@apollon77

Die Logs sehen nicht so schlecht aus. Allerdings ist, im Vergleich zu den Logs von vor 2 Tagen, nun auch eine Fehlermeldung vorhanden: "ERROR: No packet manager found"

Web-GUI - Entfernen einer Instanz

$ ./iobroker del info.0
Delete adapter "info.0"
host.iob10b Counted 1 instances of info.0
host.iob10b Counted 1 devices of info.0
host.iob10b Counted 58 channels of info.0
ERROR: No packet manager found
host.iob10b Counted 294 states of info.0
host.iob10b Counted 14 states of system.adapter.info.0
host.iob10b Deleting 368 object(s).
host.iob10b: Only 200 objects left to be deleted.
process exited with code 0

Web-GUI - Adapter löschen

$ ./iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
ERROR: No packet manager found
host.iob10b Deleting 2 object(s).
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)
process exited with code 0

Danach öffnet sich in beiden Fällen die AdapterKonfiguration ....

Was mir noch aufgefallen ist: Das entfernen von Adaptern/Instanzen funktioniert mittels Konsole auch nur dann, wenn ioBroker vorher gestoppt wurde!

Konsole - ioBroker läuft. Instanz wird nicht gelöscht (nach starten ist nach einiger Zeit der Adapter auch wieder da)

iobroker@iob10b:~$ iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
host.iob10b Counted 1 devices of info
host.iob10b Counted 58 channels of info
host.iob10b Counted 294 states of info
host.iob10b Counted 14 states of system.adapter.info
host.iob10b Deleting 369 object(s).
No packet manager found
host.iob10b: Only 200 objects left to be deleted.
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)

Konsole - ioBroker gestoppt und trotz der Fehlermeldung am Ende, wird die Instanz und der Adapter entfernt.

iobroker@iob10b:~$ iobroker stop
iobroker@iob10b:~$ iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
host.iob10b Counted 1 devices of info
host.iob10b Counted 58 channels of info
host.iob10b Counted 294 states of info
host.iob10b Counted 14 states of system.adapter.info
No packet manager found
host.iob10b Deleting 369 object(s).
host.iob10b: Only 200 objects left to be deleted.
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)
 Cannot write files: /opt/iobroker/iobroker-data/files/info.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/info.admin/_data.json'

crunchip

ich bekomm´s immer noch nicht gebacken, den Js-controller zu installieren

root@IoBroker:~# cd /opt/iobroker
root@IoBroker:/opt/iobroker# iobroker stop
root@IoBroker:/opt/iobroker# npm install ioBroker/ioBroker.js-controller
[..................] / rollbackFailedOptional: verb npm-session cfd65c7e37e779d

darkiop

@crunchip

Versuche es mal mit sudo:

sudo -H -u iobroker npm install iobroker.js-controller

crunchip

@darkiop habe noch nie ein sudo verwendet:thinking_face:
aber es tut sich was:+1:

> iobroker.js-controller@2.1.1 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.11.3

> iobroker.js-controller@2.1.1 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

41 file(s) successfully synchronized with ioBroker storage.
Please DO NOT copy files manually into ioBroker storage directories!

The following notifications happened during sync:
- Added 40 Files in Directory "daswetter.admin"
- Ignoring Directory "icons-material-svg" because officially not created as meta object. Plea                       se remove directory!
- Ignoring Directory "icons-material-svg.admin" because officially not created as meta object                       . Please remove directory!
- Ignoring Directory "icons-mfd-svg" because officially not created as meta object. Please re                       move directory!
- Ignoring Directory "icons-mfd-svg.admin" because officially not created as meta object. Ple                       ase remove directory!
- Ignoring Directory "iobroker.admin.admin" because officially not created as meta object. Pl                       ease remove directory!
- Ignoring Directory "iobroker.discovery.admin" because officially not created as meta object                       . Please remove directory!
- Ignoring Directory "multicast.admin" because officially not created as meta object. Please                        remove directory!
- Ignoring Directory "sayit.0" because officially not created as meta object. Please remove d                       irectory!
- Added 1 Files in Directory "vis.0"

npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must instal                       l peer dependencies yourself.
npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must in                       stall peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted                        {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/os                       x-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor                       @1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@2.1.1
updated 8 packages in 71.234s

was mir aber nichts nützt, immer noch 2.1.1

Homer.J.

@crunchip wollte bei mir auch nicht, so ging es.

cd /opt/iobroker
iobroker stop
iobroker update
npm install ioBroker/ioBroker.js-controller

crunchip

@Homer-J auch das funktioniert nicht

crunchip

@crunchip wird immer besser

root@IoBroker:~# sudo -H -u iobroker npm install iobroker.js-controller
Error: EACCES: permission denied, scandir '/root'
TypeError: Cannot read property 'get' of undefined
    at errorMessage (/usr/lib/node_modules/npm/lib/utils/error-message.js:38:39)
    at errorHandler (/usr/lib/node_modules/npm/lib/utils/error-handler.js:201:13)
    at /usr/lib/node_modules/npm/bin/npm-cli.js:78:20
    at cb (/usr/lib/node_modules/npm/lib/npm.js:225:22)
    at /usr/lib/node_modules/npm/lib/npm.js:263:24
    at /usr/lib/node_modules/npm/lib/config/core.js:81:7
    at Array.forEach (<anonymous>)
    at /usr/lib/node_modules/npm/lib/config/core.js:80:13
    at f (/usr/lib/node_modules/npm/node_modules/once/once.js:25:25)
    at /usr/lib/node_modules/npm/lib/config/core.js:110:20
TypeError: Cannot read property 'loaded' of undefined
    at exit (/usr/lib/node_modules/npm/lib/utils/error-handler.js:97:27)
    at process.errorHandler (/usr/lib/node_modules/npm/lib/utils/error-handler.js:216:3)
    at process.emit (events.js:198:13)
    at emitPromiseRejectionWarnings (internal/process/promises.js:140:18)
    at process._tickCallback (internal/process/next_tick.js:69:34)
/usr/lib/node_modules/npm/lib/utils/error-handler.js:97
  var doExit = npm.config.loaded ? npm.config.get('_exit') : true
                          ^

TypeError: Cannot read property 'loaded' of undefined
    at exit (/usr/lib/node_modules/npm/lib/utils/error-handler.js:97:27)
    at process.errorHandler (/usr/lib/node_modules/npm/lib/utils/error-handler.js:216:3)
    at process.emit (events.js:198:13)
    at process._fatalException (internal/bootstrap/node.js:497:27)

? Offline

@crunchip du bist im falschen Verzeichnis, führ das mal in /opt/iobroker aus... :-)

crunchip

@ilovegym ja, ich war schon im richtigen Verzeichnis, hatte aber putty geschlossen, da es ja stehn bleibt und nicht weiterläuft, siehe :arrow_down: ,

@crunchip sagte in Beta-Test js-controller 2.2.x GitHub:

ich bekomm´s immer noch nicht gebacken, den Js-controller zu installieren

root@IoBroker:~# cd /opt/iobroker
root@IoBroker:/opt/iobroker# iobroker stop
root@IoBroker:/opt/iobroker# npm install ioBroker/ioBroker.js-controller
[..................] / rollbackFailedOptional: verb npm-session cfd65c7e37e779d

hatte nach erneutem öffnen von Putty, vergessen ins Verzeichnis zu wechseln. So der so, es geht weder mit/ohne sudo auch ein iobroker upload hilft nicht

crunchip

@crunchip
Befehl mit sudo gibt mir die 2.1.1, habs mal mit direkteingabe 2.2.4 probiert---No matching found und der übliche Befehl
npm install ioBroker/ioBroker.js-controller
bleibt stehn, siehe
@apollon77 hast du eine Idee?

root@IoBroker:/opt/iobroker# sudo -H -u iobroker npm install iobroker.js-controller

> iobroker.js-controller@2.1.1 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.11.3

> iobroker.js-controller@2.1.1 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first


The following notifications happened during sync:
- Ignoring Directory "icons-material-svg" because officially not created as meta object. Please remove directory!
- Ignoring Directory "icons-material-svg.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "icons-mfd-svg" because officially not created as meta object. Please remove directory!
- Ignoring Directory "icons-mfd-svg.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "iobroker.admin.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "iobroker.discovery.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "multicast.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "sayit.0" because officially not created as meta object. Please remove directory!

npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@2.1.1
updated 1 package in 70.729s
root@IoBroker:/opt/iobroker# npm install iobroker.js-controller@2.2.4
npm ERR! code ETARGET
npm ERR! notarget No matching version found for iobroker.js-controller@2.2.4.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2019-12-30T15_58_00_588Z-debug.log
root@IoBroker:/opt/iobroker# npm install ioBroker/ioBroker.js-controller
[..................] / rollbackFailedOptional: verb npm-session f2424b93be34e960

Homer.J.

@crunchip hab es eben nochmal bei mir durchlaufen lassen, kurz warten und es läuft.

cd /opt/iobroker
iobroker stop
apt update
apt upgrade
npm install ioBroker/ioBroker.js-controller

Community Forum

NEWS

Beta-Test js-controller 2.2.x GitHub

Support us

505

32.4k

81.4k

1.3m