Jump to content

Emby server becomes unresponsive.


Recommended Posts

Posted

So, a couple weeks ago I had a hard time getting emby installed on this rig.  Ubuntu server 15.04.  Now I'm having an issue where it'll just either become responsive, or shuts down randomly.  Could be 10 minutes after starting, could be 36 hours later.  The only addon Im using is pushbullet.  I've tried both regular and beta servers, and the issue persists.  Sometimes "service emby-server restart" will work, sometimes not.  Sometimes I have to actually reboot the machine to get the program to start.  So how do I start tracking this down? 

Posted

What is your hardware for your server?

 

I had similar recently on my WHS machine and it was rendering the page without the options or open metadata; this is with a quad core Sandybridge Xeon and 8GB RAM. I've just reinstalled WHS2011 on a 256GB Crucial BX100 SSD and the difference is amazing. Library scans now don't hang the MB webpage and can transcode multiple streams at once

Posted

What is your hardware for your server?

 

I had similar recently on my WHS machine and it was rendering the page without the options or open metadata; this is with a quad core Sandybridge Xeon and 8GB RAM. I've just reinstalled WHS2011 on a 256GB Crucial BX100 SSD and the difference is amazing. Library scans now don't hang the MB webpage and can transcode multiple streams at once

 

 

This isn't that the hardware can't keep up, it's that the application is shutting down. It's not rendering pages because it's not running.

Posted

Any ideas, anything I can start with?

Posted

can someone point me towards where the logs are saved, so i can pull them?

Posted (edited)

Alright, made it almost 2 and a half hours before shutting down this time!

 

Looking at this log, it looks like something happens when trying to scan the watch folders, but Im probably reading it wrong.  Could use any help here, im lost.

 

 

Edit:   if the server log looks funky, I tried to delete a bunch of the filler (at one point it was 80 megs) that was just addresses to media.

server-63578079744.txt

unhandled_3dde464b-8f02-4043-8f0e-5ab7b317526d.txt

Edited by Zekesdad
Posted

you must have enabled the realtime library monitor because it's off by default for linux. turn it off and you should be fine. as mentioned in another thread, we're just going to take it away from operating systems where it's not known to be stable, so that you can't enable it in the first place.

Posted (edited)

you must have enabled the realtime library monitor because it's off by default for linux. turn it off and you should be fine. as mentioned in another thread, we're just going to take it away from operating systems where it's not known to be stable, so that you can't enable it in the first place.

I'll try that.  Will auto organize still work?

 

edit: and this used to work, the library monitor, until a few weeks ago.  or at the very least, it didn't shut the program down.

Edited by Zekesdad
Posted

ok, so got up this morning (having stopped the library watcher yesterday) and the program had once again shut down.

Posted

then we need to see logs again because that was clearly the problem from the previous log.

Posted

then we need to see logs again because that was clearly the problem from the previous log.

 

 

 

Ok.  I deleted the logs and restarted again just to make sure they're as clean as possible.  I'll post again when it dies.  And thanks again Luke for helping. 

Posted

some kind of out of memory problem. is this happening consistently? try turning off the auto-organize feature and seeing if the problem persists.

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
×
×
  • Create New...