Raspberry / iobroker absturz: Loading chunk 401 failed
-
Hallo zusammen,
ich habe das Gefühl das mein Raspberry ein Problem hat. Ich hatte seit einiger Zeit immer wieder Iobroker abstürze und dachte dass es an einer sterbenden SD Karte liegen könnte. Dabei hatte ich gehäuft abstürze wenn ich auf den Admin zugreifen wollte. Danach war immer nur ein harter PI Neustart möglich da auch kein Zugriff über SSH mehr ging. Nun habe ich in den letzten Tagen alles auf einer neuen SD Karte neu aufgesetzt und leider das selbe Problem wieder. Er scheint zumindest mehrere Stunden gut zu laufen und wenn ich dann auf den Admin zugreifen will kommt folgende Fehlermeldung und alles hängt:
Error in GUI! Please open the browser console (F12), copy error text from there and create the issue on github Without this information it is not possible to analyse the error. It should looks like error If in the second line you will see at :3000/static/js/main.chunk.js:36903 and not the normal file name, please try to reproduce an error with opened browser console. In this case the special "map" files will be loaded and the developers can see the real name of functions and files. Loading chunk 401 failed. (timeout: http://192.168.178.80:8081/static/js/401.a8026601.chunk.js) ChunkLoadError: Loading chunk 401 failed.(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t)(timeout: http://192.168.178.80:8081/static/js/401.a8026601.chunk.js)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at t.f.j (http://192.168.178.80:8081/static/js/main.22705a8c.js:1:11752)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at http://192.168.178.80:8081/static/js/main.22705a8c.js:1:1118(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at Array.reduce (<anonymous>)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at t.e (http://192.168.178.80:8081/static/js/main.22705a8c.js:1:1096)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at http://192.168.178.80:8081/static/js/6518.bdbf8c40.chunk.js:2:216775(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at P (http://192.168.178.80:8081/static/js/3617.303c042a.chunk.js:2:3345)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at Ei (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:120780)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at ks (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:109412)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at ys (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:109340)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at vs (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:109203)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at as (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:104307)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at S (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:131297)(e,t)=>(0,f.jsxs)("div",{children:[e,(0,f.jsx)("br",{})]},t) at MessagePort.T (http://192.168.178.80:8081/static/js/2882.4644449f.chunk.js:2:131831)Kennt jemand das Problem?
Schönen Gruß!
-
Was sagt
iob diag? -
@nftvirus sagte in Raspberry / iobroker absturz: Loading chunk 401 failed:
Please open the browser console (F12), copy error text from there
und was hast du da gesehen?
-
@meister-mopper ```
======== Start marking the full check here =========Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 3 Model B Plus Rev 1.3 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 08:07:06 up 15:27, 1 user, load average: 0.81, 1.06, 6.40 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred ~ Throttling has occurred ~ Soft temperature limit has occurred *** Time and Time Zones *** Local time: Mon 2024-03-25 08:07:06 GMT Universal time: Mon 2024-03-25 08:07:06 UTC RTC time: n/a Time zone: Europe/London (GMT, +0000) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 909M 653M 145M 0.0K 110M 197M Swap: 99M 99M 0.0K Total: 1.0G 753M 145M 909 M total memory 653 M used memory 253 M active memory 426 M inactive memory 144 M free memory 3 M buffer memory 107 M swap cache 99 M total swap 99 M used swap 0 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 3.1G 25G 12% / devtmpfs devtmpfs 325M 0 325M 0% /dev tmpfs tmpfs 455M 0 455M 0% /dev/shm tmpfs tmpfs 182M 1000K 181M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Mar 24 16:39:33 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=473cba6a-02 rootfstype=ext4 fsck.repair=yes rootwait [Sun Mar 24 16:39:36 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Sun Mar 24 16:39:36 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Sun Mar 24 16:39:36 2024] EXT4-fs (mmcblk0p2): recovery complete [Sun Mar 24 16:39:36 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Sun Mar 24 16:39:36 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Sun Mar 24 16:39:39 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 517M /var/ 179M /var/cache 175M /var/cache/apt 148M /var/lib 123M /var/lib/apt/lists Archived and active journals take up 88.0M in the file system. /opt/iobroker/backups: 1.6M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 163M /opt/iobroker/iobroker-data/ 123M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 45M /opt/iobroker/iobroker-data/files/devices.admin/static 45M /opt/iobroker/iobroker-data/files/devices.admin The five largest files in iobroker-data are: 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 14M /opt/iobroker/iobroker-data/objects.jsonl 8.6M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.d0c8b930.chunk.js.map 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2466692-if00 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.1-1nodesource1 Version table: 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.devices.0 : devices : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.wled.0 : wled : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "node-red" : 5.1.0 , installed 5.1.0 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Objects and States Please stand by - This may take a while Objects: 570 States: 397 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 37 *** 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 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 29659 4860/io.mqtt.0 tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 34853 4843/node-red tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 32848 4765/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 29570 4765/iobroker.js-co tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 12843 491/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 32451 4783/io.admin.0 tcp6 0 0 :::80 :::* LISTEN 1001 34854 4843/node-red tcp6 0 0 :::22 :::* LISTEN 0 12845 491/sshd: /usr/sbin udp 0 0 0.0.0.0:41473 0.0.0.0:* 108 12773 339/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12005 620/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 33825 4890/io.wled.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12771 339/avahi-daemon: r udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 33010 4843/node-red udp6 0 0 :::546 :::* 0 14918 620/dhcpcd udp6 0 0 :::53449 :::* 108 12774 339/avahi-daemon: r udp6 0 0 :::5353 :::* 108 12772 339/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-03-25 07:45:56.639 - info: node-red.0 (4790) Node-RED: 25 Mar 07:45:56 - [info] Dashboard version 3.6.5 started at /ui 2024-03-25 07:46:02.767 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [info] Settings file : /opt/iobroker/iobroker-data/node-red/settings.js 2024-03-25 07:46:02.775 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [info] Context store : 'default' [module=memory] 2024-03-25 07:46:02.782 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [info] User directory : /opt/iobroker/iobroker-data/node-red/ 2024-03-25 07:46:02.786 - warn: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [warn] Projects disabled : editorTheme.projects.enabled=false 2024-03-25 07:46:02.796 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [info] Flows file : /opt/iobroker/iobroker-data/node-red/flows.json 2024-03-25 07:46:02.883 - warn: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [warn] Encrypted credentials not found 2024-03-25 07:46:02.964 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:02 - [info] Server now running at http://127.0.0.1:1880/ 2024-03-25 07:46:03.021 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:03 - [info] Starting flows 2024-03-25 07:46:03.341 - info: wled.0 (4890) WLED initialisation finalized, ready to do my job have fun ! 2024-03-25 07:46:04.281 - info: node-red.0 (4790) Node-RED: 25 Mar 07:46:04 - [info] Started flows 2024-03-25 07:46:06.282 - info: zigbee.0 (4854) Try to reconnect. 1 attempts left 2024-03-25 07:46:06.285 - info: zigbee.0 (4854) Starting Zigbee npm ... 2024-03-25 07:46:06.327 - info: zigbee.0 (4854) Installed Version: iobroker.zigbee@1.10.1 2024-03-25 07:46:06.728 - error: zigbee.0 (4854) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'" 2024-03-25 07:46:06.730 - error: zigbee.0 (4854) Failed to start Zigbee 2024-03-25 07:46:06.732 - error: zigbee.0 (4854) Error herdsman start 2024-03-25 07:47:29.452 - info: mqtt.0 (4860) Client [Schildkroeten] connected with secret 1711352849445_4891 2024-03-25 07:47:29.516 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/Schildkroeten/#" with regex /^cmnd\.Schildkroeten\..*/ 2024-03-25 07:47:29.518 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/Schildkroeten/#" with regex /^mqtt\.0\.cmnd\.Schildkroeten\..*/ 2024-03-25 07:47:29.521 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/tasmotas/#" with regex /^cmnd\.tasmotas\..*/ 2024-03-25 07:47:29.523 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/tasmotas/#" with regex /^mqtt\.0\.cmnd\.tasmotas\..*/ 2024-03-25 07:47:29.527 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/Schildkroeten_fb/#" with regex /^cmnd\.Schildkroeten_fb\..*/ 2024-03-25 07:47:29.529 - info: mqtt.0 (4860) Client [Schildkroeten] subscribes on "cmnd/Schildkroeten_fb/#" with regex /^mqtt\.0\.cmnd\.Schildkroeten_fb\..*/ 2024-03-25 07:47:29.533 - info: mqtt.0 (4860) Client [Schildkroeten] unsubscribes on unknown topic "homeassistant/status" -
@nftvirus sagte in Raspberry / iobroker absturz: Loading chunk 401 failed:
Nun habe ich in den letzten Tagen alles auf einer neuen SD Karte neu aufgesetzt
Und warum nimmt man dann nicht auch das aktuelle Betriebssystem als Basis?
-
@thomas-braun dachte eigentlich dass es aktuell war. Habe mich aber gerade bei der Analyse auch gewundert
-
Davon abgesehen ist vermutlich die Zeitzone falsch und nodejs/npm ist auch falsch.
-
@nftvirus sagte in Raspberry / iobroker absturz: Loading chunk 401 failed:
Previously detected issues:
~ Under-voltage has occurred
~ Arm frequency capping has occurred
~ Throttling has occurred
~ Soft temperature limit has occurredDa ist wohl ein neues Netzteil fällig.
Spiel da auf eine neue SD-Karte ein 64bit bookworm Image drauf.
-
@meister-mopper danke werde ich machen
-
@thomas-braun werde nochmal neu aufsetzen und ein neues Netzteil nehmen. Danke!
-
-
@thomas-braun wie gesagt ist eigentlich vor ein paar tagen vielleicht zwei drei Wochen frisch installiert keine Ahnung was ich da vergeigt habe. Aber auf jeden Fall danke für die Hilfe!
-
@thomas-braun sehe gerade dass mir der RPI imager für den 3b+ nur Bullseye anbietet. Mache ich da was falsch? Oder läuft Bookworm auf dem 3B+ nicht?
[edit] hat sich erledigt nehme ein Image von der RPI Seite ist laut der Seite für 3B+ zugelassen. Keine Ahnung warum es nicht direkt über den Imager angeboten wird.
