Having a world of trouble with my Sonarr on Synology setup.
I installed Sonarr and configured it.
I then followed a guide to change the user that was running the app, so it is now running under the user “sonarr” which I created from the Synology console.
I change my /etc/passwd and added sonarr to users group.
I changed the startup script to make the USER variable “sonarr”.
It ran and worked great for a week, my server restarted and I noticed that Sonarr wouldn’t run, I tried everything, and noticed my changes to /etc/passwd had reverted. I had to change it again, ran Sonarr and all my settings were erased and I noticed the AppData directory is AppData directory
/root/.config/NzbDrone
What has gone wrong? I now placed my backup files in that folder, and my settings are back, but I feel like something is wrong and I will lose it again upon restart.
Can anyone help me debug and fix my install? I wanted to run it with a custom user so that I could manually give the user access to all the directories.
Is there a reason you did this? The defeult user for Sonarr is part of the sc-media group, so that group having the correct permissions should be enough.
I did this because when I installed the “nzbdrone” user was actually not part of sc-media. So I wanted more fine grain control of the user it would use.
Now with a “sonarr” user I can individually grant permission to that user to the correct directories.
But now everything seems messed up
Is there a reason my nzbdrone user was not part of sc-media?
It is, its just created in a way that is not visible to DSM (i’m not sure why that is the case, it just is).
Since everything is now in /root/ that means Sonarr is running as root, which means however it is being started has changed which user it is running as, has the startup script changed?
