mirror/Radarr
1
0
Fork 0
mirror of https://github.com/Radarr/Radarr synced 2024-12-22 07:52:34 +00:00
Code Issues Releases Wiki Activity

Added section about hardlink protections in debian linux

Hayden Andreyka 2019-12-16 21:56:08 -07:00
parent b531e1088f
commit a749c52082
1 changed files with 30 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
Common-Problems.md

@ -198,3 +198,33 @@ Use the Movie Editor to fix paths of existing movies.
![Settings](https://i.imgur.com/owNqa3s.png)
* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.
## Radarr is not picking up completed downloads / "Check For Finished Download" task hangs forever
On Linux (primarily Debian-based) systems, hardlinking files requires ownership permissions by default. If you are running your download client as a daemon under a separate user from Radarr (best practice), Radarr will not be the owner of the downloaded files by default and therefore will be unable to make a hardlink into your Movies folder.
To fix this, you can either make Radarr the owner of the downloaded files or you can disable the hardlink protection in Linux.
### Option 1: Making Radarr the owner of the files
This is probably better than disabling hardlink protection, but in my experience I was unable to get group ownership (adding the same primary group to both the radarr and download daemon user) to work. Your alternative is to run radarr and your download client under the same user.
1. Find the service file for your Radarr and download client by running `sudo service <service> status` and looking at the output as shown:
![](https://tkno.pw/38P1kyy)
2. Open up the service file and make your modifications to the daemon user. Either set both users the same, or both groups the same. (Or all the same)
![](https://tkno.pw/38L0v9W)
3. Now reload your daemon or reboot the server. With systemctl, you want to run `sudo systemctl daemon-reload` and restart the services as well.
### Option 2: Disabling hardlink protection
To avoid the mess with users and group permissions, you can disable the hardlink protection feature that causes the issue in the first place.
1. Open up `/etc/sysctl.conf` in your favorite text editor
2. Uncomment/change/append this in the file: `fs.protected_hardlinks = 0`
3. Run `sysctl -p` to apply your changes.
[Source for hardlink protection](https://unix.stackexchange.com/questions/209309/hard-link-permissions-behavior-different-between-centos-6-and-centos-7/209452#209452)