Quota exceeded on dataset applications/.system/cores

TrueNAS General
,
1

Hello,

Since installing 25.04.2.0 (and 25.04.2.1) I am getting this error on and off:

Quota exceeded on dataset applications/.system/cores. Used 92.45% (946.68 MiB of 1 GiB).

Currently I am getting it roughly every 10 minutes.
When looking at /var/db/system/cores however I only see 1 454K file:

core.systemd-journal.0.37b8320fa12d4fcd8c15caf931a30724.935.1755540885000000.zst

Which does not match the error, so it seems the system is systematically deleting the file or storing it elsewhere? I would like to see what apps are throwing errors and filling out the log.

Where can I find this log? How can I fix this error in general? What does it indicate?

2

Having logged into ssh as root I am getting these errors. That would explain why no log file is generated, however I am not sure what this is/

2025 Aug 21 21:24:08 borgcube Process 1167306 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 21:40:14 borgcube Process 1227479 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 21:56:06 borgcube Process 1287545 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 22:12:08 borgcube Process 1347718 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 22:28:16 borgcube Process 1408527 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 22:44:30 borgcube Process 1469560 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 23:00:26 borgcube Process 1531149 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 23:16:35 borgcube Process 1591833 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 23:32:49 borgcube Process 1657206 (node) of user 568 terminated abnormally without generating a coredump.
2025 Aug 21 23:48:58 borgcube Process 1716036 (node) of user 568 terminated abnormally without generating a coredump.
3

ok, resolved.

A custom app was throwing errors because node.js was running out of memory. I used the env variable NODE_OPTIONS=--max-old-space-size=4096 which increases the container’s NODE.js memory and resolves this.