Freshinstall Ubuntu 16.04 QB2.3.7 Sonarr doesnt work

complete fresh only changes made to box after QB install were fstab to include drives other then that nothing has been done. Ive waited for it to come up, ive turned it off/back on, restarted services(think only rutorrent/autodl?).
restarted server, and uninstalled/reinstalled.

Is it stating the service is enabled on your dashboard? I cannot seem to replicate any issues with this. The only issue I had noticed during the development and testing phase of including Sonarr was if you have your seedbox on a domain then this could cause an issue. However, connecting via http://_serverip_:8989 brings up Sonarr without issue.

I can start sonar thru cli by calling it with mono, however thru the dashboard and thru boot it doesnt hold thru.

Could you try to run the update from your dashboard and attempting it once more? I have tried this on 3 machines (different installs/hardware etc and cannot hit this issue)

It is possible, as the init.d script was botched on the initial push, that you may possibly have that version. It was the initial commit for v2.3.7 - which is to be officially announced tomorrow.

git pulled from dashboard as well as uninstall /reinstall. i ran top -u at the same time and i saw mono for a split second but that was it, after the install is done sonarr goes green but goes right to red afterwords.

Is the toggle sticking to the ‘On’ position?

That would essentially be like an sed command is writing itself without any request being made. I’m firing up a fresh install now and will try to reproduce this.

no its sticking to off, it flashes on right after install.

what is service sonarr status showing?

its showing on. but toggling it doesnt change the enabled/disable portion.

Could you PM me some details so I can check it out first-hand?

Flashes on then dies. Init.d script must be woking if it starts.

My money is on a bad configuration or a somehow missed depend… what OS are you running? The repo should grab what it needs as sonarr is repo based… stranger things have happened though. The output of “service sonarr status” would help a lot :wink:

Resolved: Fresh install didnt work Fresh install on vm did, time to start over.

1 Like