emby server unresponsive

[revengineer 142]

My windows emby server is repeatedly becoming unresponsive overnight. That is, the website no longer loads on the clients including in a web browser running directly on the server. If that happens, the service cannot be shut down. While the service control panel allows stopping the service and then reports as stopped, the underlying application does not shutdown even after waiting for several minutes. The application also cannot be stopped with admin privileges through the taskmanager or taskkill. Only a server reboot, which is extremely disruptive in a domain environment, brings emby back to life. If I remember correctly, this behavior has started with build 5911. The log is attached. hoping for a quick fix as this bug renders emby unusable on my network. Thank you in advance.

emby.log

Edited April 17, 2016 by revengineer

[Luke 42078]

hi, as a test, can you try removing cover art and let me know if that has any impact?

 

if not, then please provide entire server logs from the time it went unresponsive. thanks.

[revengineer 142]

Will try without coverart and report back. The attached log however was complete. I tried loading the web interface at ~9:30. I tried several clients to no avail. The attempts to load the emby web page do not even show in the logs. Then I tried to shut down at 9:37, and there are some entries related to this. However, the mediabrowser application never shut down.

[revengineer 142]

I turned coverart off. But before I could do so I had to reboot the server again because the admin website would not load. The log is attached. I tried to load the website at ~16:40, which is again not shown in log file.

emby2.log

[Luke 42078]

Can you define would not load? Can you describe that a little? thanks.

[SikSlayer 249]

I am having the same issue....will post a log in a moment but for now, the server is running in my tray, and I can't log into it.

The dashboard, nor front pages load up. No apps can access it.

 

Here is the log: server-63596516688.txt

Edited April 17, 2016 by SikSlayer

[SikSlayer 249]

Actually, I notice now that anything that tries to log in crashes the server.

Here's a log file of that happening: server-63596516688-NEW.txt

[Luke 42078]

Actually, I notice now that anything that tries to log in crashes the server.

Here's a log file of that happening: server-63596516688-NEW.txt

2016-04-17 19:04:54.5427 Error ServerManager: The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

[SikSlayer 249]

A simple reboot was all it took.

...............WTF is that *^&% about?! 

 

In any case, thanks.

[revengineer 142]

Can you define would not load? Can you describe that a little? thanks.

None of the emby ui shows in browser. Browser does not time out, spins wheel indicating that it keeps trying to load.

 

After disabling coverage, emby server is still responsive this morning. Maybe the recent coverlet update introduced the issue. Will keep monitoring and report back if anything changes.

[revengineer 142]

 

2016-04-17 19:04:54.5427 Error ServerManager: The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

This is very clearly not my issue and if problems persist should be pursued in a separate thread.

[ebr 16181]

A simple reboot was all it took.

...............WTF is that *^&% about?! 

 

In any case, thanks.

 

Next time it happens, see if there is an ffmpeg process running (without someone actually streaming something).

[revengineer 142]

Next time it happens, see if there is an ffmpeg process running (without someone actually streaming something).

This does also not apply to the OPs issue.

[revengineer 142]

At this point, the server is still responsive pointing increasingly to an issue with coverart.

[Luke 42078]

Thanks for the info.

[revengineer 142]

I was wrong. Got home from work and the server was out to lunch again. So it's not coverart. So it happened between 2 pm and ~6:30 pm. The logs is attached. I now updated to v5930 so see if that makes a difference.

 

There should really be an option to not autoupdate. I rather stay on a stable version with less functionality than on a version with bells and whistles that never responds when I need the server.

emby3.log

[revengineer 142]

As an interesting note, at least during the last two incidents, the downloading of subtitles was interrupted.

[ZachOfAllTrades 0]

Luke,

 

I don't know the internals of this app, but I'd be tempted to count count revengineer's report as another possible case of a threading problem, quite possibly related to what was elsewhere reported about ffmpeg threads not closing. The error description in this log contains the message:

"There were not enough free threads in the ThreadPool to complete the operation."

[revengineer 142]

As I said above, ffmpeg is not the issue. No such threads are running at the time the server is nonresponsive.

 

On another note, the server is still running fine 24 hours after upgrading to v5930 with coverart. This is the longest the server was operational in a two week period. Will keep monitoring (and knocking on wood). 

[revengineer 142]

The problem just reoccurring. Server is not responding. I am now running v5931. The previous logs did not contain any useful information. Do I need to enable debug logging?

[hyttam 2]

I am having similar issues. I did a complete reinstall with 3.0.5931.0 and the server will run, but no media are coming up on the web interface or my roku. I have restarted the server several times. It stays like this without end.

 

[hyttam 2]

The system came back after I forced a cleanup of the database. It works now.

[revengineer 142]

The above issue is completely different from mine and irrelevant to this thread.

[revengineer 142]

I am attaching the log from this mornings incident. I notice that there are a lot of DLNA errors just before the log entries stop. Hint or coincidence?

emby4.log

[Luke 42078]

I am attaching the log from this mornings incident. I notice that there are a lot of DLNA errors just before the log entries stop. Hint or coincidence?

 

as a test, can you try disabling the dnla server and dlna play to features? thanks.