sb-discover-requests is not functioning properly
Posted by 2legit4u
My question: sb-discover-requests is not functioning properly SparkBox AI replied: Jellyfin looks fine, and the Discover container still isn't finishing its pass. - Jellyfin: It's up and accepting logins for the sparkbox account, with no errors. It's reachable. That doesn't prove the Discover pass is reading the library correctly, though. - Discover: I restarted the container once, as you asked. The log still shows only the start line, now from 11:28:22. No finish line, no count, no error. Doctor doesn't check this container, so it has nothing to add. So I can't tell you why it stops at 168, and I shouldn't have said earlier that the pass was still working toward a result. The logs don't show that. The "healthy" tag only means the process is running. The next step is Tom. Hit Share to demox below and include this: the Discover container logs one start line and never a finish line, the restart didn't change that, Jellyfin shows no errors, and the library shows 168. Tom can see the container code, which I can't. If you can, also tell me roughly how many movies and shows Jellyfin has, so we know whether 168 is a real limit or a short pass. What I still need help with: (describe what didn't work or what's still broken)
3 replies
Chris wrote:
I'm sorry. The SparkBox assistant gave you a wrong diagnosis in this thread. I can't find a limit of 168 anywhere in the Discover code, so please don't read anything into that number. Here is what the container does. It writes its start line once, then writes a line only when a pass adds, removes or requests something. A quiet pass is silent by design, so a start line with nothing after it doesn't by itself mean it is stuck. 'Healthy' means it finished a pass within the last 10 minutes. It doesn't show that the library count is right. The Share to demox button is real. It sends the chat to the SparkBox team privately. It doesn't change anything on your box, so it isn't a fix by itself. One check that shows which part is broken: tap the heart on one poster in the Discover & Request library in any Jellyfin app, wait about five minutes, and tell me whether that title now shows as requested in Seerr. Please also tell me your SparkBox version and what you expected to happen that isn't happening. We've logged this so the assistant's answer gets corrected for the next person.
2legit4u wrote:
Discover & Request (sb-discover-requests) shows 168 posters, and I want more. The container log has one start line and never a finish line. A restart didn't change that. Jellyfin shows no errors. My library is 52 titles (3 series, 49 movies). Is 168 a built-in cap, or does the pass stop early? My spakrbox version is 1.7.6 and pressing the heart button does send the request to seer
Chris wrote:
Thanks for checking, and I'm sorry for the wrong start in this thread. To your question: 168 is not a built-in cap. I can't find that number anywhere in the Discover code. Each refresh (every 6 hours) takes up to 40 movies and 40 shows from Seerr's own discover lists, skips anything already requested or available, and adds any new ones as posters. A poster that drops off those lists stays for up to 14 days before it is removed, so the total can go past 80. That is the likely source of your count, but I can't see your box, so I can't confirm it. A quiet log doesn't mean the pass has stopped. The container writes its start line once, then only logs passes that add, remove or request something. Problems show up as lines containing "pass failed", "WARN" or "waiting:". One read-only check: sudo docker logs --tail 300 sb-discover-requests | grep -E "pass failed|WARN|waiting" If it prints nothing, the worker is running without reported errors. If it prints lines, send them back with any titles or names removed. The 40-per-list number is set in the code, not in a setting, so there is no switch that shows more posters right now. A correction to my earlier note: Share to demox does two things. It opens a public post, and it sends a private copy of the conversation to the SparkBox team. It doesn't change anything on your box.