Hello
Love the program and it seems to work most of the time. However I am noticing alot of instances were the episode is not on disk ( red in the schedule) however when I manually search, the episode is available and in the activity it says it was downloaded…but I see no record of it…here are some screen shots I hope might help.
http://imgur.com/kNHncpK ( Manual search shows it became available 10 days ago)
http://imgur.com/kNHncpK ( activity shows that it downloaded the file 10 days ago as expected)
However, the episode is not on disk, not in failed downloads either…its like it never existed.
This is true for SEVERAL episodes of various shows…the majority of the same series downloads just fine…ie I have episodes 1,2,3,4,6 but episode five did not work…
One error i see in nzb drone is “Enable Complete Download Handling if possible” i dont know if this could be the culprit but because most things work fine I dont know
Continuing from IRC, if you can get debug log files of that episode from tonight (during an RSS sync it may give us something to go on). Otherwise please add debug log files if/when it happens again.
Markus:
I appreciate the followup, it was late last night and the computer I was on decided to shut down abruptly for a windows update. My other rig ( nzb rig) has some kind of issue with java so I couldnt load the irc web based chat I also dont have an stand alone IRC client.
The plan for now is to let nzb run in debug logging mode, until we have a good example of the issue. Then pull that example out of the log since it would be way to long to post in it’s entirety.
Here is my question, the only way for me to SEE if the file that is missing from disk is available is to manually search for it through nzb drone…I assume when I do that it will add things to the log that relate to that file…is there anything identifying in the log that referances the actual first automatic pass not working, vs the manual search part…does that make sense?
Looking in the UI won’t log anything related to a file on the indexer, searching it will, which will clutter the logs a bit, but since its going to need to be on the indexer’s RSS feed so you get proper debug logs you’ll need to be keeping a fairly close eye on it. Checking nightly is going to be the best way to see if any releases for that night were missed.
You’ll see a message at the debug level that says: “Release rejected for the following reasons:” followed by a list of reasons, its going to log that every time it rejects a release (which is pretty common for series unknown).