[How-to] Node.js für ioBroker richtig updaten

Stabilostick

@zgadgeter
Dann wird wohl der zigbee-Stick von Deinem OS nicht richtig erkannt. Das hat aber weniger mit dem Node.js-Update zu tun. Welche HW? Welches Os? Was sagt der Befehl „lsusb“? Neuer Thread?

zgadgeter

@Stabilostick
Der Rechner ist ein Nuc. OS is unten.
Frage ist, kann ich das serial Verzeichnis von einem anderem Iobroker nehmen wo ich genau den selben stick nochmals habe, und der auch funktioniert? Da habe ich nach gesehen und habe den stick gefunden im serial Verzeichnis.

Linux ubuntu_iobroker 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 8087:0a2a Intel Corp.
Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 006: ID 0a5c:2198 Broadcom Corp. Bluetooth 3.0 Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Stabilostick

@zgadgeter sagte in [How-to] Node.js für ioBroker richtig updaten:

anderem Iobroker nehmen

Master-Slave iobroker-Installation.

Oder stecke den Stick in andere USB-Ports und schaue mit lsusb nach.

zgadgeter

@Stabilostick said in [How-to] Node.js für ioBroker richtig updaten:

@zgadgeter sagte in [How-to] Node.js für ioBroker richtig updaten:

anderem Iobroker nehmen

Master-Slave iobroker-Installation.

Oder stecke den Stick in andere USB-Ports und schaue mit lsusb nach.

Nee, kann ich nicht...bin zur Zeit 200 km weg, login via VPN...
Was ist mit dem Verzeichnis kopieren? Aber, in dem Verzeichnis "serial/byid" ist ein komisches file:

ioBroker-Pi:/dev/serial/by-id $ ls -l
insgesamt 0
lrwxrwxrwx 1 root root 13 Jul  8 22:17 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E208A1-if00 -> ../../ttyACM0

Laesst sich nicht kopieren?

Stabilostick

@zgadgeter
Das ist der zigbee-Stick. Und er wird nach /dev/ttyACM0 umgeleitet (siehe Ende der Zeile).

zgadgeter

@Stabilostick said in [How-to] Node.js für ioBroker richtig updaten:

@zgadgeter
Das ist der zigbee-Stick. Und er wird nach /dev/ttyACM0 umgeleitet (siehe Ende der Zeile).

ok, aber wie bekomme ich das ganze auf den anderen iobroker einfach kopiert?

Stabilostick

@zgadgeter
Du installierst auf den pi einen iobroker und machst ihn zum Slave deines NUC-ioBrokers. Stichwort „Multihost“.

Dann installiert du über den Admin des Masters auf dem Slave den zigbee-Adapter.

https://www.iobroker.net/#de/documentation/config/multihost.md

zgadgeter

@Stabilostick
Danke fuer die Hilfe, bin mir aber nicht sicher ob wir an einander vorbei reden:
NUC: das ist der Iobroker wo der Zigbee nicht mehr funktioniert nach dem update
Pi: das ist der zweite iobroker wo der zigbee (ein zweiter stick) funktioniert.
Ich dachte mir ich koennte das serial Verzeichnis einfach von dem Pi iobroker rubber kopieren zu dem Nuc iobroker, so das der erro (not found) nicht mehr da waere?

apollon77

Nein. Alles unter /dev wird vom Betriebssystem verwaltet! Wenn der usb Stick da nicht drin ist dann stimmt was nicht. Reboot kann helfen. Ggf musst du aber auch mal Stromlos machen bzw den Stick raus und rein. Natürlich per VPN blöd.

Das hat aber mit dem fix Skript oder dem Adapter nix zu tun.

zgadgeter

@apollon77 Hallo und danke. Versteh, danke fuer die Erklaerung...waere auch zu einfach gewesen :).
Ich probiere mal das jemand zuhause ein restart macht, bzw. den Stick mal raus nimmt.
Wenn das alles aber nicht funktioniert....gibt es da noch weitere Moeglichkeiten?
danke nochmals.

arteck

@zgadgeter da wird der port nicht weitergereicht wie ich es erkennen kann..
bzw. der iobroker user darf auf den port nicht zugreifen

wie währe es mit einem neuen Thread.. das hat nix mit dem Update von node zu tun

zgadgeter

@arteck said in [How-to] Node.js für ioBroker richtig updaten:

@zgadgeter da wird der port nicht weitergereicht wie ich es erkennen kann..
bzw. der iobroker user darf auf den port nicht zugreifen

wie währe es mit einem neuen Thread.. das hat nix mit dem Update von node zu tun

Naja, das ganze ist ja passiert direkt bei dem Update von node passiert. Ob es das Resultat von dem update war kann ich nicht sagen....nur Zufall?
Egal, ich mache ein neues Thread auf.

FYI, zigbee raus/rein stecken auch nichts gebracht.

smartboart

Hallo Gemeinde, kann mir einer sagen, wie ich diese Fehlermeldungen bei Adapter aktualisierungen reduzieren kann..System läuft unauffälig. Die Fehlerliste betrifft alle npm Installationen / Adapterupdates...

$ ./iobroker upgrade hm-rega
Update hm-rega from @2.4.0 to @2.4.1
NPM version: 6.9.0
npm install iobroker.hm-rega@2.4.1 --production --save --prefix "/opt/iobroker" (System call)
In file included from ../node_modules/nan/nan.h:82:0,                 from ../src/bufferutil.cc:16:
../node_modules/nan/nan_new.h: In function ‘v8::Local<T> NanIntern::To(v8::Handle<v8::Integer>) [with T = v8::Integer; v8::Handle<v8::Integer> = v8::Local<v8::Integer>]’:
../node_modules/nan/nan_new.h:29:66: warning: ‘v8::Local<v8::Integer> v8::Value::ToInteger() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 To<v8::Integer>(v8::Handle<v8::Integer> i) { return i->ToInteger(); }
                                                                  ^

In file included from ../src/validation.cc:7:0:/home/iobroker/.node-gyp/10.16.0/include/node/v8.h:10046:15: note: declared here
 Local<Object> Value::ToObject() const {
               ^~~~~

make: *** [Release/obj.target/validation/src/validation.o] Fehler 1
gyp
 
ERR!
 build error 
gyp
 ERR! 
stack
 Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262: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.182-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/utf-8-validategyp 
ERR! node -v v10.16.0gyp ERR! 
node-gyp -v v3.8.0gyp
 ERR! not ok 
npm
 
WARN
 babel-eslint@5.0.4 requires a peer of eslint@<2.3.0 but none is installed. You must install peer dependencies yourself.
npm
 
WARN
 xmlhttprequest-ts@1.0.1 requires a peer of @angular/common@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
npm 
WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/core@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional
 SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bufferutil@1.1.0 (node_modules/bufferutil):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bufferutil@1.1.0 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: utf-8-validate@1.1.0 (node_modules/utf-8-validate):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: utf-8-validate@1.1.0 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1


npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.hm-rega"
npm
 
notice
 created a lockfile as package-lock.json. You should commit this file.
got /opt/iobroker/node_modules/iobroker.hm-rega/admin
upload [3] hm-rega.admin /opt/iobroker/node_modules/iobroker.hm-rega/admin/words.js words.js application/javascript
Update "system.adapter.hm-rega.0"
upload [2] hm-rega.admin /opt/iobroker/node_modules/iobroker.hm-rega/admin/index_m.html index_m.html text/html
upload [1] hm-rega.admin /opt/iobroker/node_modules/iobroker.hm-rega/admin/index.html index.html text/html
upload [0] hm-rega.admin /opt/iobroker/node_modules/iobroker.hm-rega/admin/homematic.png homematic.png image/png
Adapter "hm-rega" updated
process exited with code 0

marcuskl

Beimir klappt alles nur wen ich node -v eingebe kommt immernoch Node js 8.x ?

root@iobroker:~# node -v
v8.16.0
root@iobroker:~# nodejs -v
v10.16.0
root@iobroker:~#

Homoran

@marcuskl sagte in [How-to] Node.js für ioBroker richtig updaten:

Beimir klappt alles nur wen ich node -v eingebe kommt immernoch Node js 8.x ?

Dann hast du -warum auch immer (einmal einen Befehl im falschen Verzeichnis ausgeführt...)- zwei node installationen parallel laufen.

Das wird zu Problemen führen

marcuskl

@Homoran was mache ich nun ?

marcuskl

Ich habe damal die node 6 mit dem Befehl

Sudo n 8.12.0

geupdatet.

Liegt da der Fehler ?

Homoran

@marcuskl sagte in [How-to] Node.js für ioBroker richtig updaten:

was mache ich nun ?

Dazu bin ich nicht fit genug.

@paul53 hatte bereits mehrfach das procedere zum Auffinden der Versionen und Entfernen der falschen hier im Forum gepostet.

Da musst du mal suchen

FuLLHDvs480p

Hallo,

habe folgendes Problem:

rock64@rock64:/opt/iobroker$ iobroker stop
rock64@rock64:/opt/iobroker$ curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -

## Installing the NodeSource Node.js 10.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu xenial InRelease
Get:3 http://deb.ayufan.eu/orgs/ayufan-rock64/releases  InRelease [1339 B]
Ign:4 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Get:5 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:6 https://deb.nodesource.com/node_10.x stretch InRelease
Hit:7 http://cdn-fastly.deb.debian.org/debian stretch Release
Fetched 92.4 kB in 2s (39.7 kB/s)
Reading package lists... Done

## Confirming "stretch" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/stretch/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK

## Creating apt sources list file for the NodeSource Node.js 10.x repo...

+ echo 'deb https://deb.nodesource.com/node_10.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_10.x stretch main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu xenial InRelease
Ign:3 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Get:5 http://deb.ayufan.eu/orgs/ayufan-rock64/releases  InRelease [1339 B]
Hit:6 http://cdn-fastly.deb.debian.org/debian stretch Release
Hit:7 https://deb.nodesource.com/node_10.x stretch InRelease
Fetched 1339 B in 2s (583 B/s)
Reading package lists... Done

## Run `sudo apt-get install -y nodejs` to install Node.js 10.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
     echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn


rock64@rock64:/opt/iobroker$ sudo apt-get install -y nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (10.16.0-1nodesource1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
rock64@rock64:/opt/iobroker$ node -v
v10.16.0
rock64@rock64:/opt/iobroker$ curl -sL https://iobroker.net/fix.sh | bash -

==========================================================================

    Welcome to the ioBroker installation fixer!
    Script version: 2019-07-21

    You might need to enter your password a couple of times.

==========================================================================


==========================================================================
    Installing prerequisites (1/3)
==========================================================================


==========================================================================
    Checking ioBroker user and directory permissions (2/3)
==========================================================================

Created /etc/sudoers.d/iobroker
Fixing directory permissions...

==========================================================================
    Checking autostart (3/3)
==========================================================================

Enabling autostart...
Autostart enabled!

==========================================================================

    Your installation was fixed successfully
    Run iobroker start to start ioBroker again!

==========================================================================

rock64@rock64:/opt/iobroker$ npm rebuild

> @abandonware/bluetooth-hci-socket@0.5.3-1 preinstall /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket
> npm install node-pre-gyp

npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules
npm ERR! path /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp'
npm ERR!  { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp']
npm ERR!   stack:
npm ERR!    'Error: EACCES: permission denied, access \'/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path:
npm ERR!    '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/node-pre-gyp' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rock64/.npm/_logs/2019-07-26T09_47_03_405Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 243
npm ERR! @abandonware/bluetooth-hci-socket@0.5.3-1 preinstall: `npm install node-pre-gyp`
npm ERR! Exit status 243
npm ERR!
npm ERR! Failed at the @abandonware/bluetooth-hci-socket@0.5.3-1 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rock64/.npm/_logs/2019-07-26T09_47_03_647Z-debug.log
rock64@rock64:/opt/iobroker$ npm install @abandonware/bluetooth-hci-socket
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/abbrev
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/ansi-regex
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/aproba
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/balanced-match
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/chownr
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/code-point-at
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/concat-map
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/brace-expansion
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/console-control-strings
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/core-util-is
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/deep-extend
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/delegates
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/detect-libc
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/fs.realpath
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/has-unicode
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/inherits
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/ini
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/isarray
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/minimatch
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/ignore-walk
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/minimist
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/mkdirp
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/needle/node_modules/debug
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/npm-bundled
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/npm-packlist
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/number-is-nan
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/is-fullwidth-code-point
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/object-assign
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/os-homedir
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/os-tmpdir
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/osenv
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/nopt
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/path-is-absolute
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/process-nextick-args
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/rc/node_modules/minimist
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/safe-buffer
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/safer-buffer
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/iconv-lite
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/sax
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/needle
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/set-blocking
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/signal-exit
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/string_decoder
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/strip-ansi
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/string-width
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/strip-json-comments
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/rc
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/util-deprecate
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/readable-stream
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/are-we-there-yet
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/wide-align
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/gauge
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/npmlog
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/wrappy
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/once
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/inflight
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/glob
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/rimraf
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/yallist
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/minipass
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/fs-minipass
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/minizlib
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/tar
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/needle/node_modules
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/rc/node_modules
npm WARN ELOOP: too many symbolic links encountered, stat '/opt/iobroker/node_modules/bluetooth-hci-socket'
npm WARN ELOOP: too many symbolic links encountered, stat '/opt/iobroker/node_modules/iobroker.type-detector'
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket/package.json'

npm ERR! path /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket'
npm ERR!  { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket']
npm ERR!   stack:
npm ERR!    'Error: EACCES: permission denied, access \'/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path:
npm ERR!    '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rock64/.npm/_logs/2019-07-26T09_58_41_378Z-debug.log
rock64@rock64:/opt/iobroker$

Fixer Script habe ich laufen lassen,
Radar2 und Ble vorher komplett gelöscht.
Auch die Neuinstallation von bluetooth-hci-socket schlägt fehl.
js-controller: 1.5.14

Jemand eine Idee?

AlCalzone

@FuLLHDvs480p Eigentlich dürfte das nicht passieren, aber probier mal im Ordner /opt/iobroker folgendes:

sudo -H -u iobroker npm install @abandonware/bluetooth-hci-socket

um die Installation als Benutzer iobroker auszuführen, der dort Schreibrechte haben müsste.

Community Forum

NEWS

[How-to] Node.js für ioBroker richtig updaten

Support us

454

32.4k

81.4k

1.3m