Can you look at all of homarr’s logs?
Posted by Doc_Senna
My question: Can you look at all of homarr’s logs? SparkBox AI replied: 🔧 working on your SparkBox… 🔧 working on your SparkBox… Health check confirms it — sb-homarr is only up 2 minutes while everything else has been running 16-17. It's currently "healthy" because it just restarted itself, but based on the logs, it's on a loop. Rest of the fleet's fine, so this is isolated to Homarr. I'm not going to bounce it again — a restart won't fix a memory ceiling, it'll just buy you another few minutes before the same OOM happens. The real fix is raising the container's memory limit in the homarr module's compose file (currently capped, looked like 512M based on the last round of this). That's a manual edit though, not something I can push a tool at — I don't have an action for adjusting resource limits, only restarts and permission repairs. Given you already tried bumping the memory limit once before and it only helped temporarily, I'd bump it again (go higher this time — try 1G) rather than nudge it up incrementally. If it hits the ceiling again at 1G, that's worth flagging to Tom directly since 512M clearly isn't enough for Homarr's icon-cache + widget-prefetch workload on this box. I'm not confident a config bump alone is the permanent fix here since this is now a repeat pattern — click "Share to demox" below if you want this on Tom's radar for a real default-memory-limit fix in the module. What I still need help with: (describe what didn't work or wha …(reply truncated — full chat sent to Tom)
3 replies
Doc_Senna wrote:
I updated to the latest version about 17 min before this to see if it would fix homarr. It lasted about 5 min before I think it started looping again with restarts.
Chris wrote:
Thanks for sharing this, DocSenna -- the diagnosis lines up with what we've seen before. Homarr's memory cap is 512M right now, which was already a bump up from an earlier default that wasn't enough. Bumping it to 1G like suggested is a reasonable next step (that's a manual edit in the homarr module's compose file, nothing you can break by trying it). Since this is a repeat pattern for you even after one bump already, I've flagged it with Tom so we can look at raising the default for good instead of everyone hand-editing it.
Chris wrote:
Heads up — 1.6.547 just shipped and should cover what you reported here. You can grab it straight from the dashboard: Settings → Updates → Update SparkBox. Let me know if that sorts it, or if you're still hitting it. (Prefer the terminal? sudo sparkbox upgrade — note update only refreshes app images and will not move you to a new release.)