Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systemd service won't start after mono update #2585

Closed
kaysond opened this issue Feb 27, 2018 · 18 comments
Closed

Systemd service won't start after mono update #2585

kaysond opened this issue Feb 27, 2018 · 18 comments
Labels
sonarr upstream Issue can / could be fixed by using Sonarr's code Type: Bug Issue is a bug

Comments

@kaysond
Copy link

kaysond commented Feb 27, 2018

Mono just got updated to 5.10.0.140 on Ubuntu 17.10. Now my radarr service doesn't start. The log says

Feb 27 13:00:16 fserver systemd[1]: Started Radarr Daemon.
Feb 27 13:00:16 fserver mono[4859]: Press enter to exit...

If I run /usr/bin/mono /opt/Radarr/Radarr.exe -nobrowser -data=/var/lib/radarr in a terminal, I get the same "Press enter to exit..." message

I have Radarr v0.2.0.980.

Obviously I can just roll back the mono version, but I'm wondering if this can be fixed...

@Animosity022
Copy link

There is a similar issue over here:

Sonarr/Sonarr#2431

I just rolled back my mono version for now.

@galli-leo galli-leo added Type: Bug Issue is a bug under investigation sonarr upstream Issue can / could be fixed by using Sonarr's code labels Feb 27, 2018
@galli-leo
Copy link
Contributor

According to taloth, an issue with NLog (always NLog 🤦‍♂️)

@Taloth
Copy link
Contributor

Taloth commented Feb 27, 2018

@galli-leo Not always. Jackett is having some Autofac issue on mono 5.10 😄

Btw. I pushed our (Sonarr's) fix to our develop branch, but gonna let it stay there for a day or two before I get it out to master.
I also put up a single file download at https://download.sonarr.tv/hotfixes/regression-mono-5.10/NLog.dll.gz but that's only for power users, ppl should stick with mono 5.8 till now.
The updated NLog version, seems to work for Sonarr and Radarr in docker container I used for the smoke tests, but don't know about actual usage.
The single file download can be handy though for ppl already on 5.10, so it gets back on the rails and is able to auto-update again.

@galli-leo
Copy link
Contributor

Ah thanks a ton for the testing and downloads!

@dutch2005
Copy link

thnx, used the NLog.dll , tested with 5.10 and 5.13 (nightly) and sonarr is working once more, once again ;)

@Taloth
Copy link
Contributor

Taloth commented Feb 28, 2018

@galli-leo fyi I just released to Sonarr master. I'll reply if issues come up.

@galli-leo
Copy link
Contributor

@Taloth Thanks! Just pushed a change, this should show up on nightly shortly.

@erickgrau
Copy link

Any chance anyone know how to request this update gets to Synology? I can't start Sonarr and it as well as Mono are running latest available versions. I think mono was updated and it broke Sonarr.

Help Please !

Synology 6.1.5-15254 Update 1
Versions grabbed from Package Center
Mono 5.8.0.108-11
Sonarr 20170106-9

Thanks,

Erick

@fryfrog
Copy link
Collaborator

fryfrog commented Mar 2, 2018

Mono 5.8 is fine for both Sonarr and Radarr, I've been using it for ages. This issue is specific to 5.10.

@fryfrog
Copy link
Collaborator

fryfrog commented Mar 2, 2018

@galli-leo: Fwiw, I don't see the fix coming through to nightly. Last one is Feb 28.

@betterbuckleup
Copy link

@galli-leo @fryfrog I second that, the update isn't showing up for me either

@attzonko
Copy link

attzonko commented Mar 2, 2018

You can manually grab NLog.dll until the fix arrives.

In the directory where you have Radarr installed just run:
wget -O - http://download.sonarr.tv/hotfixes/regression-mono-5.10/NLog.dll.gz | gunzip -c > NLog.dll

@samsepiol59
Copy link

@galli-leo how does your fix work? I mean, do I need to update radarr or something?! There's no new release!

@fryfrog
Copy link
Collaborator

fryfrog commented Mar 3, 2018

The fix didn't build, so it was reverted. Still needs to be done and released. :(

This issue should be un-closed. :)

@samsepiol59
Copy link

Ah ok, well thanks for the quickest answer ever! :)

galli-leo added a commit that referenced this issue Mar 3, 2018
Fixes #2585
Merge remote-tracking branch 'origin/develop' into develop


Revert "Fixed: NLog causing a crash under mono 5.10"

This reverts commit d11b565.

Added console logging in case NLog fails to initialize.

Fixed: Updated NLog to 4.5 RC6 to handle mono 5.10
Fixed: Messed up merge from Cherry pick


Fixed: Appveyor build.


Revert "Fixed: Appveyor build."

This reverts commit 9928235.

Revert "Fixed: Messed up merge from Cherry pick"

This reverts commit 450d905.

Revert "Fixed: Updated NLog to 4.5 RC6 to handle mono 5.10"

This reverts commit 1b20cbb.

Fixed: NLog causing issues with mono 5.10
@galli-leo
Copy link
Contributor

Well it's fixed now (at least on nightly)

@kaysond
Copy link
Author

kaysond commented Mar 3, 2018

@samsepiol59 You can grab this sonarr hotfix until the new release comes out - https://www.reddit.com/r/sonarr/comments/80ylur/new_sonarr_version_v2005183_and_mono_510_guide_if/

Basically download that new Nlog dll, and replace the old one, then restart

@samsepiol59
Copy link

Stupid question, I installed everything with atomic toolkit and set the develop branch for updates... How can I update to the latest nightly without being able to enter the gui?!

PS hope I'm not testing your patiences too much!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
sonarr upstream Issue can / could be fixed by using Sonarr's code Type: Bug Issue is a bug
Projects
None yet
Development

No branches or pull requests

10 participants