NEWS
ioBroker auf einem Raspberry Pi5
-
Hallo zusammen,
ich hatte das zwar schon in der Hardware Rubrik gepostet, aber ich denke in einem neuen Thread ist es besser aufgehoben.
Gestern kam mein Raspberry Pi5 in 8GB, auf den ich dann versucht habe, ioBroker zu installieren.Ich habe auf eine SD Karte Bookworm 64Bit lite installiert, dann Expand Filesystem (muss man das überhaupt noch machen?), dann ein Update und dann über das Script
curl -sLf https://iobroker.net/install.sh | bash -...ioBroker installiert.
Im Schritt 3 gab es folgende Fehlermeldungen:
========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done ========================================================================== Node.js not found. Installing... ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done ca-certificates is already the newest version (20230311). curl is already the newest version (7.88.1-10+deb12u4). gnupg is already the newest version (2.2.40-1.1). gnupg set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node _18.x nodistro main Processing triggers for man-db (2.11.2-2) ...ource1_arm64.deb ...led.) Installed nodejs Node.js Installed successfully! Changing npm registry to https://registry.npmjs.org Processing triggers for man-db (2.11.2-2) ...arm64.deb ... installed.) Installed acl Setting up libavahi-compat-libdnssd-dev:arm64 (0.8-10) ...-10_arm64.deb ... Installed libavahi-compat-libdnssd-dev Processing triggers for man-db (2.11.2-2) ...1) ...1_arm64.deb ...ed.) Installed libudev-dev Processing triggers for man-db (2.11.2-2) ...pt2) .....1+rpt2) ...2712v8......4.deb ....... Installed libpam0g-dev Processing triggers for man-db (2.11.2-2) ...m64.deb ......installed.) Installed git Extracting templates from packages: 100% Setting up libcairo2-dev:arm64 (1.16.0-7+rpt1) ....u3) ...t1) .........rm64.deb ... Installed libcairo2-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) ...m64.deb ... .... Installed libpango1.0-dev Setting up libjpeg-dev:arm64 (1:2.1.5-2) ...5-2) ...4.deb ....deb ...) Installed libjpeg-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) ... installed.) Installed libgif-dev Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.10+dfsg-1+b1) .......... Installed librsvg2-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) .....nstalled.) Installed cmake ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== User iobroker created Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! errno ERR_SOCKET_TIMEOUT npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/@iobroker%2fdb-states-file: Socket timeout npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2023-11-09T17_43_57_638Z-debug-0.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Created symlink /etc/systemd/system/multi-user.target.wants/iobroker.service → /lib/systemd/system/iobroker.service. Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.178.93:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console!Also, einen Proxy oder was ähnliches habe ich nicht.
Mit dem Netzwerk ist alles i.O. Der andere Pi4 mit ioBroker läuft im gleichen Netz.Über
iob statusgab es dann folgende Meldung:
pi@RPI5:/opt/iobroker $ iob status 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:86:12) at node:internal/main/run_main_module:23:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.18.2 pi@RPI5:/opt/iobroker $Daraufhin habe ich aufgeführt:
pi@RPI5:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated dgram@1.0.1: npm is holding this package for security reason s. 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 request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup '/opt/iobroker/node_modules', npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroke r/node_modules'] { npm WARN cleanup errno: -39, npm WARN cleanup code: 'ENOTEMPTY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: '/opt/iobroker/node_modules' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 24 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! creating conf/iobroker.json npm ERR! Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! {1} npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2 023-11-09T21_42_08_685Z-debug-0.log pi@RPI5:/opt/iobroker $ iob status node:internal/modules/cjs/loader:1080 throw err; ^ {1} 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:86:12) at node:internal/main/run_main_module:23:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } {1} Node.js v18.18.2 pi@RPI5:/opt/iobroker $Aber wahrscheinlich mangelt es erst einmal an Hardware um das nachzuvollziehen.
-
Hallo zusammen,
ich hatte das zwar schon in der Hardware Rubrik gepostet, aber ich denke in einem neuen Thread ist es besser aufgehoben.
Gestern kam mein Raspberry Pi5 in 8GB, auf den ich dann versucht habe, ioBroker zu installieren.Ich habe auf eine SD Karte Bookworm 64Bit lite installiert, dann Expand Filesystem (muss man das überhaupt noch machen?), dann ein Update und dann über das Script
curl -sLf https://iobroker.net/install.sh | bash -...ioBroker installiert.
Im Schritt 3 gab es folgende Fehlermeldungen:
========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done ========================================================================== Node.js not found. Installing... ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done ca-certificates is already the newest version (20230311). curl is already the newest version (7.88.1-10+deb12u4). gnupg is already the newest version (2.2.40-1.1). gnupg set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node _18.x nodistro main Processing triggers for man-db (2.11.2-2) ...ource1_arm64.deb ...led.) Installed nodejs Node.js Installed successfully! Changing npm registry to https://registry.npmjs.org Processing triggers for man-db (2.11.2-2) ...arm64.deb ... installed.) Installed acl Setting up libavahi-compat-libdnssd-dev:arm64 (0.8-10) ...-10_arm64.deb ... Installed libavahi-compat-libdnssd-dev Processing triggers for man-db (2.11.2-2) ...1) ...1_arm64.deb ...ed.) Installed libudev-dev Processing triggers for man-db (2.11.2-2) ...pt2) .....1+rpt2) ...2712v8......4.deb ....... Installed libpam0g-dev Processing triggers for man-db (2.11.2-2) ...m64.deb ......installed.) Installed git Extracting templates from packages: 100% Setting up libcairo2-dev:arm64 (1.16.0-7+rpt1) ....u3) ...t1) .........rm64.deb ... Installed libcairo2-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) ...m64.deb ... .... Installed libpango1.0-dev Setting up libjpeg-dev:arm64 (1:2.1.5-2) ...5-2) ...4.deb ....deb ...) Installed libjpeg-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) ... installed.) Installed libgif-dev Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.10+dfsg-1+b1) .......... Installed librsvg2-dev Processing triggers for libc-bin (2.36-9+rpt2+deb12u3) .....nstalled.) Installed cmake ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== User iobroker created Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! errno ERR_SOCKET_TIMEOUT npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/@iobroker%2fdb-states-file: Socket timeout npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2023-11-09T17_43_57_638Z-debug-0.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Created symlink /etc/systemd/system/multi-user.target.wants/iobroker.service → /lib/systemd/system/iobroker.service. Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.178.93:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console!Also, einen Proxy oder was ähnliches habe ich nicht.
Mit dem Netzwerk ist alles i.O. Der andere Pi4 mit ioBroker läuft im gleichen Netz.Über
iob statusgab es dann folgende Meldung:
pi@RPI5:/opt/iobroker $ iob status 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:86:12) at node:internal/main/run_main_module:23:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.18.2 pi@RPI5:/opt/iobroker $Daraufhin habe ich aufgeführt:
pi@RPI5:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated dgram@1.0.1: npm is holding this package for security reason s. 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 request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup '/opt/iobroker/node_modules', npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroke r/node_modules'] { npm WARN cleanup errno: -39, npm WARN cleanup code: 'ENOTEMPTY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: '/opt/iobroker/node_modules' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 24 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! creating conf/iobroker.json npm ERR! Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! {1} npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2 023-11-09T21_42_08_685Z-debug-0.log pi@RPI5:/opt/iobroker $ iob status node:internal/modules/cjs/loader:1080 throw err; ^ {1} 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:86:12) at node:internal/main/run_main_module:23:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } {1} Node.js v18.18.2 pi@RPI5:/opt/iobroker $Aber wahrscheinlich mangelt es erst einmal an Hardware um das nachzuvollziehen.
@hg6806 sagte in ioBroker auf einem Raspberry Pi5:
ich hatte das zwar schon in der Hardware Rubrik gepostet,
du bist zu spät
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@hg6806 sagte in ioBroker auf einem Raspberry Pi5:
ich hatte das zwar schon in der Hardware Rubrik gepostet,
du bist zu spät
-
@hg6806 sagte in ioBroker auf einem Raspberry Pi5:
die Suche hatte auch nichts ergeben.
Darüber hab ich ihn gerade gefunden.
ich mach dann hier mal zu
848
Online32.6k
Benutzer81.9k
Themen1.3m
Beiträge