[Gelöst] IObroker startet wieder nicht

Almixx

Hallo. Habe gestern mit Putty ein update und upgrade gemacht und es wurde pivCCU auf eine neue Version gebracht. Jetzt läuft mal wieder IOBroker nicht, warum?

Almixx


Adapter State
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.17.1

Enabled adapters with bindings
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.17.1

ioBroker-Repositories
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.17.1

Installed ioBroker-Instances
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.17.1

Objects and States
Please stand by - This may take a while
Objects:        0
States:         0

*** OS-Repositories and Updates ***
Hit:1 https://repos.influxdata.com/debian stable InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Hit:5 https://phoscon.de/apt/deconz buster InRelease
Hit:6 https://apt.pivccu.de/piVCCU stable InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1000       19463      380/deCONZ
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          18129      637/sshd
tcp        0      0 127.0.0.1:8088          0.0.0.0:*               LISTEN      999        19473      602/influxd
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1000       19581      380/deCONZ
tcp6       0      0 :::8086                 :::*                    LISTEN      999        20830      602/influxd
tcp6       0      0 :::22                   :::*                    LISTEN      0          18131      637/sshd
tcp6       0      0 :::3000                 :::*                    LISTEN      109        39507      5525/grafana
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          15010      474/dhclient
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        16532      409/avahi-daemon: r
udp        0      0 0.0.0.0:52034           0.0.0.0:*                           108        16534      409/avahi-daemon: r
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1000       19851      380/deCONZ
udp6       0      0 :::47206                :::*                                108        16535      409/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                108        16533      409/avahi-daemon: r

*** Log File - Last 25 Lines ***

2023-08-26 12:22:02.142  - info: host.raspberrypi instance system.adapter.vis-inventwo.0 terminated with code null ()
2023-08-26 12:22:02.278  - warn: host.raspberrypi instance system.adapter.trashschedule.0 terminated due to SIGTERM
2023-08-26 12:22:02.278  - info: host.raspberrypi instance system.adapter.trashschedule.0 terminated with code null ()
2023-08-26 12:22:02.278  - warn: host.raspberrypi instance system.adapter.deconz.0 terminated due to SIGTERM
2023-08-26 12:22:02.279  - info: host.raspberrypi instance system.adapter.deconz.0 terminated with code null ()
2023-08-26 12:22:02.338  - info: host.raspberrypi instance system.adapter.shuttercontrol.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-08-26 12:22:02.491  - warn: host.raspberrypi instance system.adapter.fullybrowser.0 terminated due to SIGTERM
2023-08-26 12:22:02.492  - info: host.raspberrypi instance system.adapter.fullybrowser.0 terminated with code null ()
2023-08-26 12:22:02.492  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGTERM
2023-08-26 12:22:02.493  - info: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2023-08-26 12:22:02.635  - warn: host.raspberrypi instance system.adapter.web.0 terminated due to SIGTERM
2023-08-26 12:22:02.636  - info: host.raspberrypi instance system.adapter.web.0 terminated with code null ()
2023-08-26 12:22:02.636  - warn: host.raspberrypi instance system.adapter.mytime.0 terminated due to SIGTERM
2023-08-26 12:22:02.636  - info: host.raspberrypi instance system.adapter.mytime.0 terminated with code null ()
2023-08-26 12:22:02.721  - warn: host.raspberrypi instance system.adapter.wled.0 terminated due to SIGTERM
2023-08-26 12:22:02.722  - info: host.raspberrypi instance system.adapter.wled.0 terminated with code null ()
2023-08-26 12:22:03.054  - info: host.raspberrypi instance system.adapter.influxdb.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-08-26 12:22:03.054  - info: host.raspberrypi All instances are stopped.
2023-08-26 12:22:03.160  - warn: host.raspberrypi instance system.adapter.socketio.0 terminated due to SIGTERM
2023-08-26 12:22:03.161  - info: host.raspberrypi instance system.adapter.socketio.0 terminated with code null ()
2023-08-26 12:22:03.161  - info: host.raspberrypi All instances are stopped.
2023-08-26 12:22:03.162  - warn: host.raspberrypi instance system.adapter.history.0 terminated due to SIGTERM
2023-08-26 12:22:03.162  - info: host.raspberrypi instance system.adapter.history.0 terminated with code null ()
2023-08-26 12:22:03.163  - info: host.raspberrypi All instances are stopped.
2023-08-26 12:22:03.279  - info: host.raspberrypi terminated

Thomas Braun

@almixx

Buster ist tot, installier da ein lebendes Betriebssystem.
Hatte ich dir aber auch vor Wochen schon geraten. Der Rat dazu hat ja auch einen Grund.

Almixx

Aber es ging doch die ganze Zeit, ich weiß halt nicht, was ich alles machen müsste.

Thomas Braun

@almixx

Joar, sowas geht immer 'die ganze Zeit', bis es eben nicht mehr geht.

Almixx

@thomas-braun
OK. Was wären denn die einzelnen Schritte, die ich machen müsste , um wieder auf dem Stand von jetzt zu sein. Backups vom Adapter wären vorhanden....
benutze IOB, Homematic, Grafana+InfluxdB und Deconz

Thomas Braun

@almixx

Weil ich ich es gerade in der Zwischenablage habe:

https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht

Den anderen Kram musst du halt wieder installieren.

Almixx

@thomas-braun
Ich habe ja ne ssd, funktioniert die Installation dann direkt darauf?

Thomas Braun

@almixx

Das Zielmedium kann im Imager ausgesucht werden.

Almixx

@thomas-braun
So, nach deinem Rat habe ich alles neu installiert und per Restore wieder drauf gespielt. Läuft wieder alles, bis auf Influxdb. Da schaue ich jetzt noch bei.

NEWS

[Gelöst] IObroker startet wieder nicht

Support us

1.0k
Online

32.1k
Users

80.7k
Topics

1.3m
Posts

NEWS

[Gelöst] IObroker startet wieder nicht

Support us

1.0kOnline

32.1kUsers

80.7kTopics

1.3mPosts

1.0k
Online

32.1k
Users

80.7k
Topics

1.3m
Posts