tomspark wrote:
That's a solid repro — downloads that are already running resume, but fresh ones hang until you restart. Hitting it 3 times is significant. A few quick checks: (1) Does qBittorrent's WebUI show the torrent as added but stalled, or does it not appear at all? (2) Any disk-space concerns or I/O errors in the host/container logs around the time it hangs? (3) Sonarr/Radarr logs showing the qBit connection as OK when it fails? That pattern (restart fixes it, repeats after uptime) looks like a resource leak or connection pool issue. I'm flagging it with the team — this one's worth a proper fix, not just a restart workaround.
tomspark wrote:
Perfect—that stalled-on-add pattern is exactly what we need to track. When it happens again, grab docker logs sb-qbittorrent | tail -100 and docker logs sb-sonarr (or sb-radarr). Also note if disk space or memory looks tight at that moment. Post those logs here and we'll pinpoint whether it's a queue issue, resource constraint, or connection dropout.