Closed a10kiloham closed 6 years ago
I need to check who last changed the code because that PR fixed it. I will check soon and let you know.
That location is the show folder or the download folder?
That location is download folder. Every show is copied to the NAS under /mnt then symlinked
Can you run git commands?
Run inside Medusa folder:
git revert 088c6eaada435b76127f583c65279413b345ec8c
Restart medusa
I'm using the docker image so don't think git installed. Can try later tho
Can you edit the medusa *.py files?
Use this instead of your medusa/post_processor.py:
I will check tomorrow. But it's weird. When it started to happen? Does it happens for all files? All torrents and NZBs?
@bobbysteel have no clue why its not working anymore. Do you use Jackett ? I will need more info
Medusa stores info hash from torrent in the Snatch.
Can you open your main.db, history table and filter action column that ends with 02 and check if info hash is available?
Use SQLite DB Browser.
Send a screen shot of latest rows filtered by action ending 02
@bobbysteel like this:
@bobbysteel tell me the resource name from the last row that has a action ending with 02 and you know file got PPed. I think it's not finding info hash because resource name column (torrent name) is not the same as the torrent name (folder)
Just tell me the value in the resource name column
ok weirdly i found that particular one that threw an error but it doesn't end in 02 but 04. That resource matching the error above is action 104, resource /Media/Remote/tv/Acquitted/Acquitted S01 E10 (Finale) - Hardcoded Eng Subs - Sno.mp4, info_hash NULL
@bobbysteel still happening? If yes, can you manually snatch an episode, check in the DB if it has a info_hash in the action column that ends with 02 (snatch). then manually PP only that file and send the logs from the screen please?
Ok I've been able to reproduce.
Steps:
1) show is missing episodes, manual search not returning anything
2) I've found a matching torrent on another tracker, so I add the torrent manually
3) post-processing script (nzbToMedia) sends it to Medusa after downloading
4) Medusa throws error Unable to get info to move torrent later as no info hash available for:
It was never snatched as it was a manual add and call to postprocessor by other script. Seems this error should only be called when it's in reference to a torrent that was in fact first snatched.
That is expected. As I said before the info hash is stored in the Snatch. As you didn't snatch in Medusa, we don't know the info hash
So isn't the warning unnecessary then? I'd expect not to receive a warning in that case as nothing is technically wrong.
Well, it wasn't a snatch from Medusa, so it can't remove torrent from client. User is warned because torrent won't be removed so he can manually remove it
Wouldn't it be useful to add a check then to see if it was in snatches before warning? I can try and code this myself if that make sense
i will think about it
I'm getting this constantly now and can't figure out why. There was an earlier issue #3233 where @fernandog reported this and it seemed fixed, but I'm getting it now on files I've copied over from my remote seedbox as well as some torrents I've downloaded now.