Jump to content

Emby crashing on startup (Ubuntu 14.04)

bishop

By bishop
in Linux

 Share

Recommended Posts

bishop

bishop   12

Posted
Posted (edited)

All but one of my logs are <20kb in size and the service crashes immediately upon start.

 

I recently tried dist-upgrading to the latest version of mono (4+) to fix some Sonarr and Emby issues but have since reinstalled both services fresh without the mono ppa. I've been having issues with stability for a while but never reached out.

 

My library was just imported last night and I was troubleshooting Kodi addon issues when this started happening again.

 

embycrash3.log is the first, chronologically.

Edited by bishop
Link to comment
Share on other sites
Luke Emby Team

Luke   37064

Posted
Posted

I don't see anything in those logs that would cause a crash. It looks like you have metadata saving in media folders enabled but the server doesn't have access to write to those folders. That's just an fyi, shouldn't cause a crash.

 

Have you tried mono 3.10? that seems to be the most stable right now. Also there is this that I found quite interesting:

 

http://emby.media/community/index.php?/topic/19955-emby-crashing-ubuntu-server/?p=207271

  • Like 1
Link to comment
Share on other sites
bishop

bishop   12

Posted
  • Author
Posted

So then it may be a mono issue rather than an emby or sonarr issue? Would that be why nothing within the logs that I provided (now deleted) didn't indicate a crash?

 

That's good to know-- of course the day that I finally post about it is the day that Taloth posts his findings. Just my luck. :)

 

Thank you for helping me.

Link to comment
Share on other sites
thefirstofthe300

thefirstofthe300   291

Posted
Posted

So then it may be a mono issue rather than an emby or sonarr issue? Would that be why nothing within the logs that I provided (now deleted) didn't indicate a crash?

 

That's good to know-- of course the day that I finally post about it is the day that Taloth posts his findings. Just my luck. :)

 

Thank you for helping me.

 

Actually, that thread states that the issue is in the kernel. As soon as Ubuntu pushes a new kernel to there production repos, that issue will be fixed.

  • Like 1
Link to comment
Share on other sites
Luke Emby Team

Luke   37064

Posted
Posted

Yea but it's always possible that an older version of mono might not call whatever method triggers the problem. Could provide a workaround in the meantime.

  • Like 2
Link to comment
Share on other sites
Poptartica

Poptartica   12

Posted
Posted (edited)

I was getting a similar problem, crash on startup. I didn't even upgrade my kernel...

have no idea why that started ... tried to reinstall mediabrowser, nope. PPAs were going haywire (conflicting repo's even after I cleaned out any other references to mono in my sources list), etc etc.. the instructions on the download page seem to be outdated or not valid for a few different ubuntu versions (mint 17.1/ubuntu14.04)..

tried to manually install, nope. login page led to an HTTP Get error. Re-checked my dll references, and they were indeed to the ones I had.

 

Tried to update mono, nope, v. 4 is what the xamarin repo was handing out and that just flat out wouldn't start emby. Removed that and tried to go to 3.10, that didn't work either and the 3.10 install was giving me missing dependencies (libmono/mono-devel) errors when I tried to install mediabrowser (note this is following the exact directions on the download/install section).

 

So essentially went from working just fine a day ago to crashing 10 seconds after start with no kernel or mono updates between the two, then to unable to even launch :o I've since upgraded my kernel wondering if whatever I had was just incompatible with the mono versions I was getting, but, that wasn't it either.

 

(note that before this, I was running on mono 3.12.1, and that was actually the most stable I've ever had Emby/MB, with no errors or etc, for the longest time)

Edited by Poptartica
Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted

The instructions on the page are correct for the moment, the conflicting repo is a know issue with using snapshots from the ppa, this is a commonly documented issue.

http://emby.media/community/index.php?/topic/19581-debian-install-fail-are-not-allowed-when-publishing-distributions/

 

If you like you can test a new beta repo. PM if you are interested.

Link to comment
Share on other sites
Taloth Saldono

Taloth Saldono   4

Posted
Posted

You restarted your system? Coz the kernel could've been installed a while ago but never used coz that takes a reboot.

Link to comment
Share on other sites
Poptartica

Poptartica   12

Posted
Posted (edited)

The instructions on the page are correct for the moment, the conflicting repo is a know issue with using snapshots from the ppa, this is a commonly documented issue.

http://emby.media/community/index.php?/topic/19581-debian-install-fail-are-not-allowed-when-publishing-distributions/

 

If you like you can test a new beta repo. PM if you are interested.

 

Thanks for pointing that out! I understand much better now. I'll definitely be hitting you up for that :)

 

You restarted your system? Coz the kernel could've been installed a while ago but never used coz that takes a reboot.

 

Hello Taloth, I did restart my system, but that's definitely worth checking since I know in the past that's been the dealbreaker for some issues I've encountered. It was originally showing as being on kernel 3.13.0-37 when I first encountered the issue. It now has installed and loaded kernel 3.13.0-46, and the issue is still occurring.

 

Thanks as always for checking in on these issues guys, it's really appreciated! I'm glad Emby and Sonarr are both growing really fast, you guys have always handled any wrinkles (even user related ones) very fast.

Edited by Poptartica
Link to comment
Share on other sites
Taloth Saldono

Taloth Saldono   4

Posted
Posted

It shouldn't crash that easily on -46. So it might be another problem. I hope -54 comes out soon so we know for sure.

Link to comment
Share on other sites
bishop

bishop   12

Posted
  • Author
Posted

Taloth,

 

Due to an unrelated situation I wiped my server yesterday and reinstalled 14.04 and created what I'd consider my stock image in case anything goes wrong.

 

The kernel that automatically installed is 3.16.0-37-generic. I believe that may be the kernel that Poptartica was referencing but stated 3.13.0-37 instead.

 

The issues are present on this kernel as well. I know that the error you submitted was for 3.13.0-46+ but will the fix be included in the 3.16 line?

Link to comment
Share on other sites
Taloth Saldono

Taloth Saldono   4

Posted
Posted

The kernel that automatically installed is 3.16.0-37-generic. I believe that may be the kernel that Poptartica was referencing but stated 3.13.0-37 instead.

 

The issues are present on this kernel as well. I know that the error you submitted was for 3.13.0-46+ but will the fix be included in the 3.16 line?

 

New trusty (14.04.2) installs get the utopic kernel (3.16) via the LTS enablement stack.

 

And, yes, it will be fixed for utopic (and vivid) as well.

 

But Poptartica mentioned both 3.13.0-37, 3.13.0-46.

While the first could be a typo (3.16.0-37), the second cannot coz there is no 3.16.0-46.

 

Nor does it matter much, whether it's the same issue or not, you still want the fix installed before investigating other potential causes.

Link to comment
Share on other sites
emamid

emamid   0

Posted
Posted

I'm not sure if this is the same issue or not, but I'm getting frequent crashes on Ubuntu 14.04.2, and usually the last thing I see in the log is:

2015-05-17 16:03:00.3070 Info - App: HttpClientManager POST: http://www.mb3admin.com/admin/service/registration/ping
2015-05-17 16:03:00.9416 Error - HttpAsyncTaskHandler: Error occured while Processing Request: Access token is invalid or expired.
	*** Error Report ***
	Version: 3.0.5607.2
	Command line: /opt/mediabrowser/MediaBrowser.Server.Mono.exe -programdata /var/lib/mediabrowser
	Operating system: Unix 3.16.0.37
	Processor count: 4
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/mediabrowser
	Mono: 3.10.0 (tarball Wed Nov  5 12:50:04 UTC 2014)
	Application Path: /opt/mediabrowser/MediaBrowser.Server.Mono.exe
	Access token is invalid or expired.
	MediaBrowser.Controller.Net.SecurityException
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken (IServiceRequest request, System.String token) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateUser (IServiceRequest request, IAuthenticationAttributes authAttribtues) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.Authenticate (IServiceRequest request, IAuthenticationAttributes authAttribtues) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Controller.Net.AuthenticatedAttribute.RequestFilter (IRequest request, IResponse response, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.ServiceStackHost.ApplyRequestFiltersSingle (IRequest req, IResponse res, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.ServiceStackHost.ApplyRequestFilters (IRequest req, IResponse res, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.Host.RestHandler.ProcessRequestAsync (IRequest httpReq, IResponse httpRes, System.String operationName) [0x00000] in <filename unknown>:0
Link to comment
Share on other sites
Luke Emby Team

Luke   37064

Posted
Posted

 

I'm not sure if this is the same issue or not, but I'm getting frequent crashes on Ubuntu 14.04.2, and usually the last thing I see in the log is:

2015-05-17 16:03:00.3070 Info - App: HttpClientManager POST: http://www.mb3admin.com/admin/service/registration/ping
2015-05-17 16:03:00.9416 Error - HttpAsyncTaskHandler: Error occured while Processing Request: Access token is invalid or expired.
	*** Error Report ***
	Version: 3.0.5607.2
	Command line: /opt/mediabrowser/MediaBrowser.Server.Mono.exe -programdata /var/lib/mediabrowser
	Operating system: Unix 3.16.0.37
	Processor count: 4
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/mediabrowser
	Mono: 3.10.0 (tarball Wed Nov  5 12:50:04 UTC 2014)
	Application Path: /opt/mediabrowser/MediaBrowser.Server.Mono.exe
	Access token is invalid or expired.
	MediaBrowser.Controller.Net.SecurityException
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken (IServiceRequest request, System.String token) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateUser (IServiceRequest request, IAuthenticationAttributes authAttribtues) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.Authenticate (IServiceRequest request, IAuthenticationAttributes authAttribtues) [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Controller.Net.AuthenticatedAttribute.RequestFilter (IRequest request, IResponse response, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.ServiceStackHost.ApplyRequestFiltersSingle (IRequest req, IResponse res, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.ServiceStackHost.ApplyRequestFilters (IRequest req, IResponse res, System.Object requestDto) [0x00000] in <filename unknown>:0 
	  at ServiceStack.Host.RestHandler.ProcessRequestAsync (IRequest httpReq, IResponse httpRes, System.String operationName) [0x00000] in <filename unknown>:0

 

That's not going to crash the server. I would read this:

 

http://emby.media/community/index.php?/topic/19955-emby-crashing-ubuntu-server/?p=207271

Link to comment
Share on other sites
bishop

bishop   12

Posted
  • Author
Posted (edited)

To resolve this:

 

32 bit:

Download the .deb packages.

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-headers-4.0.4-040004_4.0.4-040004.201505171336_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-headers-4.0.4-040004-generic_4.0.4-040004.201505171336_i386.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-image-4.0.4-040004-generic_4.0.4-040004.201505171336_i386.deb
Install them. 
sudo dpkg -i linux-headers-4.0.4*.deb linux-image-4.0.4*.deb
For 64-Bit Systems

Download the .deb packages.

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-headers-4.0.4-040004_4.0.4-040004.201505171336_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-headers-4.0.4-040004-generic_4.0.4-040004.201505171336_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/linux-image-4.0.4-040004-generic_4.0.4-040004.201505171336_amd64.deb
Install them. 
sudo dpkg -i linux-headers-4.0.4*.deb linux-image-4.0.4*.deb
 
To uninstall:
sudo apt-get remove 'linux-headers-4.0.4*' 'linux-image-4.0.4*'
 
Reboot and use GRUB to boot into 4.0.4.
 
I can run the mono bug-~.exe from the other thread for several hours without a crash. It was crashing within 10 seconds before.
Edited by bishop
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...