Can't remove failed torznab downloads #869
Comments
|
PR(#870) will fix the problem with the failed downloads not being deleted. It looks like the reason why it wasn't able to delete them is because all of those items currently in your Failed list don't have a unique ID (they're all just All of your logs in your carepackage are in INFO level, but since you're primarly using torznab (and I don't) and if you're able and willing to of course - if you could change your logging to DEBUG level ( config.ini = |
|
#870 fixed the issue. Here's the relevant section with updated DEBUG level logs 29-Aug-2021 09:26:48 - DEBUG :: mylar.searcher.4006 : SEARCH-QUEUE : Torrent Provider: torznab This also gives me a little more indication where the breakdown is occurring trying to add the .torrent file to deluge. The connection passes the test built into the downloader page (which I'm assuming is verified by the "connected to deluge" line), but for some reason is unable to add the torrent. Any ideas? |
|
Did you enter in the deluge daemon port into mylar as opposed to the web ui port ? ( Go into Preferences / Daemon. Then enable the Daemon port and chose an appropriate port number and ensure that 'Allow Remote Connections' is enabled as well. Then Apply the settings. In Mylar, you enter in the url:port as the host entry (ie. thisis.deluge.com:22181 - don't precede it with a protocol either). Once you run the daemon once, the auth file is generated and from there you can edit the file manually and change passwords, or view what the username/passwords are - I believe it defaults to the username/password of whoever is running the Deluge daemon. So then just plunk in the username/password into Mylar, and save the config. |
|
I believe I have all of those things already set up and configured correctly. Here's some images just to verify. Torrent client config in Mylar & successful connection message Daemon config in deluge Contents of my Auth file I noticed that I had set up the mylar account as a regular user (5). I tried changing it to admin level (10) just to see if that fixed anything, but it didn't. |
|
For further testing, I also tried remote connecting from another instance of deluge to my main instance through the daemon port and adding a .torrent using the account in the auth file, and everything seems to be working as expected that way. For some reason there's some issue with the way mylar is attempting to add the .torrent |
|
Yeah I'd leave the user level at (5) - no point giving it admin access unless it's required (which it's not for this). The only other thing I can think of is if you have created a label |
|
The label was already set up so I could define a specific download directory within deluge. Could having it defined in deluge any Mylar cause any conflicts? |
IMP: changed Toggle Verbose button to (Enable / Disable) Debug Logging depending on logging level enabled IMP: added Clear All Specific Logs to Exceptions/Tracebacks option IMP: search-4-missing option added to series detail IMP: +mark option added for watchlisted series that have issues in a Skipped status on weeklypull IMP: series issues in Skipped status on the weeklypull colour-graded now IMP: allow metatagging to write out reading order sequence when dealing with multiple arcs IMP: option to toggle cherrypy logging via the config.ini (cherrypy_logging) FIX: CDATA element being returned by CV for Issue_Number results in error FIX: remove Add All to ReadingList option from series detail page (due to space) FIX: series issues in Skipped status on the weeklypull color graded now FIX: catch invalid name when deleting series via Delete Series FIX: correct some invalid css FIX: adjust column layouts for better fit on index page FIX: (#869) Unable to clear Failed downloads that have no ID value present FIX: RSS scheduled job was always in a running status, even if it was not FIX: corrected user-agent url FIX: downloading non-watchlisted arc issues would fail to be detected if items were not within a folder (ie. just a file) FIX: remove defunt deferrer usage and replace with inline FIX: unbalanced paranthesis error when using DDL and results include a pack FIX: DDL not being able to properly reference link FIX: newznab test option would incorrectly append api endpoint in some situations FIX: reworked newznab api url in search to better detect url's with api endpoint already included FIX: allow for enclosures URL as opposed to just using link field in provider response FIX: DBUpdater would not run every backfill_timespan interval (default 10 minutes) when updating large backlog queue FIX: Status' not indicated as Running in Activity/Jobs tab FIX: if the db updater was trying to backfill dates that fell within the problem dates array, would fail to compare and not update anything
I was in the process of trying to debug why I wasn't able to get my deluge integration to work, and came across an issue in which I'm unable to clear failed torznab downloads.
This portion of my log shows the torrent being marked as failed (Which I may open another topic for, since it's a different issue). But when I wanted to remove the failed download to debug a few things to see what was causing it to fail, it doesn't see the torrent anymore because it's marked as failed.
I attempted to go to the manage failed links page to remove the them so they wouldn't be ignored, however when I select them and choose "clear failed locks" from the dropdown, they just deselect and remain there. Originally when I did it there were some nzb files in there that were removed, so I know the selection button works.
CarePackage
carepackage.zip
Environment:
The text was updated successfully, but these errors were encountered: