Neues YouTube-Video: Visualisierung im Devices-Adapter

[SMS]

Hi zusammen,

wollte gerade das Update machen. Master ist schon eine Weile auf 3.3.22 und jetzt wollte ich die Slaves nachziehen.
Folgendes Problem:

pi@MotionEye:~ $ iob update
internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob                                                                                 roker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js                                                                                 :75:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

pi@MotionEye:~ $ iob upgrade self
internal/modules/cjs/loader.js:905
  throw err;
  ^

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

Dann dachte ich, OK machst mal ein Update vom Pi, was auch funktioniert hat.

Danach immer noch die o.g. Meldungen.

pi@MotionEye:~ $ iob start
pi@MotionEye:~ $ iobroker start
Job for iobroker.service failed because the control process exited with error code.
See "systemctl status iobroker.service" and "journalctl -xe" for details.
pi@MotionEye:~ $ systemctl status iobroker.service
● iobroker.service - ioBroker Server
   Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2022-02-04 23:15:09 CET; 29s ago
     Docs: http://iobroker.net
  Process: 853 ExecStart=/usr/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobroker.js-controller/controller.js (code=exited, sta
 Main PID: 853 (code=exited, status=1/FAILURE)

Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Service RestartSec=100ms expired, scheduling restart.
Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Scheduled restart job, restart counter is at 5.
Feb 04 23:15:09 MotionEye systemd[1]: Stopped ioBroker Server.
Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Start request repeated too quickly.
Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Failed with result 'exit-code'.
Feb 04 23:15:09 MotionEye systemd[1]: Failed to start ioBroker Server.
Feb 04 23:15:15 MotionEye systemd[1]: iobroker.service: Start request repeated too quickly.
Feb 04 23:15:15 MotionEye systemd[1]: iobroker.service: Failed with result 'exit-code'.
Feb 04 23:15:15 MotionEye systemd[1]: Failed to start ioBroker Server.

pi@MotionEye:~ $ journalctl -xe
-- Automatic restarting of the unit iobroker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Feb 04 23:15:09 MotionEye systemd[1]: Stopped ioBroker Server.
-- Subject: A stop job for unit iobroker.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit iobroker.service has finished.
--
-- The job identifier is 1283 and the job result is done.
Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Start request repeated too quickly.
Feb 04 23:15:09 MotionEye systemd[1]: iobroker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit iobroker.service has entered the 'failed' state with result 'exit-code'.
Feb 04 23:15:09 MotionEye systemd[1]: Failed to start ioBroker Server.
-- Subject: A start job for unit iobroker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit iobroker.service has finished with a failure.
--
-- The job identifier is 1283 and the job result is failed.
Feb 04 23:15:15 MotionEye sudo[864]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl start iobroker
Feb 04 23:15:15 MotionEye sudo[864]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Feb 04 23:15:15 MotionEye systemd[1]: iobroker.service: Start request repeated too quickly.
Feb 04 23:15:15 MotionEye systemd[1]: iobroker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit iobroker.service has entered the 'failed' state with result 'exit-code'.
Feb 04 23:15:15 MotionEye systemd[1]: Failed to start ioBroker Server.
-- Subject: A start job for unit iobroker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit iobroker.service has finished with a failure.
--
-- The job identifier is 1340 and the job result is failed.
Feb 04 23:15:15 MotionEye sudo[864]: pam_unix(sudo:session): session closed for user root

Was ist da passiert?

So sieht es aktuell aus:

Danke!!

[SMS]

keiner eine Ahnung? Ein Backup von kurz davor hat leider nichts gebracht.
Das komische ist wieder, das ich nicht auf die Konsole zugreifen kann.

[Thomas Braun]

@sms

Installier nochmal drüber.