yes
Posted by cherett80
My question: yes SparkBox AI replied: 🔧 working on your SparkBox… Didn't take clean. Given the container's own logs show nothing wrong — no error, no OOM, just repeated 13-minute clean boots — bouncing it again is unlikely to hold, since whatever's cycling it (a healthcheck, restart policy, or the same external stop event that hit qBittorrent/Prowlarr/Seerr) is still there and will just cycle it again. At this point I'm out of moves that are just going to be guessing — this is a pattern (restartcontainer success rate is only ~53% fleet-wide, and this one didn't even complete) not a straightforward config fix. Two things worth doing: 1. Check docker ps yourself for sb-flaresolverr's actual restart count/uptime right now — if it's sitting at a few seconds of uptime repeatedly, that's Docker's own restart policy or a healthcheck failing it, not FlareSolverr. 2. This is worth a "Share to demox" — a container cycling every ~13 min with completely clean logs each time (no error to chase) alongside three other containers getting SIGTERM'd around the same window smells like something bigger than a single app wedge, maybe host memory pressure or a stuck update job. Tom's crew should see the pattern across your whole fleet, not just this one container. What I still need help with: (describe what didn't work or what's still broken)
2 replies
Chris wrote:
Hey cherett80 — thanks for sharing this, and your SparkBox AI's read on it lines up with what we'd want to check too. One container cycling with totally clean logs, right alongside a few others getting stopped in the same window, does point at something bigger than one app wedged. If you get the chance, the uptime/restart count for sb-flaresolverr from docker ps would help narrow it down. I've flagged the pattern with Tom so it gets looked at across the fleet, not just your box.
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.)