Radarr: Duplicates are continually being downloaded

Created on 2 Aug 2019  Â·  4Comments  Â·  Source: Radarr/Radarr

Describe the bug
Movies are being repeatedly downloaded, often at lower quality.

This happened after I upgraded from the 0.2.x series to the 2.0.x series.

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade from 0.2.x series to 2.0.x series
  2. Change no previous settings
  3. Movies which had previously reached the Profile cut off are continually downloading new version

Expected behavior
When a film is tracked and the Profile cut off has been reached new versions are no longer downloaded.

Screenshots
History

Manual Search

Files

Film Data

Profile

Desktop (please complete the following information):

  • OS: Docker 18.03.1-ce, build 9ee9f40 on Ubuntu 16.04
  • Mono Version: 6.0.0.313
  • Version: 2.0.0.1413

Debug Logs
debug logs

More Info
I noticed the Filesize for all affected films (and any others I check) is 0 B. Could that be related?

I'm running Radarr inside a Docker container on a Linux host with the files mounted from a Linux NAS via NFS.

On the Docker host the permissions are:
Film directory: drwxrwsr-x 1024 users
Film files: -rw-rw-r-- 1 1024 users

NAS permisssions:
Film directory: drwxrwsr-x admin users
Film files: -rw-rw-r-- 1 admin users

users has the GID 100 on both the Docker host and NAS.

I'm running the Radarr container with docker-compose and this config:

version: '3.6'

services:
  radarr:
    environment:
      - PGID=1000
      - PUID=1000
      - TZ=Europe/London
    image: linuxserver/radarr:2.0.0.1413-ls16
    ports:
      - "9003:7878"
    restart: unless-stopped
    volumes:
      - /home/henmunli/configs/radarr:/config
      - /mnt/downloads:/downloads
      - /mnt/media/Films:/movies

On the Docker host UID/GID 1000 is the primary user.

The 0B filesize indicator and line 142 of the gist (UpgradeAllowedSpecification|File is no longer available, skipping this file.) make me think this might be permissions related, however I can't find any specific log lines to back this up so it's definitely just a hunch.

Any help is much appreciated!

bug done aphrodite

All 4 comments

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.98. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

Thanks for the detailed report, 2.0 series is not ready for dedicated use, it should only be used for dev and testing right now.

@Qstick – thanks for the heads up, I should have paid closer attention! Is there a way to migrate my config from 2.x -> 0.2.x?

Unfortunately not. DB cannot be migrated backwards without alot of manual work

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DaveidWeba picture DaveidWeba  Â·  3Comments

feerlessleadr picture feerlessleadr  Â·  3Comments

christronyxyocum picture christronyxyocum  Â·  3Comments

alpinewinter picture alpinewinter  Â·  3Comments

Rouzax picture Rouzax  Â·  3Comments