[gelöst] FATAL ERROR: JavaScript heap out of memory
-
======================= SUMMARY ======================= v.2022-12-31 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Installation: Native Timezone: Europe/Berlin User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.19.0 /usr/bin/node v16.19.0 /usr/bin/npm 8.19.3 ioBroker Core: js-controller 4.0.21 admin 6.2.23 <--- Last few GCs ---> [5069:0x3fb7e58] 79610 ms: Mark-sweep 957.3 (968.9) -> 957.0 (974.7) MB, 119.3 / 0.0 ms (average mu = 0.259, current mu = 0.131) allocation failure scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: line 10: 5068 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker Status: Status admin: <--- Last few GCs ---> [5087:0x55d0e88] 79700 ms: Mark-sweep 957.4 (969.2) -> 957.1 (974.7) MB, 130.7 / 0.0 ms (average mu = 0.245, current mu = 0.137) allocation failure scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iobroker: line 10: 5086 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" <--- Last few GCs ---> [5103:0x5630ef0] 79383 ms: Scavenge 955.0 (967.1) -> 955.0 (968.1) MB, 3.7 / 0.0 ms (average mu = 0.509, current mu = 0.445) allocation failure [5103:0x5630ef0] 79516 ms: Mark-sweep (reduce) 960.9 (973.4) -> 960.6 (971.7) MB, 77.3 / 0.0 ms (+ 25.2 ms in 11 steps since start of marking, biggest step 18.0 ms, walltime since start of marking 133 ms) (average mu = 0.426, current mu = 0.351) final <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 10: 5102 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Pending iob updates: 0 <--- Last few GCs ---> [5118:0x4f3fef0] 79633 ms: Mark-sweep (reduce) 957.4 (969.9) -> 957.3 (968.2) MB, 32.2 / 0.0 ms (+ 37.2 ms in 22 steps since start of marking, biggest step 27.4 ms, walltime since start of marking 85 ms) (average mu = 0.411, current mu = 0.292) finali <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory /usr/bin/iob: line 10: 5117 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects: 0 States: 0 Size of iob-Database: 659M /opt/iobroker/iobroker-data/objects.jsonl 8.8M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ==================== -
@mwolle sagte in FATAL ERROR: JavaScript heap out of memory nach node Update:
659M /opt/iobroker/iobroker-data/objects.jsonl
zeige mal :
du -sh /opt/iobroker/iobroker-data/backup-objects/*objects*du -sh /opt/iobroker/iobroker-data/backup-objects/*objects* 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_07-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_09-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_11-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_13-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_15-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_17-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_19-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_21-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_23-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_01-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_03-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_05-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_07-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_09-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_11-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_13-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_15-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_17-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_19-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_21-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_23-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_01-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_03-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_05-51_objects.jsonl.gz -
du -sh /opt/iobroker/iobroker-data/backup-objects/*objects* 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_07-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_09-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_11-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_13-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_15-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_17-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_19-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_21-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-03_23-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_01-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_03-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_05-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_07-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_09-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_11-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_13-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_15-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_17-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_19-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_21-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-04_23-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_01-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_03-51_objects.jsonl.gz 1,6M /opt/iobroker/iobroker-data/backup-objects/2023-01-05_05-51_objects.jsonl.gz -
@glasfaser ich wollte es gerade ja updaten...Compression geht leider auch nicht (mehr)
Database maintenance (3/4) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl <--- Last few GCs ---> [6084:0x4474f28] 19212 ms: Scavenge 951.0 (962.6) -> 950.8 (968.4) MB, 6.0 / 0.0 ms (average mu = 0.708, current mu = 0.713) allocation failure [6084:0x4474f28] 19278 ms: Mark-sweep (reduce) 956.3 (973.7) -> 956.2 (966.7) MB, 35.9 / 0.0 ms (+ 2.7 ms in 5 steps since start of marking, biggest step 2.6 ms, walltime since start of marking 66 ms) (average mu = 0.672, current mu = 0.625) finalize <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory AbortedOder versucht mal (wenn npm>7 ist)
npm x --yes @iobroker/jsonltool@latest /opt/iobroker/iobroker-data -
Oder versucht mal (wenn npm>7 ist)
npm x --yes @iobroker/jsonltool@latest /opt/iobroker/iobroker-datanpm -v 8.19.3npm x --yes @iobroker/jsonltool@latest /opt/iobroker/iobroker-data Compressing /opt/iobroker/iobroker-data/states.jsonl Cannot compress states.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:78:17) Compressing /opt/iobroker/iobroker-data/objects.jsonl Cannot compress objects.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:93:17) No relevant JSONL files found to compress, skip -
npm -v 8.19.3npm x --yes @iobroker/jsonltool@latest /opt/iobroker/iobroker-data Compressing /opt/iobroker/iobroker-data/states.jsonl Cannot compress states.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:78:17) Compressing /opt/iobroker/iobroker-data/objects.jsonl Cannot compress objects.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:93:17) No relevant JSONL files found to compress, skipiob stoppen
und schauen ob noch Prozesse herumgeistern. -
iobroker stop cd /opt/iobroker/iobroker-data/ mv objects.jsonl objects.jsonl.old cd backup-objects/ gunzip -ck 2023-01-03_07-51_objects.jsonl.gz > /opt/iobroker/iobroker-data/objects.jsonl iobroker startiobroker stop cd /opt/iobroker/iobroker-data/ mv objects.jsonl objects.jsonl.old cd backup-objects/ gunzip -ck 2023-01-03_07-51_objects.jsonl.gz > /opt/iobroker/iobroker-data/objects.jsonl iobroker startdas scheint funktioniert zu haben, zumindest konnte ich jetzt Komprimieren und ein iob update klappte wieder
-
iob stoppen
und schauen ob noch Prozesse herumgeistern.@thomas-braun ja das hat sich mit dem anderem Verfahren überschnitten. Komprimieren klappte nun
-
Also ich fasse zusammen: Eine <770MB objects.json konnte bei 1,6GB "free" speicher nicht komprimiert werden? und iobroker war zu dem zeitounkt auch gestoppt? Was bracuht dann 2GB RAM ? aber naja ok... ihr habt es hinbekommen ... für mich passt da was nicht zusammen
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
Also ich fasse zusammen: Eine <770MB objects.json konnte bei 1,6GB "free" speicher nicht komprimiert werden? und iobroker war zu dem zeitounkt auch gestoppt? Was bracuht dann 2GB RAM ? aber naja ok... ihr habt es hinbekommen ... für mich passt da was nicht zusammen
@apollon77 sagte in [gelöst] FATAL ERROR: JavaScript heap out of memory:
für mich passt da was nicht zusammen
Stimmt, kam mir eigentlich auch seltsam vor.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden475
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge