Hi,
I recently switched from Sickbeard, especially for the failed episodes handling…
I installed Mono and Sonarr on my Synology NAS from the SynoCom packages.
version for Mono is 3.10.2
version for Sonarr is 20150104-4
after installation, it worked and i was able to set it up.
but i wanted to change the user that nzbdrone/Sonarr is running as because I have a user called “apps” for nzbget, couchpotato, etc. that has the permissions for writing to the correct folders.
So I edited the line in "/var/packages/nzbdrone/scripts/start-stop-status"
to USER=“apps”.
After rebooting the Synology, Sonarr wasn’t running so i tried to start it manually… but it does not seem to have an effect.
In the packages tab on my Synology, it still says the service is stopped.
the pkg log file says the following:
2015/01/17 15:27:38 start nzbdrone: begin to start version 20150104-4
2015/01/17 15:27:41 start nzbdrone: start version 20150104-4 successfully, result 0
Here are a few things to check:
Did you modify the /etc/passwd file to enable apps to have a login instead of “no login”?
Do you have user home folders enabled on your Synology?
Can you verify you have a folder by the name of apps in home folders?
Is there a .config directory inside apps?
Did you chown -R the install folder for sonarr in @appstore to give apps permissions to use it?
Modifying the script is only 1 step to get the proper user to work.
Here are some exact steps from a post on the sickbeard forums which walks you through the process:
Create a new user in your Synology Control Panel. I named mine “auto” (since it will be automating everything) and added the user to the group Users.
Make sure the apps you are going to edit are turned off from Synology Package Center. Don’t uninstall them, just make sure they’re “Stopped” instead of “Running”.
Now SSH or Telnet using PuTTY (or a similar program) to your DiskStation.
Edit your /etc/group file and if your newly created user isn’t added to the line that has users:x:100: go ahead and add him at the end.
Now edit /etc/passwd (very carefully, suggest making a backup first!) and find your newly created user at the bottom of the list.
On the line that has your newly created user, replace /var/services/homes/auto:/sbin/nologin where auto is the name of your new user with: /usr/local/sickbeard/var:/bin/sh
Now go to your sickbeard directory. This is located at /usr/local/sickbeard but this is just a symbolic link. The actual path is most likely at /volume1/@appstore/sickbeard
Type: chown -R auto:users /volume1/@appstore/sickbeard/ (be sure to replace auto with whichever username you chose, and users with whichever group you are using)
Now we edit the startup script that Sick Beard uses so that we can tell it to run as the new user.
Edit /var/packages/sickbeard/scripts/start-stop-status and find where it says RUNAS=“sickbeard” and change sickbeard to your user (in my case “auto”).
You will now repeat steps 7-10 for each of the following programs: SABnzbd, Transmission, and Couch Potato changing the directory to match the program you’re working on.
After you’re done, reboot the Synology NAS and try downloading a file. You shouldn’t have any more permission errors.
I’ve done all of that. But whenever there is an issue with sonarr and I need to reset the program, stopping and then restarting never ever works 1st time. I either have persevere attempting restarts between 5-50 times or restarting the whole server, both of which are counter-intuative.
I had been using it for a good 7 months on my Synology server, but recently for some reason it’s been acting really funny (as stated above)
Updated it last night and do you think I can get the thing to run at all??
No support in these forums at all (I know it’s a free software and all of that, but not acknowledgement), I’m hoping to get SickBeard up and running cos I can’t go on like this no longer…
Honestly, its not even clear what your issue is. The thread was started by one user and you said you to need to restart 5-50 times to get it to work.
What is the issue?
We have dozens of users running on Synology without issues, but too my knowledge they have not attempted to alter how its run, since that’s not an issue with Sonarr, but with how its being run there is a limited amount we can do.
The nuts and bolts of the issue is for some reason it won’t start at all now and recently before last nights upgrade it was running in the background with no web access through Chrome or Safari.
The initial post seems pretty clear to me, which are the exact issues I’ve been having with my install. You install it, change app permissions, so that the program has the able to write to the drives, but when trying to start the program it doesn’t seem to want to play ball. As I said I could be sitting there and try to Run the program over 50 times with no success, which to me is a considerable issue. Considering I ran SickBeard this morning with 1 click…
Taking a guess here, because there’s nothing to work with: you installed via synocommunity’s package?
I’m running sonarr without issues on my synology for a long time now, but I’m still using and old, self-compiled syno package and I’m not touching it because I can’t be bothered. Once it’s installed, there is nothing to be gained by updating the synocommunity package. Sonarr can update itself to a new version on synology, and the only thing the synocommunity package upgrade will do for you is break things you may have customized (such as the user running the application).
Have you tried removing the package and installing it again? And I mean remove properly. Check for leftover dirs, config files, …
Then install the package from synocommunity from scratch. Don’t change a thing. Just see if you can run sonarr succesfully. Don’t worry about the folder permissions yet, or adding series, or anything. Just see if you can start the application and open it in your browser.
If you must, go from there and follow the various guides floating around how to change the user running sonarr on your synology. Keep track of what you changed and how. If it breaks, post relevant details.
You can also check the synocommunity github pages, there’s plenty of people running sonarr with a different user.
Thirrian, it’s far from “I can’t be bothered” attitude thanks. I was under the impression that upgrading the SynoCommunity package was updating everything not just the package itself.
Granted I’m not the best with terminal, but I will and do use any resource I can find to get my way around the various guides out there, all I need is the constructive guidance and I’ll be on my way.
I was not looking to removing every existance of the install, knowing the pain I’d gone through to initially set it up and this was very much a last resort option, but if the consensus is of this opinion that there nothing else to try, then I may give it a go.
I checked the log file in the directory stated above, but there was nothing written to it after Jan 8th, even though it has been running up until yesterday?
Ok, please excuse my ignorance. I’m looking in the SynoCommunity package through DSM and the Sonarr package I have is the most recent version (2015021305).
Are you saying I need to install the update once that package is up and running through the GUI?
If so, as stated above I can’t get the package to run. Is there an alternative method?
in that case, somehow the