Beta Test js-controller 3.0.x auf GitHub

[deta]

Hallo,
hab gerade auch das Update auf 3.0 gemacht, funktioniert zwar alles, habe dennoch ein paar Fehler bei der Install gehabt, vielleicht könnt Ihr mir da bitte mal helfen, diese zu beseitigen.

Hier das Install..

root@rock:/opt/iobroker# npm install ioBroker/ioBroker.js-controller
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

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

NPM version: 6.14.4

> sharp@0.24.1 install /opt/iobroker/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.0
info sharp Attempting to build from source via node-gyp but this may fail due to the above error
info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies
make: Entering directory '/opt/iobroker/node_modules/sharp/build'
  TOUCH Release/obj.target/libvips-cpp.stamp
  CXX(target) Release/obj.target/sharp/src/common.o
In file included from ../src/common.cc:25:0:
/usr/include/vips/vips8:35:25: fatal error: glib-object.h: No such file or directory
 #include <glib-object.h>
                         ^
compilation terminated.
sharp.target.mk:127: recipe for target 'Release/obj.target/sharp/src/common.o' failed
make: *** [Release/obj.target/sharp/src/common.o] Error 1
make: Leaving directory '/opt/iobroker/node_modules/sharp/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:191:23)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.4.192-rockchip64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/sharp
gyp ERR! node -v v10.20.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 

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

object system.certificates updated
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/@abandonware/.noble.DELETE/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/unix-dgram/package.json'
npm WARN bl@0.7.0 requires a peer of stream-browserify@* 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":"arm64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.24.1 (node_modules/sharp):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.24.1 install: `(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ iobroker.js-controller@3.0.6
updated 1 package and audited 31342 packages in 145.011s

16 packages are looking for funding
  run `npm fund` for details

found 171 vulnerabilities (167 low, 1 moderate, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Das bekomme ich nicht in Griff..

Danke schon mal

cu Deta

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

[Dr. Bakterius]

@foxriver76 sagte in Beta Test js-controller 3.0.x auf GitHub:

@Dr-Bakterius pushover brauchst du die Version von GitHub 1.2.4

Danke, schon gemerkt.

[Homer.J.]

@foxriver76 läuft wieder.

[foxriver76]

tr064 schaue ich dann an ob Controller was kaputt gemacht hat oder tr-064 was net passt.

[AlCalzone]

@deta sagte in Beta Test js-controller 3.0.x auf GitHub:

+ iobroker.js-controller@3.0.6
updated 1 package

Alles gut!

[BBTown]

Sodele, ich habe die v3.0.6 auch einmal zusammen mit node.js v12.16.2 installiert.
Die Installation verlief fehlerfrei, alle Adapter sind grün!

In den Logs habe ich zum Einen die hier bereits erwähnte Warnung
adapter.objects.getObjectView is deprecated ...
Bei mir kommen diese wiederkehrend vom iot.0 und vom web.0 Adapter sowie einmalig vom admin.0

Vom broadlink2.0 Adapter erhalte ich wiederholt die Warnung:
State value to set is invalid for broadlink2.0.RMproWohnzimmer.Temperature: The state contains the forbidden properties user!

Beim Start des iot.0 Adapter kommen dann noch diese Meldungen:

iot.0	2020-04-12 12:29:17.324	warn	(2413) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
iot.0	2020-04-12 12:29:17.281	warn	(2413) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
iot.0	2020-04-12 12:29:17.143	warn	(2413) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
iot.0	2020-04-12 12:29:16.779	warn	(2413) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
iot.0	2020-04-12 12:29:16.779	warn	(2413) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
iot.0	2020-04-12 12:29:16.771	warn	the module (for instance, using `npm rebuild` or `npm install`).
iot.0	2020-04-12 12:29:16.771	warn	NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
iot.0	2020-04-12 12:29:16.771	warn	NODE_MODULE_VERSION 64. This version of Node.js requires
iot.0	2020-04-12 12:29:16.771	warn	was compiled against a different Node.js version using
iot.0	2020-04-12 12:29:16.771	warn	(2413) Cannot initialize getImage: Error: The module '/opt/iobroker/node_modules/canvas/build/Release/canvas.node'

Ach ja, schöne Ostern an alle

[deta]

@AlCalzone Und die Fehler? mit dem RR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.0
Bekomme ich nicht in Griff...

Welches ist eigentlich jetzt die aktuelle richtige lauffähige Version vom tr-064 Adapter? Link?
Der Spinnt bei mir noch.

Und Radar2 bringt im Log Fehler jetzt.

[AlCalzone]

@deta sagte in Beta Test js-controller 3.0.x auf GitHub:

Und die Fehler? mit dem RR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.0
Bekomme ich nicht in Griff...

Für welchen Adapter wird das denn benötigt? Der Controller braucht die nicht, deshalb auch die Erfolgsmeldung am Ende. Hat also mit JS-Controller 3.x nichts zu tun.

[deta]

@AlCalzone Weis ich leider nicht, der Fehler kommt fast bei jeden Update von Adaptern.

[AlCalzone]

@deta Einen Hinweis könnte folgender Befehl bieten:

cd /opt/iobroker
npm ls sharp

[deta]

ok das kommt

iobroker.inst@2.0.2 /opt/iobroker
└─┬ iobroker.iot@1.4.2
  └── UNMET OPTIONAL DEPENDENCY sharp@~0.24.1

Wohl vom iot Adapter Mal da fragen danke oder hast du ne Idee?

[AlCalzone]

@deta Ne frag ruhig mal in dem Kontext nach.

[apollon77]

@Kueppert dann müssten die Verzeichnis rechte Schuld sein. Aber support für root Systeme ist so ne Sache

[apollon77]

@Dr-Bakterius sagte in Beta Test js-controller 3.0.x auf GitHub:

Der rflink-Adapter konnte keinen Serial-Port finden. Auch eine Neuinstallation des Adapters hat nicht geholfen. Dieses Problem konnte ich dann durch folgenden Befehl im iobroker-Verzeichnis lösen (hat halt dann rund 15 Minuten gedauert alle Adapter neu zu installieren):

Ja ich fürchte hier greif das Auto-Rebuild nicht weil das nicht verfügbare Serialport im ersten schritt für Admin abgefangen wird und somit keine Exception fliegt. Was hat das Log genau gesagt?

[apollon77]

@BBTown Und tut bewi iot was nicht trotz der meldung? Wenn Du den Adapter beendest sollte er versuchen zu rebuilden. mach mal ... Bzw mehr log bitte

[apollon77]

@deta sagte in Beta Test js-controller 3.0.x auf GitHub:

libvips

Wir AlCalzone schon sagt nix vom Controller ... Aber die Meldungbesagt das Du ein Linux Paket in einer minimalen Version brauchst ... versuch mal "apt install libvips-dev" ... kommt da eine >=8.9.0 ?

[apollon77]

Hey All,

habe gerade mal alles gecheckt was seit heute früh auf kam.

Am Ende ist es:

• tr-064 wo @foxriver76 gerade schaut
• serialport bei rflink wo ggf. die Rebuild-Exception nicht fliegt und daher kein Auto Rebuild passiert
• iot mit auch nem Warn wegen nicht rebuild Paketen ... da sollte man mal einen Neustart des Adapters versuchen ob er das dann erkennt und rebuildet.
• pushover 1.2.4 muss noch ins Latest

Hab ich alles erwischt?

[deta]

@apollon77 sagte in Beta Test js-controller 3.0.x auf GitHub:

@deta sagte in Beta Test js-controller 3.0.x auf GitHub:

libvips

Wir AlCalzone schon sagt nix vom Controller ... Aber die Meldungbesagt das Du ein Linux Paket in einer minimalen Version brauchst ... versuch mal "apt install libvips-dev" ... kommt da eine >=8.9.0 ?

Hab ich schon, ist installiert.

root@rock:~# apt install libvips-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
libvips-dev is already the newest version (8.4.5-1+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Aber bei kommt

root@rock:~# vips -v
Could not find the database of available applications, run update-command-not-found as root to fix this
vips: command not found

root@rock:~# sudo update-command-not-found 
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_contrib_Contents-arm64.lz4 ... . done
I: Writing data for dl.yarnpkg.com_debian_dists_stable_main_Contents-armhf.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_stretch-utils_Contents-armhf.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_main_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_contrib_Contents-armhf.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_main_Contents-armhf.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_stretch-desktop_Contents-armhf.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_non-free_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_contrib_Contents-armhf.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_main_Contents-armhf.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-updates_main_Contents-arm64.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_stretch-utils_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_non-free_Contents-arm64.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_main_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_non-free_Contents-armhf.lz4 ... . done
I: Writing data for mirrors.dotsrc.org_armbian-apt_dists_stretch_stretch-desktop_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-updates_main_Contents-armhf.lz4 ... . done
I: Writing data for dl.yarnpkg.com_debian_dists_stable_main_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_non-free_Contents-armhf.lz4 ... . done
I: Writing data for dl.yarnpkg.com_debian_dists_stable_main_Contents-all.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_main_Contents-arm64.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch-backports_main_Contents-armhf.lz4 ... . done
I: Writing data for httpredir.debian.org_debian_dists_stretch_contrib_Contents-arm64.lz4 ... . done
root@rock:~# vips -v
The program 'vips' is currently not installed.  You can install it by typing:
apt install libvips-tools
vips: command not found
root@rock:~# apt install libvips-tools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Recommended packages:
  nip2 libvips-doc
The following NEW packages will be installed:
  libvips-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 92,3 kB of archives.
After this operation, 198 kB of additional disk space will be used.
Get:1 http://httpredir.debian.org/debian stretch/main arm64 libvips-tools arm64 8.4.5-1+deb9u1 [92,3 kB]
Fetched 92,3 kB in 0s (391 kB/s)   
Selecting previously unselected package libvips-tools.
(Reading database ... 53112 files and directories currently installed.)
Preparing to unpack .../libvips-tools_8.4.5-1+deb9u1_arm64.deb ...
Unpacking libvips-tools (8.4.5-1+deb9u1) ...
Setting up libvips-tools (8.4.5-1+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
root@rock:~# vips -v
vips-8.4.5-Fri Jan 18 18:15:36 UTC 2019
root@rock:~# 

gelöst, mal sehen beim nächsten Update

[deta]

Der TR-064 Adapter macht bei mir dieses Problem.

tr-064-community.0	2020-04-12 15:00:22.767	info	(29197) Terminated (NO_ERROR): Without reason
tr-064-community.0	2020-04-12 15:00:22.763	info	(29197) terminating
tr-064-community.0	2020-04-12 15:00:22.678	error	(29197) TypeError: Cannot read property 'getState' of undefined at checkIfUpdated (/opt/iobroker/node_modules/iobroker.tr-064-community/lib/soef.js:1006:20) at Object.options.ready (/opt/iobro
tr-064-community.0	2020-04-12 15:00:22.671	error	(29197) uncaught exception: Cannot read property 'getState' of undefined
tr-064-community.0	2020-04-12 15:00:22.597	info	(29197) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.tr-064-community, node: v10.20.0, js-controller: 3.0.6
tr-064-community.0	2020-04-12 14:59:35.065	info	(27910) Terminated (NO_ERROR): Without reason
tr-064-community.0	2020-04-12 14:59:35.061	info	(27910) terminating
tr-064-community.0	2020-04-12 14:59:34.989	error	at process._tickCallback (internal/process/next_tick.js:68:7)
tr-064-community.0	2020-04-12 14:59:34.989	error	at Promise.all.then (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:7986:76)
tr-064-community.0	2020-04-12 14:59:34.989	error	at Object.options.ready (/opt/iobroker/node_modules/iobroker.tr-064-community/lib/soef.js:1120:13)
tr-064-community.0	2020-04-12 14:59:34.989	error	at checkIfUpdated (/opt/iobroker/node_modules/iobroker.tr-064-community/lib/soef.js:1006:20)
tr-064-community.0	2020-04-12 14:59:34.989	error	(27910) TypeError: Cannot read property 'getState' of undefined
tr-064-community.0	2020-04-12 14:59:34.983	error	(27910) uncaught exception: Cannot read property 'getState' of undefined
tr-064-community.0	2020-04-12 14:59:34.925	info	(27910) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.tr-064-community, node: v10.20.0, js-controller: 3.0.6

[apollon77]

@deta naja. Community Version wird nicht weiter gepflegt. Bitte auf originalen wechseln mit 3.1.4