über Port 8081 und 8082 kann ich ioBroker nicht aufrufen
-
@thomas-braun ```
========== Start marking the full check here ===========
Script v.2024-12-09 Raspbian+zigbee diag+masking *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.62+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 09:13:01 up 9:19, 3 users, load average: 1.31, 2.24, 1.90 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: ~ Under-voltage detected ~ Arm frequency capped Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** TIME AND TIMEZONES *** Local time: Sun 2025-02-02 09:13:01 CET Universal time: Sun 2025-02-02 08:13:01 UTC RTC time: Sun 2025-02-02 08:13:01 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': shthorsten HOME=/home/shthorsten GROUPS=shthorsten adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker User that is running 'js-controller': js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: true Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 4.2G 518M 1.8G 24M 2.0G 3.7G Swap: 60M 0B 60M Total: 4.3G 518M 1.9G Active iob-Instances: 0 4045 M total memory 494 M used memory 663 M active memory 1231 M inactive memory 1731 M free memory 254 M buffer memory 1653 M swap cache 57 M total swap 0 M used swap 57 M free swap *** top - Table Of Processes *** top - 09:13:01 up 9:19, 3 users, load average: 1.31, 2.24, 1.90 Tasks: 202 total, 1 running, 201 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 4045.0 total, 1729.1 free, 496.3 used, 1908.4 buff/cache MiB Swap: 57.7 total, 57.7 free, 0.0 used. 3548.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** 1332 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.0G 0 2.0G 0% /dev tmpfs tmpfs 405M 5.9M 399M 2% /run /dev/mmcblk0p2 ext4 15G 14G 0 100% / tmpfs tmpfs 2.0G 288K 2.0G 1% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 76M 435M 15% /boot/firmware tmpfs tmpfs 405M 192K 405M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/run/user/1000/doc portal fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.3G /var/ 1.1G /var/log/journal/404274c0b2bb418589be89042d5b9a67 1.1G /var/log/journal 1.1G /var/log 995M /var/cache Archived and active journals take up 1.0G in the file system. /opt/iobroker/backups: 859M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.4G /opt/iobroker/iobroker-data/ 1.2G /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 37M /opt/iobroker/iobroker-data/files/radar-trap.admin/build/index.js.map 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.2-1nodesource1 Version table: 20.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages *** 20.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages Temp directories causing deletion problem: 10 Some problems detected, please run iob fix Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Hosts: Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Core adapters versions js-controller: 7.0.6 admin: 7.4.10 javascript: 8.8.3 nodejs modules from github: 0 Adapter State Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Enabled adapters with bindings ioBroker-Repositories Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Installed ioBroker-Instances Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bookworm InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bookworm-updates InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f20.x_dists_nodistro_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.com/debian bookworm InRelease: Splitting up /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_bookworm_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease into data and signature failed W: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f20.x_dists_nodistro_InRelease into data and signature failed W: Failed to fetch http://archive.raspberrypi.com/debian/dists/bookworm/InRelease Splitting up /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_bookworm_InRelease into data and signature failed W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://deb.debian.org/debian bookworm InRelease Err:1 http://deb.debian.org/debian bookworm InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Err:2 http://deb.debian.org/debian-security bookworm-security InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease into data and signature failed Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Err:3 http://deb.debian.org/debian bookworm-updates InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease into data and signature failed Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Err:4 http://archive.raspberrypi.com/debian bookworm InRelease Splitting up /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_bookworm_InRelease into data and signature failed Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f20.x_dists_nodistro_InRelease into data and signature failed 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: http://deb.debian.org/debian bookworm InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bookworm-updates InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.com/debian bookworm InRelease: Splitting up /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_bookworm_InRelease into data and signature failed W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f20.x_dists_nodistro_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian-security_dists_bookworm-security_InRelease into data and signature failed W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm-updates_InRelease into data and signature failed W: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f20.x_dists_nodistro_InRelease into data and signature failed W: Failed to fetch http://archive.raspberrypi.com/debian/dists/bookworm/InRelease Splitting up /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_bookworm_InRelease into data and signature failed W: Some index files failed to download. They have been ignored, or old ones used instead. Pending Updates: 92 *** 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 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 471316 49074/iobroker.js-c tcp 1 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 470381 49074/iobroker.js-c tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17901 3284/cupsd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 5987 888/sshd: /usr/sbin tcp6 0 0 ::1:631 :::* LISTEN 0 17900 3284/cupsd tcp6 0 0 :::3389 :::* LISTEN 112 1983 952/xrdp tcp6 0 0 :::22 :::* LISTEN 0 5989 888/sshd: /usr/sbin tcp6 0 0 ::1:3350 :::* LISTEN 0 1917 878/xrdp-sesman udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 4678 676/avahi-daemon: r udp 0 0 0.0.0.0:56703 0.0.0.0:* 104 4680 676/avahi-daemon: r udp6 0 0 fe80::2c7c:a66:e1e9:546 :::* 0 457635 821/NetworkManager udp6 0 0 :::5353 :::* 104 4679 676/avahi-daemon: r udp6 0 0 :::54800 :::* 104 4681 676/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-02-02 09:14:30.067 - info: host.raspberrypi starting 32 instances 2025-02-02 09:14:30.287 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeCurrent" 2025-02-02 09:14:30.317 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewest" 2025-02-02 09:14:30.321 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewestNext" 2025-02-02 09:14:30.326 - info: host.raspberrypi instance system.adapter.history.0 in version "3.0.1" started with pid 49110 2025-02-02 09:14:30.330 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmCurrent" 2025-02-02 09:14:30.383 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest" 2025-02-02 09:14:30.388 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext" 2025-02-02 09:14:30.393 - info: host.raspberrypi Some obsolete host states deleted. 2025-02-02 09:14:31.418 - error: host.raspberrypi could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Please also check left over processes when stopping ioBroker! Error: ENOSPC: no space left on device, write 2025-02-02 09:14:31.418 - error: host.raspberrypi Please consider running the installation fixer when on Linux. 2025-02-02 09:14:31.642 - info: history.0 (49110) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.history, node: v20.18.1, js-controller: 7.0.6 2025-02-02 09:14:31.724 - info: history.0 (49110) enabled logging of hm-rpc.0.info.connection (Count=1), Alias=false 2025-02-02 09:14:34.297 - error: host.raspberrypi Caught by controller[0]: [Error: ENOSPC: no space left on device, write] { 2025-02-02 09:14:34.297 - error: host.raspberrypi Caught by controller[0]: errno: -28, 2025-02-02 09:14:34.297 - error: host.raspberrypi Caught by controller[0]: code: 'ENOSPC', 2025-02-02 09:14:34.297 - error: host.raspberrypi Caught by controller[0]: syscall: 'write' 2025-02-02 09:14:34.298 - error: host.raspberrypi Caught by controller[0]: } 2025-02-02 09:14:34.298 - error: host.raspberrypi instance system.adapter.history.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2025-02-02 09:14:34.298 - info: host.raspberrypi Restart adapter system.adapter.history.0 because enabled 2025-02-02 09:14:34.334 - info: host.raspberrypi instance system.adapter.javascript.0 in version "8.8.3" started with pid 49134 2025-02-02 09:14:35.300 - error: host.raspberrypi could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Please also check left over processes when stopping ioBroker! Error: ENOSPC: no space left on device, write 2025-02-02 09:14:35.301 - error: host.raspberrypi Please consider running the installation fixer when on Linux.============ Mark until here for C&P =============
iob diag has finished.
-
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
*** RASPBERRY THROTTLING ***
immer noch!
Was hängt alles am Netzteil/Raspi?@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
1332 CRITICAL ERRORS DETECTED!dito!
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
Pending Updates: 92
und Probleme mit den Repos.
Alles wahrscheinlich weil
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
ENOSPC: no space left on device, write
die ist rappelvoll
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:/dev/mmcblk0p2 ext4 15G 14G 0 100% /
-
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
Current issues:
~ Under-voltage detected
~ Arm frequency capped
Die Spannungsversorgung ist zu schwach. Vernünftiges Netzteil verwenden.
js-controller is not running
Der muss halt laufen.
*** DISPLAY-SERVER SETUP ***
Display-Server: true
Ausschalten...
*** DMESG CRITICAL ERRORS ***
1332 CRITICAL ERRORS DETECTED!
Das sind 1332 Fehler zu viel.
Pending Updates: 92
Das sind 92 Updates zu viel. Wobei auch bei deinen Quellen irgendwas krumm ist. Die Meldungen hab ich aber noch nie gesehen.
/dev/mmcblk0p2 ext4 15G 14G 0 100% /
Dein Dateisystem ist zu. Kein Platz mehr für irgendwas.
-
@homoran Ich habe das netzteil getauscht (Kein Handy Netzteil) 4,5 A hängt nur der Raspberry dran.
-
Installier es neu, diesmal direkt OHNE Desktop und dem ganzen Zinnober in der 64Bit-Lite-Version.
Die braucht auch weniger Platz auf dem Datenträger. Ich würde da aber auch einen größeren verwenden. -
@thorsten4-71 Wie bekomme ich den js-controller zum laufen? Soll ich mir eine neue Karte holen - welche würdest Du mir empfehlen - und neu aufsetzen?
-
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
Soll ich mir eine neue Karte holen - welche würdest Du mir empfehlen - und neu aufsetzen?
Hab ich gerade im Post davor geschrieben.
Neben neuer Karte brauchst du aber auch ein gescheites Netzteil.
Das originale von Raspberry ist zu empfehlen. Hab ich hier an meinen Kisten auch ausschließlich im Einsatz. -
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
das netzteil getauscht (Kein Handy Netzteil) 4,5 A hängt nur der Raspberry dran.
das offizielle pi 5 Netzteil hat höhere Spezifikationen
Am pi selber hängen keine USB Geräte?
-
@thomas-braun hatte ich übersehen, war gerade am schreiben. OK Dank dir. Welche Größe würdest Du mir empfehlen?
-
@homoran nein, da hängt nichts dran. Vielen Dank, werde ich mir zulegen und alles neu machen. grrr
-
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
Welche Größe würdest Du mir empfehlen?
Kann man so generell nicht sagen.
Ich verwende hier 32 - 64 GB SD-Karten, SSDs sind deutlich größer.
Und halt keine Platzfresser wie einen graphischen Desktop, ein Office-Paket und sonstigen Blödsinn. -
@thorsten4-71 sagte in über Port 8081 und 8082 kann ich ioBroker nicht aufrufen:
Welche Größe würdest Du mir empfehlen?
unter 32GB bekommst du eh kaum noch was.
Ich würde aber auf 64 GB gehen.Sieh zu, dass du was vernünftiges bekommst, mindestens mit pro, ultra, besser mit endurance im Namen
