iobroker startet nicht nach node-js Update 16.18.1

Thomas Braun

Zunächst mal ordentlich mit dem System agieren.
Leg dir einen User für das tägliche Geschäft an.

Zu Fehler 25: Ist oben angepinnt.

KaFaBe

@thomas-braun sagte in iobroker startet nicht nach node-js Update 16.18.1:

@kafabe

Zunächst mal ordentlich mit dem System agieren.
Leg dir einen User für das tägliche Geschäft an.

Zu Fehler 25: Ist oben angepinnt.

Ok, werde einen normalen User anlegen.

Hatte versucht Fehler 25 zu beheben. Scheinbar ohne Erfolg.
Oder liegt es am Benutzer?

root@odroid:/opt/iobroker/node_modules# for i in $(find /opt/iobroker/node_m                                                                                                                         odules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf $                                                                                                                         {i%%/}; done
root@odroid:/opt/iobroker/node_modules# cd
root@odroid:~# iobroker start
root@odroid:~# iobroker status
node:internal/modules/cjs/loader:988
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller                                                                                                                         /iobroker.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:98                                                                                                                         5:15)
    at Function.Module._load (node:internal/modules/cjs/loader:833:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/ru                                                                                                                         n_main:81:12)
    at node:internal/main/run_main_module:22:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
root@odroid:~# sudo -H -u iobroker npm install iobroker.js-controller
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /root/node_modules/iobroker.js-controller
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/root/node_modules/iobroke                                                                                                                         r.js-controller'
npm ERR!  [Error: EACCES: permission denied, mkdir '/root/node_modules/iobro                                                                                                                         ker.js-controller'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: '/root/node_modules/iobroker.js-controller'
npm ERR! }
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-che                                                                                                                         ck the
npm ERR! permissions of the file and its containing directories, or try runn                                                                                                                         ing
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-11-22T12_55_45_027Z-debug-0.log
root@odroid:~#

Thomas Braun

@kafabe

Natürlich liegt es am Nutzer. Und daran, dass du im falschen Verzeichnis stehst.

UND LEG DIR EINEN USER AN UND LASS DEN root IN RUHE!!!!!

KaFaBe

@thomas-braun
Hab es leider nicht geschafft, auch nicht mit einem anderen Benutzer.

Unter root lief das System mehrere Jahre ohne Probleme.

Homoran

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

mehrere Jahre ohne Probleme.

und hat die Rechte mittlerweile dermaßen verbogen dass

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

npm ERR! code EACCES

der arme user iobroker natürlich nicht an

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

path /root/node_modules/iobroker.js-controller

heran darf.

nicht nur root, auch noc sudo!
beides nogo

Thomas Braun

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

Unter root lief das System mehrere Jahre ohne Probleme.

Das sehe ich...
Mein System ohne aktivem root läuft auch seit Jahren ohne Probleme. Ich würde behaupten mit weniger Problemen als dein System.

Und was kommt jetzt mit einem Standarduser bei

cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller

um die Ecke?

Danach die Installation reparieren.

iob stop
iob fix
iob start

Künftig nicht per Dauer-root das System schleichend wegkippen lassen.

KaFaBe

@thomas-braun sagte in iobroker startet nicht nach node-js Update 16.18.1:

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

Unter root lief das System mehrere Jahre ohne Probleme.

Das sehe ich...
Mein System ohne aktivem root läuft auch seit Jahren ohne Probleme. Ich würde behaupten mit weniger Problemen als dein System.

Und was kommt jetzt mit einem Standarduser bei
cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller
um die Ecke?

npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/node-dht-sensor
npm ERR! dest /opt/iobroker/node_modules/.node-dht-sensor-QmYjQqky
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/node-dht-sensor' -> '/opt/iobroker/node_modules/.node-dht-sensor-QmYjQqky'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-11-28T10_08_51_377Z-debug-0.log
$

Thomas Braun

@kafabe

https://forum.iobroker.net/topic/57337/fehler-25-bei-adapter-install-update-mit-npm8

KaFaBe

@thomas-braun sagte in iobroker startet nicht nach node-js Update 16.18.1:

@kafabe

https://forum.iobroker.net/topic/57337/fehler-25-bei-adapter-install-update-mit-npm8

Danke habe ich ausgeführt.
Hat wohl nichts gebracht.

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

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

$ iob start
$ iob status
node:internal/modules/cjs/loader:988
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob                                     roker.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15                                     )
    at Function.Module._load (node:internal/modules/cjs/loader:833:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_ma                                     in:81:12)
    at node:internal/main/run_main_module:22:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
$ sudo -H -u iobroker npm install iobroker.js-controller
npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated later@1.2.0: Please upgrade to the maintained and new drop-in replacement @breejs/later at https://github.com/breejs/later 🚀 Thanks and happy hacking! 🚀  @niftylettuce
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/unix-dgram',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/unix-dgram'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/unix-dgram'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/unix-dgram',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/unix-dgram'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/unix-dgram'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/node-dht-sensor',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/node-dht-sensor'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/node-dht-sensor'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/node-dht-sensor',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/node-dht-sensor'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/node-dht-sensor'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 24
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c node iobroker.js setup first
npm ERR! Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-11-28T10_19_20_911Z-debug-0.log
$ pwd
/opt/iobroker
$

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Homoran

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

Danke habe ich ausgeführt.

wo?

on deinem Output seh ich nichts davon

Thomas Braun

@kafabe

Bitte VOLLSTÄNDIG posten. Inkl. LogIn prompt. Damit man sich da zurechtfindet.

KaFaBe

@homoran sagte in iobroker startet nicht nach node-js Update 16.18.1:

@kafabe sagte in iobroker startet nicht nach node-js Update 16.18.1:

Danke habe ich ausgeführt.

wo?

on deinem Output seh ich nichts davon

Last login: Mon Nov 28 11:08:23 2022 from 192.168.0.42
$ cd /opt/iobroker/node_modules
$ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -ina                                     me ".local-chromium"); do rm -rf ${i%%/}; done
$ cd
$ cd /opt/iobroker
$ iob stop
$ iob fix

Thomas Braun

@kafabe

Warum hast du kein Login prompt?

Homoran

@kafabe wo bist du da?
ich sehe den vollständigen Prompt nicht

NEWS

iobroker startet nicht nach node-js Update 16.18.1

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

Support us

917
Online

31.9k
Users

80.1k
Topics

1.3m
Posts

NEWS

iobroker startet nicht nach node-js Update 16.18.1

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

Support us

917Online

31.9kUsers

80.1kTopics

1.3mPosts

917
Online

31.9k
Users

80.1k
Topics

1.3m
Posts