Rega Fehler

Thomas Braun

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

Chris-D 0

@thomas-braun said in Rega Fehler:

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

pi@raspberrypi:~ $ cd /opt/iobroker
pi@raspberrypi:/opt/iobroker $ iobroker stop
pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller 

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

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

NPM version: 6.14.14

> iobroker@2.0.3 install /opt/iobroker/node_modules/iobroker
> node lib/checkVersions.js

NPM version: 6.14.14

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


The following notifications happened during sync: 
- Ignoring Directory "hm-rega" because officially not created as meta object. Please remove directory!


> acme-v2@1.8.6 postinstall /opt/iobroker/node_modules/acme-v2
> node scripts/postinstall


Greenlock and ACME.js v3 are on the way!
Watch for updates at https://indiegogo.com/at/greenlock


> iobroker@2.0.3 postinstall /opt/iobroker/node_modules/iobroker
> node lib/install.js



╭─────────────────────────────────────────────────────────╮
│                                                         │
│ Manual installation of ioBroker is no longer supported  │
│ on Linux, OSX and FreeBSD!                              │
│ Please refer to the documentation on how to install it! │
│ https://github.com/ioBroker/ioBroker/wiki/Installation  │
│                                                         │
╰─────────────────────────────────────────────────────────╯


npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 100
npm ERR! iobroker@2.0.3 postinstall: `node lib/install.js`
npm ERR! Exit status 100
npm ERR! 
npm ERR! Failed at the iobroker@2.0.3 postinstall 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/iobroker/.npm/_logs/2021-08-19T15_29_16_679Z-debug.log

apollon77

@chris-d-0 hattest du mal npm 7 drauf? Da ist ein Mischmasch bei dir.

Thomas Braun

@apollon77

Offenbar.

This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

ist jedenfalls ein starker Indikator für npm7.

Homoran

@thomas-braun package-lock.json löschen

Thomas Braun

@homoran Keine Ahnung was man da machen kann. Musste das auf meinem System noch nie gerade biegen. Aber da sind ja auch die Versionssprünge nie so groß. Da am Ball bleiben zahlt sich halt aus.

Homoran

@thomas-braun sagte in Rega Fehler:

Aber da sind ja auch die Versionssprünge nie so groß.

das kann ein weiteres Problem sein.

bin nicht mehr am PC.

die package-lock.json sollte IMHO direkt in /opt/iobroker liegen.
Nach löschen wird sie neu gebaut, dann in der richtigen Version wenn jetzt wieder npm v6 läuft

Chris-D 0

@apollon77 ja genau hatte ich

Chris-D 0

@homoran dann wäre die Frage wie das geht?

Chris-D 0

hat noch jemand eine Idee? der IoBroker geht jetzt nicht mehr. Vorher, bis auf den Rega Adapter, schon.

Thomas Braun

@chris-d-0

iobroker stop 
sudo -u iobroker mv /opt/iobroker/package.json /opt/iobroker/packagejson_backup
iobroker start

Chris-D 0

@thomas-braun nicht viel passt

pi@raspberrypi:~ $ iobroker stop 
pi@raspberrypi:~ $ sudo -u iobroker mv /opt/iobroker/package.json /opt/iobroker/packagejson_backup
pi@raspberrypi:~ $ iobroker start

Thomas Braun

@chris-d-0

'Nicht viel passiert' ist gut. Keine Rückmeldung = alles wurde ausgeführt.

iobroker status

Chris-D 0

@thomas-braun sehr gut

pi@raspberrypi:~ $ iobroker status
iobroker is running on this host.

At least one iobroker host is running.

Objects type: file
States  type: file

ABer IP Adresse kann nicht angezeigt werden

Thomas Braun

@chris-d-0

iobroker list adapters
iobroker list instances

Chris-D 0

@thomas-braun

pi@raspberrypi:~ $ iobroker list instances
  system.adapter.admin.0                 : admin                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.backitup.0              : backitup              -  enabled
+ system.adapter.discovery.0             : discovery             -  enabled
+ system.adapter.echarts.0               : echarts               -  enabled
  system.adapter.email.0                 : email                 - disabled
  system.adapter.fb-checkpresence.0      : fb-checkpresence      - disabled
  system.adapter.fritzdect.0             : fritzdect             - disabled
  system.adapter.habpanel.0              : habpanel              -  enabled
+ system.adapter.history.0               : history               -  enabled
+ system.adapter.hm-rega.0               : hm-rega               -  enabled
+ system.adapter.hm-rpc.0                : hm-rpc                -  enabled, port: 0
+ system.adapter.hm-rpc.1                : hm-rpc                -  enabled, port: 0
  system.adapter.ical.0                  : ical                  -  enabled
+ system.adapter.info.0                  : info                  -  enabled
+ system.adapter.iot.0                   : iot                   -  enabled
+ system.adapter.javascript.0            : javascript            -  enabled
  system.adapter.material.0              : material              -  enabled
  system.adapter.mobile.0                : mobile                - disabled
  system.adapter.openweathermap.0        : openweathermap        -  enabled
+ system.adapter.ping.0                  : ping                  -  enabled
+ system.adapter.samsung.0               : samsung               -  enabled
+ system.adapter.simple-api.0            : simple-api            -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonos.0                 : sonos                 -  enabled
  system.adapter.synology.0              : synology              - disabled, port: 5000
+ system.adapter.telegram.0              : telegram              -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.tr-064.0                : tr-064                -  enabled
+ system.adapter.tr-064.1                : tr-064                -  enabled
  system.adapter.viessmann.0             : viessmann             - disabled, port: 3002
  system.adapter.vis.0                   : vis                   - disabled
  system.adapter.web.0                   : web                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

+ instance is alive

Thomas Braun

@chris-d-0

iobroker start admin
iobroker start web

Chris-D 0

@thomas-braun said in Rega Fehler:

iobroker start admin iobroker start web

pi@raspberrypi:~ $ iobroker start admin

pi@raspberrypi:~ $ iobroker start web
pi@raspberrypi:~ $

keine Verbesserung

Thomas Braun

@chris-d-0

iobroker list instances

Thomas Braun

@chris-d-0

iobroker stop 
sudo -u iobroker mv /opt/iobroker/package.json /opt/iobroker/packagejson_backup
sudo -u iobroker mv /opt/iobroker/package-lock.json /opt/iobroker/package-lockjson_backup
iobroker start

Community Forum

NEWS

Rega Fehler

Support us

530

32.7k

82.6k

1.3m