Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Thomas Braun]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

            Time zone: Europe/London (GMT, +0000)

Vermutlich auch falsch.

[Michael_Schotthoefer]

@glasfaser
das kam dabei raus.

Spoiler

sudo -H -u iobroker npm install iobroker.js-controller
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 har-validator@5.1.5: this library is no longer supported
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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code 1
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! node:internal/modules/cjs/loader:1137
npm ERR! throw err;
npm ERR! ^
npm ERR!
npm ERR! Error: Cannot find module 'tar'
npm ERR! Require stack:
npm ERR! - /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupBackup.js
npm ERR! - /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/index.js
npm ERR! - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
npm ERR! at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
npm ERR! at Module._load (node:internal/modules/cjs/loader:975:27)
npm ERR! at Module.require (node:internal/modules/cjs/loader:1225:19)
npm ERR! at require (node:internal/modules/helpers:177:18)
npm ERR! at Object.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupBackup.js:12:31)
npm ERR! at Module._compile (node:internal/modules/cjs/loader:1356:14)
npm ERR! at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
npm ERR! at Module.load (node:internal/modules/cjs/loader:1197:32)
npm ERR! at Module._load (node:internal/modules/cjs/loader:1013:12)
npm ERR! at Module.require (node:internal/modules/cjs/loader:1225:19) {
npm ERR! code: 'MODULE_NOT_FOUND',
npm ERR! requireStack: [
npm ERR! '/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupBackup.js',
npm ERR! '/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/index.js',
npm ERR! '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
npm ERR! ]
npm ERR! }
npm ERR!
npm ERR! Node.js v18.19.0

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-17T19_59_00_782Z-debug-0.log

danke schonmal.

[Michael_Schotthoefer]

@thomas-braun
hi thomas.
heißt sd-karte formatieren und alles neu aufspielen?

[Thomas Braun]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

heißt sd-karte formatieren und alles neu aufspielen?

Ich würde es auf eine konsistente und aktuelle Basis setzen.

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

[Michael_Schotthoefer]

@thomas-braun
dann werde ich das morgen mal angehen.
ich werde berichten.

danke schonmal.

[Michael_Schotthoefer]

@thomas-braun

gibt es eine möglichkeit iobroker ein backup zu ziehen über putty?
habe backitup laufen gehabt aber habe nicht gemerkt das es schon länger nicht mehr sichert. habe über filezilla jetzt mal das ganze iobroker gesichert auf dem nas.
reicht das?

[Thomas Braun]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

gibt es eine möglichkeit iobroker ein backup zu ziehen über putty?

iobroker backup

Datei liegt dann in /opt/iobroker/backups
Wobei ich mir halt auch anschauen würde, warum dein Backitup nicht funktioniert. Insgesamt scheint mir deine Kiste leicht zu hinken...

[Michael_Schotthoefer]

@thomas-braun
wenn ich es richtig sehe benötige ich 64bit oder?

[Michael_Schotthoefer]

@thomas-braun
das hatte ich schon probiert.
geht leider nicht da anscheinend alles zerschossen ist.

[Thomas Braun]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

geht leider nicht da anscheinend alles zerschossen ist.

Ja, wissen wir.

[Glasfaser]

@michael_schotthoefer

Kannst du etwas testen :

iob stop
iob fix  
iob nodejs-update
iob setup first
sudo reboot

[Glasfaser]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

readonly on device

Hast du den Netz-Stecker gezogen !?

[Michael_Schotthoefer]

@glasfaser sagte in Iobroker lässt sich nicht mehr starten.:

@michael_schotthoefer

Kannst du etwas testen :

iob stop
iob fix  
iob nodejs-update
iob setup first
sudo reboot

habe es getestet. das kam dabei raus.

Spoiler

 ioBroker nodejs updater 2023-10-13
No recommendation for a nodejs version found on your system. We recommend to install latest version from nodejs v18 tree.

Your current setup is:
/usr/bin/nodejs         v18.19.0
/usr/bin/node           v18.19.0
/usr/bin/npm            10.2.3
/usr/bin/npx            10.2.3
/usr/bin/corepack       0.22.0

We found these nodejs versions available for installation:

nodejs:
  Installed: 18.19.0-1nodesource1
  Candidate: 18.19.0-1nodesource1
  Version table:
 *** 18.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
        100 /var/lib/dpkg/status
     18.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.16.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.9.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages



Nothing to do - Your installation is using the correct paths.

You are running nodejs v18.19.0. Do you want to install latest version from nodejs v.18 tree?

Press <y> to continue or any other key to quit
Trying to update your installation now. Please be patient.

Waiting for ioBroker to shut down - Give me a minute...
############################################################

*** These repos are active on your system:
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Get:3 https://packages.grafana.com/enterprise/deb stable InRelease [5984 B]
Err:3 https://packages.grafana.com/enterprise/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
Ign:4 https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye InRelease
Err:5 https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release
  404  Not Found [IP: 2600:1f1c:2e5:6900:e12:7a5d:4cf3:3662 443]
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/enterprise/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
E: The repository 'https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2

*** Installing ca-certificates, curl and gnupg, just in case they are missing.

*** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source

deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 1001

*** These repos are active after the adjustments:
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Get:3 https://packages.grafana.com/enterprise/deb stable InRelease [5984 B]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Err:3 https://packages.grafana.com/enterprise/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
Ign:5 https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye InRelease
Err:6 https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release
  404  Not Found [IP: 2600:1f1c:2e5:6900:e12:7a5d:4cf3:3662 443]
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/enterprise/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
E: The repository 'https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2

Installing the recommended nodejs version now!

Exact recommended version unknown, installing a fallback!
dpkg: warning: downgrading nodejs from 18.19.0-1nodesource1 to 18.0.0-1nodesource1
(Reading database ... 67384 files and directories currently installed.)
Preparing to unpack .../nodejs_18.0.0-1nodesource1_armhf.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.0.0-1nodesource1) over (18.19.0-1nodesource1) ...
Setting up nodejs (18.0.0-1nodesource1) ...
Processing triggers for man-db (2.9.4-2) ...

Updating fallback to latest nodejs v18 release
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/enterprise/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
E: The repository 'https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release' does not have a Release file.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
(Reading database ... 67647 files and directories currently installed.)
Preparing to unpack .../nodejs_18.19.0-1nodesource1_armhf.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.19.0-1nodesource1) over (18.0.0-1nodesource1) ...
Setting up nodejs (18.19.0-1nodesource1) ...
Processing triggers for man-db (2.9.4-2) ...
v18.19.0 has been installed! You are using the latest version now!
Installing the recommended nodejs version!
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/enterprise/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545
E: The repository 'https://packagecloud.io/ookla/speedtest-cli/raspbian bullseye Release' does not have a Release file.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2

We tried our best to update or fix your nodejs. Please run iob diag again to verify.

*** RESTARTING ioBroker NOW! ***
 Please refresh or restart your browser in a few moments.

pi@raspberrypi:~ $ iob setup first
node:internal/modules/cjs/loader:1137
  throw err;
  ^

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

Node.js v18.19.0

danke für die vielen hilfen von euch.

[Glasfaser]

@michael_schotthoefer

der letzte Befehl war

sudo reboot

und jetzt

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

[Michael_Schotthoefer]

@glasfaser sagte in Iobroker lässt sich nicht mehr starten.:

@michael_schotthoefer

der letzte Befehl war

sudo reboot

und jetzt

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

hat leider nicht funktioniert.

[crunchip]

@michael_schotthoefer sagte in Iobroker lässt sich nicht mehr starten.:

hat leider nicht funktioniert

Warum? MELDUNGEN?

[Borkenkäfer]

@crunchip
hallo
hänge mich hier mal rein da ich gleichen Fehlermeldungen habe
nach reboot und dem install iobroker.js-controller@5.0.17 komt
npm ERR! invalid Version
< cd /opt/iobroker
ulli@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller@5.0.17
npm ERR! Invalid Version:

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-22T17_03_13_632Z-debug-0.log>

[Borkenkäfer]

@crunchip
iob diag ergibt folgende Status

sorry das ich das so reinkopiere, kenn die andere Vorgehensweise leider nicht

Node.js v18.19.0
ioBroker Status:

Status admin and web instance:
node:internal/modules/cjs/loader:1137
throw err;
^

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

Node.js v18.19.0

Objects: 0
States: 0

Size of iob-Database:

5.8M /opt/iobroker/iobroker-data/objects.jsonl
420K /opt/iobroker/iobroker-data/states.jsonl

[Glasfaser]

@borkenkäfer sagte in Iobroker lässt sich nicht mehr starten.:

hänge mich hier mal rein

Dann zeige erst

die Full Ausgabe von

iob diag

so ... bringt das nicht !

Ausgabe in Code-Tags </>

[Glasfaser]

@borkenkäfer sagte in Iobroker lässt sich nicht mehr starten.:

sorry das ich das so reinkopiere, kenn die andere Vorgehensweise leider nicht

Hier ...

https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge

sehr gut erklärt !