Jump to content

100% CPU Load


popy
 Share

Go to solution Solved by popy,

Recommended Posts

Hey guys.

 

Experienced 100% CPU load today on my emby server 3.0.6400.0 !

It's running on Windows Home Server 2011 (2008 r2).

I have nothing changed on the server, but the mediabrowser executable was used 100% cpu load.

 

Sadly i had not enabled debugging log, but i have a normal log.

See here: Log_emby_sevrver_20_09_2016.txt

 

After that i killed the exe with task manager and restartet it.

It worked without any issues.

At least i have updated to the latest version "3.0.7200".

 

Is this a known issue?

 

thx

pOpY

Edited by popy
Link to comment
Share on other sites

I had the same thing before. Now I'm running the 3.0.71 and it's work fine.

thx for the info.

I have also update, but to the newer version "3.0.7200".

Until now i can confirm that the issue is gone.

 

If it comes back i will, disable plugins and report back here.

 

thx

pOpY

Link to comment
Share on other sites

Issue is back for me  :(

100% CPU load!

 

I just have these plugins installed and at time of the issue (or at least when ill saw it) i have not used those plugins.

Maybe this information is usefull.

This are the plugins:

57e967b5e4b40_plugins.png

 

I have now removed the plugin DLLs from plugin folder and restarted emby, will see how it goes...

 

Here is a "normal" log, should ill activate debug log?

Log: server-63610444800.zip

 

pOpY

Link to comment
Share on other sites

One more question, are there any jobs running on start of the server after reboot other than another start of the service?

I am asking because my WHS2011 reboots every Sundy-Monday night and i have a feeling that it has todo with the reboot.

Last week i posted the issue on thursday (maybe i had no time on monday) and today is monday.

 

Any hints  :rolleyes: ?

 

pOpY

Link to comment
Share on other sites

Do you have any sync tasks running?

 

Perhaps you accidentally hit the sync button in the UI?

 

no, because nobody used emby and no sync device (kodi clients) was powerd on.

I had a look on the webinterface of emby and experienced extreme lags -> this was the result of the high cpu load, which was caused by emby.

Will look at the scheduler tasks, if the issue comes back after removing the plugins.

 

Also i have tried to start "all" tasks (one after one) and looked at the cpu load.

cpu goes never above 25% (1 core?), regardless of which task is running.

 

pOpY

Edited by popy
Link to comment
Share on other sites

Again, emby goes crazy.

This time, without any plugins, it uses 2x cores of my 4 cores -> 50% cpu load.

I had a look at the tasks -> no scheduler task is running.

What i have done an hour ago, i have added some audio book mp3s.

Here is the log: Log_28_09_2016.zip

 

In the logs are massive exceptions on getting data from musicbrainz domain!?

Any hints what causes this issue?

 

thx

pOpY

Link to comment
Share on other sites

It is loading metadata for the new content, when it finishes the load should go down.

 

thx, so it seems a normal metadata scrapping load.

 

Are the exceptions in the log normal?

 

 

The 100% issue hasnt come back until ill deactivated my plugins including syncqueue, there are other users reported the same high cpu load: https://emby.media/community/index.php?/topic/23971-fast-startup-sync-server-plugin/page-31&do=findComment&comment=370894

 

Will leave it without the plugins for a few more days to see if removing of plugins has done the trick.

After that i will add it back one by one to see what does the culprit.

 

pOpY

Link to comment
Share on other sites

Hi, no the music brianz errors are not normal. i will look into those. thanks.

 

thx, please let us know what caused the exceptions.

 

pOpY

Link to comment
Share on other sites

Sadly the issue was back yesterday at about 23:00. Emby was using 100% cpu. This time, No plugin was active!!!

After killing the process and restarting the cpu utilization went back to normal.

 

Will post a log in the afternoon when I'll get home.

 

pOpY

Link to comment
Share on other sites

He

 

Sadly the issue was back yesterday at about 23:00. Emby was using 100% cpu. This time, No plugin was active!!!
After killing the process and restarting the cpu utilization went back to normal.

Will post a log in the afternoon when I'll get home.

pOpY

 

Here are the logs: Log_1-10-2016_23_00.zip

Would be nice if you can read of it whats the issue?

 

There are a lot of the following exceptions in it:

2016-10-01 00:18:18.8085 Error SsdpHandler: Failed to read SSDP message
	*** Error Report ***
	Version: 3.0.7200.0
	Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service
	Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
	Processor count: 4
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Administrator\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Eine Nachricht, die �ber einen Datagrammsocket gesendet wurde, war f�r den internen Nachrichtenpuffer oder ein anderes Netzwerklimit zu gro�, oder der Puffer f�r den Datagrammempfang war f�r das Datagramm zu klein
	System.Net.Sockets.SocketException
	   bei System.Net.Sockets.Socket.EndReceiveFrom(IAsyncResult asyncResult, EndPoint& endPoint)
	   bei MediaBrowser.Dlna.Ssdp.SsdpHandler.ReceiveCallback(IAsyncResult result)

I have seen the issue on 01.10.2016 at about 23:00, maybe the trigger/issue occured before this time.

 

thx

pOpY

Edited by popy
Link to comment
Share on other sites

@Luke: Any news on this?

Do you need any additional logs/tests to narrow down the issue?

(plugins are removed!)

 

PS: Yesterday the same issue happened again. emby uses 100% cpu and my mediaportal live tv sever has'nt got much cpu power which resulted in live tv stutter in kodi.

 

thx

pOpY

Link to comment
Share on other sites

Happy2Play

Have you tried disabling Real Time Monitoring?  (just as a test on some or all libraries) Dashboeard-Library-select each Library

Link to comment
Share on other sites

Have you tried disabling Real Time Monitoring?  (just as a test on some or all libraries) Dashboeard-Library-select each Library

 

Will try this and report back.

 

thx

pOpY

Link to comment
Share on other sites

Here is the debug log from yesteray 06.10.2016, i have seen that the cpu goes crazy at about 22:15.

After that i have restarted the emby service and all went back to normal.

 

In the log are also those "Error SsdpHandler: Failed to read SSDP message" exceptions & also musicbainz!?

 

thx

pOpY

 

PS: realtime monitoring is now deactivated on all librarys

 

 

debug_Log_emby_06_10_2016.zip

Edited by popy
Link to comment
Share on other sites

The winsock error from exception is (in german):

 

10040 (WSAEMSGSIZE) Eine Nachricht, die über einen Datagrammsocket gesendet wurde, war für den internen Nachrichtenpuffer oder ein anderes Netzwerklimit zu groß, oder der Puffer für den Datagrammempfang war für das Datagramm zu klein

 

or english:

 

WSAEMSGSIZE 10040

 

Message too long.

A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.

 

Maybe a to small declared buffer?

Here are good informations about this: http://stackoverflow.com/questions/9378146/how-to-easily-solve-the-10040-message-too-long-error-on-wsock2

@Luke: can you please check this?

 

Can the exception lead to my high cpu load?

 

thx

pOpY

Link to comment
Share on other sites

Let us know how it goes with just the core server. thanks.

 

 

Have you tried disabling Real Time Monitoring?  (just as a test on some or all libraries) Dashboeard-Library-select each Library

 

thx a lot!
one week has passed and the issue is gone!
I'll think i will leave it deactivated, as a workaround until the issue is fixed.
Is there anything i can do to help find the issue?
Logs ...

 

Thenewest 3.0.8000 states: 
  • Add library monitor error handling
  • Fix repeated refreshing from realtime monitor
 
 
@Luke: Do you think my issue is fixed with this release?
 
thx

pOpY

Link to comment
Share on other sites

Please try it out and give us your feedback. Thanks !

 

I have now updated to 3.0.8100 and activated realtime monitoring on all librarys.

Will report back...

 

pOpY

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

×
×
  • Create New...