Last update on Ubuntu-Server broke emby

[Bmuessig 0]

Since the last update emby does not work anymore. It seems like emby does not depend on a lot of packages anymore as about 180 packets were selected for auto-removal after I did the update to the latest emby. This includes the entire mono runtime. Now I have no clue anymore what belonged to emby and what didn't

It's an utter mess now. I did reinstall the mono-runtime again, because I need it for other things too and to try and fix emby.

Still emby is dead. I apt-get removed it and reinstalled it but nope. The connection on port 8096 is automatically refused and even manually starting emby won't work anymore (no error messages on stdout or stderr, but it just doesn't care about starting anything).

 

How can I downgrade to the last working update? AND why do you have to put out all these updates all the time?

It works and no update ever brought me anything interesting. Only trouble.

 

I am now purging mono entirely. I doubt a reinstall will work. I will try it anyways.

Edited August 31, 2016 by Bmuessig

[Bmuessig 0]

Look at this.

It works again after completely removing mono and emby, and then installing mono-complete (again) and after completing that, reinstalling emby-server.

Now I lost all my settings but it seems to work again.

 

Anyhow, emby itself is awesome, keep it up

Edited August 31, 2016 by Bmuessig

[Luke 42077]

Thanks for the info!

[Benkuly 3]

Today I made a fresh Ubuntu-Install and now emby doesnt start after fresh install. Remove/purge doesnt helped. There are no logs in der log folder.

Edit: same log like rafinha

Edited August 31, 2016 by Benkuly

[rafinha 8]

same issue here... fresh ubuntu and getting this:

cat /var/log/emby-server.log 
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) <0x41c1e0e0 + 0x00225> in <filename unknown>:0 
Could not load signature of Patterns.Logging.ILogger:FatalException due to: Could not load file or assembly or one of its dependencies. assembly:System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a type:<unknown type> member:<none>
exception inside UnhandledException handler: Object reference not set to an instance of an object

exception inside UnhandledException handler: Object reference not set to an instance of an object

[thatoneguy99 33]

Try this. It worked for me after the most recent Emby update.

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono...com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
sudo apt-get install mono-complete

Credit goes to seppi91

[weedos123 3]

Me too.  Original working ubuntu server 16.04 and like buessig, updated ubuntu and emby with the same results.  Emby log is the same as rafinha.

 

Tried what thateoneguy99 just posted and apt-get fails as presumably it does like the "mono....com" in the line beginning "echo..... "etc, what should it be instead of ........

 

Thanks

 

Found it, it should be 

 

"deb http://download.mono-project.com/repo/debian wheezy main"

 

 

It worked for me too.

 

If I remember correctly, not sure this is an Emby issue, perhaps and ubuntu upgrade issue.

When I ran apt-get update & upgrade, ubuntu offered me 154 files to update, I said yes and it said on 51 could be updated, the remainder would be held back.  It also said I could use apt autoremove to delete a load of mono files, which were extremely similar in name to the held back ones, so I ran it. Followed  it up by running apt-get upgrade again and it only updated the 51 files, leaving me without the ~120 files that reinstalling mono put back.

Edited August 31, 2016 by weedos123

[schamane 20]

So when will I be able to safely update?

[Benkuly 3]

If I remember correctly, not sure this is an Emby issue, perhaps and ubuntu upgrade issue.

Its seems to be Emby or missing dependencies in the deb-package, because last sunday with an "older" Emby-Version it works. Now it doesnt.

Edited September 1, 2016 by Benkuly

[hurricanehrndz 149]

Me too.  Original working ubuntu server 16.04 and like buessig, updated ubuntu and emby with the same results.  Emby log is the same as rafinha.

 

Tried what thateoneguy99 just posted and apt-get fails as presumably it does like the "mono....com" in the line beginning "echo..... "etc, what should it be instead of ........

 

Thanks

 

Found it, it should be 

 

"deb http://download.mono-project.com/repo/debian wheezy main"

 

 

It worked for me too.

 

If I remember correctly, not sure this is an Emby issue, perhaps and ubuntu upgrade issue.

When I ran apt-get update & upgrade, ubuntu offered me 154 files to update, I said yes and it said on 51 could be updated, the remainder would be held back.  It also said I could use apt autoremove to delete a load of mono files, which were extremely similar in name to the held back ones, so I ran it. Followed  it up by running apt-get upgrade again and it only updated the 51 files, leaving me without the ~120 files that reinstalling mono put back.

Please do not add mono's repo. We have mono in our repo and it's the recommended version. We do a lot of testing with different mono releases. You can run apt-get install mono-complete without adding mono's repos.

[Martum 2]

Was it really necessary to implement mono in your repository? My setup was running perfectly fine with emby and mono 4.2.3 but now it's unreachable after a few minutes. I'm currently on the move so I can't provide any logs or try to downgrade mono again. Why force a specific mono version? Why not just recommend one? People may also have other mono applications on their server which need another version. The administrators should decide themselves which one they install.

 

As I said, I will provide logs as soon as I am home again but now I can't watch anything while not at home. Never do updates before leaving the country, that's what I've learned now

[etique57 1]

It's really just a dependency problem.

 

Installed mono-complete (without reinstalling anything) and it solved the issue.

[cyrilr 0]

I have the same problem after ubuntu and emby updates. I have the same log than rafinha and the command : sudo apt-get install mono-complete, have solved my problem.