-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queue cleaning failed on formattedQueueInfo. (File: shared.py / Line: 128 / Error Message: 'downloadId' / Error Type: <class 'KeyError'> #63
Comments
Thank you for the details. could you please
this would give us way more logs and remove unecessary logs thank you |
Maybe I'm not running this right but this is my docker-compose
The container constantly restarts with these logs
Edit, it appears the container won't run with just lidarr configured. These are debug logs with radarr and sonarr as well as lidarr |
Thank you. I‘ll try to look into it on the weekend. |
ok few questions:
I will probably need to ask you a few more times to pull logs, please bear with me |
:latest w/ Sonarr + Lidarr: I'm not able to pull the dev image. (image: ghcr.io/manimatter/decluttarr:dev)
There only appears to be a single image on github and there are no tags in docker hub. edit: lidarr 2.1.7.4030-ls161 by linuxserver.io pulled using lscr.io/linuxserver/lidarr edit2: Cloned the dev branch and built the dev image :dev w/ only Lidarr: dev built image with debug logs using radar + lidarr: https://hastebin.com/share/ukohivohad.bash (cleaned up the download waiting to be imported in lidarr) |
This gets worse and worse 🤷♂️ |
you should now again be able to pull images. |
No. With lidarr and radarr commented out, I get the same logs
Decluttarr : dev image |
Super! I was hoping that‘d be the case. Will start digging |
I think I solved it. Could you please try to pull the dev image and verify? |
The container now starts with just lidarr (and just sonarr as well) configured. |
Hm. I think we are on to something here The below code shows that the lidarr queue API was successfully hit, but the response does not have the 'downloadId' key in it. According to the Lidarr API spec that should be there though.
Will try to find somebody from lidarr and ask Is there any reason that you can think of why this particular item would not have a downloadId? |
Lidarr 2.1.7.4030-ls162 (lscr.io/linuxserver/lidarr) Yes, that particular torrent likely doesn't have a download id because the torrent is currently 'pending' due to delay profiles in Lidarr. Edit: with that torrent completed, the logs look as intended, although there are currently no downloading items in lidarr
|
I wasn't even aware of the delayed profiles - functionality. learnt something new. I just added a piece of code that should hopefully deal with those delayed items. Are you able to again create a delayed lidarr-download, pull the "dev" version I just uploadeded, and post the logs (on debug level)? |
I seem to be running into a different error now that forces the container to exit.
The delay profiles are super helpful if you have private indexers. I prefer to dl what I can from usenet, but often the releases will first appear on private indexers, so I have delays in all the 'arrs. If the content doesn't show up within 12 hours, the torrent is processed, otherwise, the nzb will take priority and remove the torrent from pending. |
I am so sorry for the back and forth. I just uploaded a new version that should fix also the current_version problem. thanks for the explanation on the delay profiles and the new logs. |
The dev container now starts fine. From what I can gather, manually searched items don't adhere to the delay profiles. I believe they have to be from the RSS search. So, I haven't been able to get one from lidarr yet, but I do have some delayed downloads in sonarr so I've captured those debug logs: https://hastebin.com/share/iqedixisaz.markdown I trimmed them a bit, but let me know if you need more. |
Not sure I understand your reference to RSS searched items. From the logs, things look as if they are running fine now. Are you still experiencing any issues? |
There are 3 types of searches in the arrs. Interactive search where you pick the download, automatic search where the arr picks the download, and RSS which really isn't a search, but rather an RSS list of all torrents from every indexer that is parsed by the arrs. If something in your wanted list matches a parsed torrent from the RSS feed, it's added to the download queue. The RSS parsed torrents seem to be the only method that utilizes delay profiles. With that said, it does appear to be working as intended and I haven't seen any errors. If you want to close this, that's fine with me. I can open a different issue if I notice anything when lidarr does pick up a delayed torrent. |
understood. in theory, the way i implemented it should be agnostic about the method and should work in all 3 methods. thanks for your help with debugging this. quick one: i just pushed a (hopefully final) version, would you mind to once again post the logs of sonarr ? |
sure thing. here are the full logs from a startup with just sonarr enabled on the most recent dev image |
Looks splendid. thanks for the help. Merging to latest now and suggest we close this ticket, unless you need help with anything else? |
sounds good. If I notice anything else I'll open a new ticket. Thanks for the help! |
I just started decluttarr for the first time and ran into the following error. I saw a comment in #52 asking for a new issue so I opened this one. I will try out verbose logs to see if there is any other details.
Verbose Logs:
The stalled torrents were removed from qbit. I'm not sure if there is an API issue with lidarr, but it does seem to work as intended. Removed downloads were not immediately removed from lidarr queue, but replacement downloads had already been searched by the time the queue refreshed.
The text was updated successfully, but these errors were encountered: