<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Backup Integrity check runs into oom]]></title><description><![CDATA[<p dir="auto">Two things:</p>
<p dir="auto">I have a Cloudron (9.1.7) with two backup destinations, one MinIO and a Hetzner Storagebox. Both are set up to backup the same things every day, 2 hours apart.</p>
<ol>
<li>For whatever reason the MinIO backup (which was the default and only backup for years) lists also stopped apps even though they're not included in the backup, both in size and # of apps.</li>
</ol>
<p dir="auto">Screenshot:<br />
<img src="/assets/uploads/files/1778755546191-82f76d83-5502-4441-bcc3-7b2f4675b6c0-image-resized.jpeg" alt="82f76d83-5502-4441-bcc3-7b2f4675b6c0-image.jpeg" class=" img-fluid img-markdown" /></p>
<ol start="2">
<li>When trying to do an integrity check on the MinIO backup, it says it crashed due to oom (ran out of memory or terminated). The server has plenty of RAM and the Storagebox integrity check works without problems.</li>
</ol>
<pre><code>May 14 12:32:47 tasks: startTask - starting task 12627 with options {}. logs at /home/yellowtent/platformdata/logs/tasks/12627.log
May 14 12:32:47 tasks: updating task 12627 with: {"pending":false}
May 14 12:32:47 shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 12627 /home/yellowtent/platformdata/logs/tasks/12627.log 0 400 0
May 14 12:32:50 apphealthmonitor: app health: 25 running / 5 stopped / 0 unresponsive
May 14 12:32:52 shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 12627 /home/yellowtent/platformdata/logs/tasks/12627.log 0 400 0 errored with code 9 and signal null timeout false terminated false - stdout: "Service box-task-12627 failed to run
Service box-task-12627 finished with exit code 2 and status 9
" - stderr: "Running as unit: box-task-12627.service; invocation ID: 7db618c2df95465c8db4534413f4f106
Finished with result: oom-kill
Main processes terminated with: code=killed/status=KILL
Service runtime: 4.670s
CPU time consumed: 3.777s
Memory peak: 400.0M
Memory swap peak: 55.7M
"
May 14 12:32:52 tasks: startTask: 12627 done. error: {
  message: 'Task 12627 ran out of memory or terminated',
  code: 'crashed'
}
May 14 12:32:52 tasks: setCompleted - 12627: {"error":{"message":"Task 12627 ran out of memory or terminated","code":"crashed"}}
May 14 12:32:52 tasks: updating task 12627 with: {"completed":true,"error":{"message":"Task 12627 ran out of memory or terminated","code":"crashed"}}
May 14 12:32:52 backups: startIntegrityCheck: task error. Task 12627 ran out of memory or terminated
</code></pre>
<p dir="auto">Could be that those 2 issues are related.</p>
]]></description><link>https://forum.cloudron.io/topic/15510/backup-integrity-check-runs-into-oom</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 12:47:22 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/15510.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 14 May 2026 10:51:55 GMT</pubDate><ttl>60</ttl></channel></rss>