tom472 / mediabox

Container based media tools configuration
MIT License
428 stars 83 forks source link

NZBGet #121

Closed rickyxnguyen closed 3 years ago

rickyxnguyen commented 3 years ago

When downloading a show Sonarr can’t pick up the download after it finishes

rickyxnguyen commented 3 years ago

Only occurs when using usenet

tom472 commented 3 years ago

Hmm -- I have no way to test that - no usenet access. But I'll recheck the folder mappings and make sure they have the correct entries.

tom472 commented 3 years ago

So I did some checking to lay it out:

The docker-compose file maps this volume for NZBGet: ${DLDIR}:/downloads
${DLDIR} should equate to [path]/mediabox/content

NGBGet has MainDir: Root directory for all tasks.
/downloads so from above would equate to [path]/mediabox/content

Then has DestDir: Destination directory for downloaded files.
${MainDir}/completed which would equate to [path]/mediabox/content/completed

Then has InterDir: Directory to store intermediate files
${MainDir}/incomplete which would equate to [path]/mediabox/content/incomplete

Sonarr has this volume mapped in the docker-compose file: ${DLDIR}/completed:/data/completed
Which again equates to: [path]/mediabox/content/completed

So all of the path mappings appear to match up and be correct -- Are the files ending up anywhere?
Like still sitting in:
[path]/mediabox/content/incomplete
or
[path]/mediabox/content/completed

Also -- anything showing in the logs for NZBGet?

Let me know - Hope we can figure this out.

rickyxnguyen commented 3 years ago

It sits in the mediabox completed box

On May 27, 2021, at 23:28, Tom Morgan @.***> wrote:

 So I did some checking to lay it out:

The docker-compose file maps this volume for NZBGet: ${DLDIR}:/downloads ${DLDIR} should equate to [path]/mediabox/content

NGBGet has MainDir: Root directory for all tasks. /downloads so from above would equate to [path]/mediabox/content

Then has DestDir: Destination directory for downloaded files. ${MainDir}/completed which would equate to [path]/mediabox/content/completed

Then has InterDir: Directory to store intermediate files ${MainDir}/incomplete which would equate to [path]/mediabox/content/incomplete

Sonarr has this volume mapped in the docker-compose file: ${DLDIR}/completed:/data/completed Which again equates to: [path]/mediabox/content/completed

So all of the path mappings appear to match up and be correct -- Are the files ending up anywhere? Like still sitting in: [path]/mediabox/content/incomplete or [path]/mediabox/content/completed

Also -- anything showing in the logs for NZBGet?

Let me know - Hope we can figure this out.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

tom472 commented 3 years ago

OK so NZBGet appears to be doing the correct steps and getting completed downloads to the completed folder.
Are there any errors in the Sonarr logs related to post-processing for getting the items to the TV folder?

archshift2 commented 3 years ago

There are some inconsistencies in the yml file. Some of the directories use /downloads some use /data and some use /media. It would be nice to re-write the yml file and be consistence across all the platforms, but unfortunately an update like that would break everyone existing install base. There is a way to fix this within sonarr, add a remote path mapping in the download client section.

Remote Path: /downloads/completed/ Local Path: /data/completed/

You might also want to consider using the category tag within sonarr & radarr to help them from stay organized (same with deluge as well).

tom472 commented 3 years ago

@RickyxNguyen -- any chance the recommendation from @archshift2 helps/helped with the issue?

rickyxnguyen commented 3 years ago

I haven’t had the chance to try it out yet but I will let you know the minute I get it done

On Jun 1, 2021, at 14:05, Tom Morgan @.***> wrote:

 @RickyxNguyen -- any chance the recommendation from @archshift2 helps/helped with the issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

rickyxnguyen commented 3 years ago

Worked perfectly

tom472 commented 3 years ago

Excellent .. thanks!