n00b42 33 Posted December 5, 2016 Share Posted December 5, 2016 My Xpenology Setup became quite slow, therefore I looked into the process list and discovered that it used around nearly all available RAM (around 12 GB) top PID* VSZ VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND 25832 25.8g 22.7g 11.9g 0 11.9g 0 264 /var/packages/EmbyServer/target/mono/bin/mono /var/packages/EmbyServer/target/server/MediaBrowser.Server.Mon In Emby Administration "Running tasks" showed a "Scan media library 97.7%" which seems stuck as it did not change within half an hour. Not sure if related but the logs are filled with errors like 2016-12-04 00:08:16.5015 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 3.0.8500.0 Command line: /var/packages/EmbyServer/target/server/MediaBrowser.Server.Mono.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe Operating system: Unix 3.10.35.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: /var/packages/EmbyServer/target/var Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Tue Oct 18 07:23:39 CST 2016) Application Path: /volume1/@appstore/EmbyServer/releases/v3.0.8500/MediaBrowser.Server.Mono.exe Access to the path "/volume3/movies/Some Movie ästetik/movie.nfo" is denied. System.UnauthorizedAccessException at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0025f] in <1170fb08300b4d0db71c1d1db8555768>:0 at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize) [0x00000] in <1170fb08300b4d0db71c1d1db8555768>:0 at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int) at CommonIO.ManagedFileSystem.GetFileStream (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Boolean isAsync) [0x0001d] in <33bbb03c267e4f55a5ae1729f1d65006>:0 at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.SaveToFile (System.IO.Stream stream, System.String path) [0x00044] in <eb9be5571b7042bbaf9c6e9359c6c296>:0 at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.Save (MediaBrowser.Controller.Entities.IHasMetadata item, System.Threading.CancellationToken cancellationToken) [0x00026] in <eb9be5571b7042bbaf9c6e9359c6c296>:0 at MediaBrowser.Providers.Manager.ProviderManager+<SaveMetadata>d__47.MoveNext () [0x0023a] in <84227b04fe8f46ef8915cff10b952354>:0 (Errors are for different movies though) Might be related to: https://emby.media/community/index.php?/topic/41276-ds214-emby-mono-ram-usage/ Link to comment Share on other sites More sharing options...
Solution Luke 37118 Posted December 5, 2016 Solution Share Posted December 5, 2016 Hi, this will be resolved for the next release of Emby Server, except for the file saving errors, as that is something you'll need to handle. It would appear you've enabled saving metadata into media folders, but Emby Server does not have write access to that location. You'll want to review the access privileges for the Emby service account. Thanks. 1 Link to comment Share on other sites More sharing options...
n00b42 33 Posted December 5, 2016 Author Share Posted December 5, 2016 1) The RAM usage went back to around 300MB after I stopped and restarted the service, not sure if or when it will increase again. 2) Actually, the saving works as Emby already downloads all the metadata and media in the movie directories. Meaning, i did not encounter problems with saving the metadata myself, only saw lots of those errors in the logs. Maybe some race condition / locking issue of XPenology, will look if I can find more information.... Link to comment Share on other sites More sharing options...
Luke 37118 Posted December 5, 2016 Share Posted December 5, 2016 Thanks for the info. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now