NEWS
iobroker startet nicht mehr nach Stromausfall
-
Hallo, vielleicht könnt ihr mir weiterhelfen. Ich habe iobroker auf dem Raspberry Pi 4 mit 4 GB installiert. Backup per iobroker ist vorhanden.
Erst hatte ich den Fehler:
pi@raspberrypi4:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs 2023-08-02 12:05:18.474 - info: host.raspberrypi4 iobroker.js-controller version 4.0.23 js-controller starting 2023-08-02 12:05:18.484 - info: host.raspberrypi4 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-08-02 12:05:18.485 - info: host.raspberrypi4 hostname: raspberrypi4, node: v12.20.1 2023-08-02 12:05:18.487 - info: host.raspberrypi4 ip addresses: 192.168.0.30 fd00::9ce:6a61:65f2:1b5b 2001:a61:3a2a:5301:4bac:a24f:bdfa:dc71 fe80::936:913d:5de:c417 2023-08-02 12:05:20.604 - error: host.raspberrypi4-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
Der ging weg mit
npm i iobroker.js-controller@4.0.23 --ignore-scripts
und
curl -sL https://iobroker.net/fix.sh | bash -
konnte die object.jsonl auch komprimieren.
Starten ging leider nicht
node node_modules/iobroker.js-controller/controller.js --logs internal/modules/cjs/loader.js:818 throw err; ^ Error: Cannot find module 'triple-beam' Require stack: - /opt/iobroker/node_modules/logform/colorize.js - /opt/iobroker/node_modules/logform/levels.js - /opt/iobroker/node_modules/logform/index.js - /opt/iobroker/node_modules/winston/lib/winston.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/logger.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/index.js - /opt/iobroker/node_modules/iobroker.js-controller/main.js - /opt/iobroker/node_modules/iobroker.js-controller/controller.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15) at Function.Module._load (internal/modules/cjs/loader.js:667:27) at Module.require (internal/modules/cjs/loader.js:887:19) at require (internal/modules/cjs/helpers.js:74:18) at Object.<anonymous> (/opt/iobroker/node_modules/logform/colorize.js:4:28) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Module.require (internal/modules/cjs/loader.js:887:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/logform/colorize.js', '/opt/iobroker/node_modules/logform/levels.js', '/opt/iobroker/node_modules/logform/index.js', '/opt/iobroker/node_modules/winston/lib/winston.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/logger.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/main.js', '/opt/iobroker/node_modules/iobroker.js-controller/controller.js' ] }
Dann habe ich leider
pi@raspberrypi4:/opt/iobroker $ npm install iobroker.js-controller > iobroker.js-controller@4.0.24 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.10 > iobroker.js-controller@4.0.24 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first internal/modules/cjs/loader.js:818 throw err; ^ Error: Cannot find module 'triple-beam' Require stack: - /opt/iobroker/node_modules/logform/colorize.js - /opt/iobroker/node_modules/logform/levels.js - /opt/iobroker/node_modules/logform/index.js - /opt/iobroker/node_modules/winston/lib/winston.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/logger.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15) at Function.Module._load (internal/modules/cjs/loader.js:667:27) at Module.require (internal/modules/cjs/loader.js:887:19) at require (internal/modules/cjs/helpers.js:74:18) at Object.<anonymous> (/opt/iobroker/node_modules/logform/colorize.js:4:28) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Module.require (internal/modules/cjs/loader.js:887:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/logform/colorize.js', '/opt/iobroker/node_modules/logform/levels.js', '/opt/iobroker/node_modules/logform/index.js', '/opt/iobroker/node_modules/winston/lib/winston.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/logger.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] } npm WARN optional SKIPPING OPTIONAL DEPENDENCY: triple-beam@^1.3.0 (node_modules/winston-transport/node_modules/triple-beam): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for triple-beam@1.4.1: wanted: {"node":">= 14.0.0"} (current: {"node":"12.20.1","npm":"6.14.10"}) npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: triple-beam@1.4.1 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 1 npm ERR! iobroker.js-controller@4.0.24 install: `node iobroker.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.24 install 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/2023-08-02T10_41_46_574Z-debug.log
Und node neu installiert mit
sudo apt remove node* sudo apt remove nodejs* sudo apt update sudo apt install --reinstall nodejs
Nun sagt er iobroker ist nicht installiert.
Könnt ihr mir da bitte helfen? Kann ich einfach neu installieren und das von iobroker erstellte Backup einspielen? -
@andreas-wagner sagte in iobroker startet nicht mehr nach Stromausfall:
error: host.raspberrypi4-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
also hier steht was nicht ging... wozu dann das ganze geraffel was du da gemacht hast...
die DB war nur fraze.. hättest aus dem Backup einspiellen sollen und gut ist..
-
Ging leider auch nicht
pi@raspberrypi4:/opt/iobroker/backups $ iobroker restore iobroker_2022_08_31-02_00_10_backupiobroker.tar.gz Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
Kann ich es neu installieren und dann das Backup einspielen?
-
@arteck da steht aber auch
@andreas-wagner sagte in iobroker startet nicht mehr nach Stromausfall:
node: v12.20.1
-
@crunchip jo total übersehen
-
Dann muss ich node 14 installieren und noch
npm i iobroker.js-controller
richtig?
-
@andreas-wagner wir sind mittlerweile bei v18
Am besten iobroker neu installieren und anschließend backup zurück spielen
-
Danke, das wollte ich wissen, ob das funktioniert
-
@andreas-wagner klar, der Restore wird aber ne ganze Weile in Anspruch nehmen. Also Geduld und Zeit mitbringen.
-
Verzeichnis umbenennen und neu installieren?
Danke, es läuft wieder alles!