Jump to content


Photo

Extreme RAM usage


Best Answer Luke , 19 March 2019 - 04:33 PM

You're on an extremely old version of Emby Server. Can you update to the latest version?

Go to the full post


  • Please log in to reply
10 replies to this topic

#1 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 19 March 2019 - 04:18 PM

Hi Folks,

 

Been quite a while since i had an issue, but i know this is the right place to resolve it.

Twice within the past 24 hours my XPENO box has suffered with extremely high RAM usage.

First time it happened I was only alerted to it by trying to connect to the server to watch something.

Each time the process consuming over 2GB has been 'Main' (not sure if this is an Emby process or not).

 

The only thing I did to resolve was to stop the Emby package and start it once more. Both times the server responded normally.
This has prompted me to consider upgrading to the latest version. But would rather see what the issue is before doing anything further.

 

Send logs are here:

sendlogs_nas_synology_bromolow_3615xs_20190319T201104UTC.tgz  

& run diags are attached.

Thanks in advance.

Attached Files



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124163 posts
  • Local time: 04:54 PM

Posted 19 March 2019 - 04:20 PM

Hi, can you attach the emby server log as well? thanks.



#3 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 19 March 2019 - 04:29 PM

Hi Luke,

 

Attached.
It seems to get stuck when doing a Library Scan.

Attached Files



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124163 posts
  • Local time: 04:54 PM

Posted 19 March 2019 - 04:33 PM   Best Answer

You're on an extremely old version of Emby Server. Can you update to the latest version?


  • RobsterUK likes this

#5 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 19 March 2019 - 04:46 PM

OK, just backing up a few folders first.

 

Is the latest version 4.0.3.0-1 supported for XPENology boxes?

In other words can i simply update the package from the package center interface?



#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124163 posts
  • Local time: 04:54 PM

Posted 19 March 2019 - 04:47 PM

Yes that is the latest. Coming from a version that old you might consider a fresh install, but yes you can  upgrade.



#7 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 19 March 2019 - 05:51 PM

OK, I have updated to latest version.

Seems to have installed ok eventually. The package would not start immediately after upgrading, I had to reboot the NAS.

DB upgrade completed OK. Ran a library scan and it took 20 minutes, and for about the last 5 minutes of this 'mono-sgen' was consuming over 2GB RAM.

I understand my server was so out of date that the first library scan will be extended, but the high RAM towards the end is still concerning.

 

The server log it has generated was too big to post here. So I have uploaded it to here https://www.dropbox....44/Log.txt?dl=0

I hope everything will be ok from now on.

 

@Luke thanks for looking into this for me

 



#8 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 21 March 2019 - 05:35 AM

A quick update.
The twice daily scheduled scan has completed OK during the past 36 hours.

 

Think it's safe to say that everything is functioning OK now. I don't understand what suddenly happened to break things in the first place as nothing was installed or updated on the NAS to change anything. But installing the latest version of the server seems to have resolved the issue.



#9 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 09:54 PM

Posted 21 March 2019 - 07:56 AM

Hello @RobsterUK

 

Thanks for the update and glad to see you're back up and running; how are you finding the latest version in term of performance on your system now?

 

Regarding...

 

The package would not start immediately after upgrading, I had to reboot the NAS.

 

 

...this has been solved in the latest betas and will be fixed in the next stable, it's a DSM 5 backward compatibility issue.

 

It was part of the reason for stating this thread, to see if it made sense to keep supporting it (we will) : https://emby.media/c...urrently-using/

 

In terms of memory runaway, this certainly isn't an isolated case - whilst still rare, there have been other reports. I'm curious about your situation though, as you've been running a stable and consistent environment for so long, it strongly supports the theory that there is an external trigger driving this behaviour.

 

Has anything changed in your setup, say a new/different media playback device or a DLNA capable device been added to the network; regardless of whether it's being used for playback from Emby Server. Any different media formats or viewing patterns that coincide at all?

 

Best

- James



#10 RobsterUK OFFLINE  

RobsterUK

    Advanced Member

  • Members
  • 69 posts
  • Local time: 09:54 PM

Posted 24 March 2019 - 05:38 PM

Hi James @solabc16, thanks for dropping in.

 

One the whole things have been ok for the past few days. The Server has been running ok. I have thought about any changes within the network and /or external factors and i cannot think of anything that changed to cause the memory issue.
There have been no new devices introduced. I certainly haven't installed any apps on any device that would have been dlna reliant.
I asked my teenage son and he told me that he hadn't - but he's a 16 year old boy. So there's always a chance he's done something to his phone :rolleyes:

 

The daily library scans have completed OK. I have only been watching TV shows for a few days. Went to watch a movie on Friday evening and there was no run time / finish time / media info or chapters. This was on a recently added movie. But it was added prior to the server upgrade early last week.
upon investigation it seems there are a few titles with this issue.

 

I have looked on the forum and read a couple of topics surrounding metadata and full vs individual refreshes. If I manually refresh metadata for a title it updates it. However I went into the server Library settings and chose 'replace all metadata' from the 'scan library' option. This caused excessive RAM usage whilst running. Once the server GUI indicated it had finished mono-sgen was once more consuming 1.9GB RAM, but status was 'sleeping'. I had to stop the server package and start once more. Checked the movie title and it still does not have a fullmetadata.

 

I have read that a re-install of the server may be required to overcome this. This brings a few questions:

  1. Is this a straightforward removal - re-install?
  2. Or is a backup / restore required?
  3. I have created a manual backup (not currently a subscriber) but would be prepared to sign up for one month to get a good backup.
  4. Will a restore actually restore the metadata- therefore still having titles without full metadata?
  5. If I avoid a restore I can recreate the library folders - but what about all the watched statuses - we rely heavily on this feature.

I could do a manual refresh of all titles, but with over 800 to check, this would be fairly time consuming.

 

Any advice gratefully received.

Thanks,
Rob

 



#11 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 09:54 PM

Posted 26 March 2019 - 08:54 AM

Hello @RobsterUK

 

If a lot of new images are processed as part of the refresh, I have seen this drive the memory footprint to some pretty high levels, from which they never return : https://emby.media/c...usage/?p=700269

 

This is something I'm digging into, but it will take some time and the upcoming runtime switch adds another variable.

 

The uninstall/re-install and backup/restore are all reasonably well tried and tested processes. Depending how complex your configuration is, starting from scratch may also be an option.

 

I'd like to think this wouldn't be necessary, but if you're still having quirky issues maybe it's the most pragmatic solution.

 

However, I'm not best placed to advise on how this would affect the watched statuses - others would be better placed to give you a definitive answer on this. @Luke?

 

Best

- James






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users