IceBoosteR 10 Posted January 20, 2018 Posted January 20, 2018 (edited) Hello all, first of all THANK you for your hard work making this great piece of software! I really enjoy the project and love the fact, that you are not that focussed on collecting all the possible data like PLEX does. But back to my problem. When I start my emby server on FreeNAS (FreeBSD based) the process mono-sgen is consuming lot of resources. (Background: I only have some music in emby) First of all, CPU is for some hours on about 30% load (Xeon E3-1225v3) and during this time, there can be seen often write operations on my SSD. I dont know why but it is bothering me, as I don't know why Emby does this and in my eyes it is not neccessary to write data. Read would make perfect sense, but also not from SSD, as there are only the Emby internal files stored, and the music is written from my HDD pool. Can someone please explain this to me, and if there is a solution available, please share. In this case, early 50GB are written in 1h, before I stopped the server again. I have installed Emby from the FreeNAS plugins, but I dont mind to reinstall it from scratch with the suggestion here: https://emby.media/freebsd-server.html The only thing I would like to know on this how to "recompile the multimedia/ffmpeg package". Many thanks, IceBoosteR Edited January 20, 2018 by IceBoosteR
Luke 38842 Posted January 20, 2018 Posted January 20, 2018 hi there, please attach the information requested in how to report a problem. thanks !
IceBoosteR 10 Posted January 20, 2018 Author Posted January 20, 2018 Hi, I am sorry, did not know about this page. Here you have the logfile. Emby.log
Luke 38842 Posted January 20, 2018 Posted January 20, 2018 Hi there, you're running a pretty old version of Emby Server. If you try updating to the latest version it should be more efficient. Thanks !
IceBoosteR 10 Posted January 20, 2018 Author Posted January 20, 2018 (edited) Hi there, you're running a pretty old version of Emby Server. If you try updating to the latest version it should be more efficient. Thanks ! Hi, ok I will update and report back! Edit: Ok I will need to make a fresh installation, can you maybe make some clarifications on the FreeBSD documentation part :"recompile the multimedia/ffmpeg package". Edit2: Got it Thanks Edited January 20, 2018 by IceBoosteR
woodsb02 17 Posted January 21, 2018 Posted January 21, 2018 I believe the FreeNAS plugin already has the necessary ffmpeg compile flags set. Those instructions are only for if you installed emby via the FreeBSD package.
IceBoosteR 10 Posted January 21, 2018 Author Posted January 21, 2018 I believe the FreeNAS plugin already has the necessary ffmpeg compile flags set. Those instructions are only for if you installed emby via the FreeBSD package. Hi I believe that also. The plugin is often out of date, so I was trying to create a manual jail and follow the instruction given on the Emby website. With this I run in various problems with ports and make, as FreeNAS is using FreeBSD 11.0 as default for jails, which is no longer supported, so port update and so on is not guranteed to work, and it does not for me.... I am searching around to get a workaround but found none yet.
woodsb02 17 Posted January 21, 2018 Posted January 21, 2018 Perhaps check on the FreeNAS forums if there is a way to move to FreeBSD 11.1 for your jails? As a manual workaround, you could try running freebsd-update in the jail to upgrade to 11.1... but I am not sure if this is recommended on FreeNAS?
IceBoosteR 10 Posted January 21, 2018 Author Posted January 21, 2018 (edited) Hi, I think that there is no possibility to manually move to FreeBSD 11.1. I can try to make a manual upgrade for that certain jail, but yes - it is not recommended. Back to the topic. I have installed the latest version of the plugin for FreeNAS of Emby which contains version 3.2.60.0 Even tho, every minute around 500MB of data is written to my SSD, without any kind of reason. Please have a look into that @@Luke . I have attached again the screenshot, it seemes to be temporary data, as I see much delets on that SSD devices at the same time. Storage for that jail/plugin is NOT increasing. So writing temp data to disk is a bad idea in my opinion. Use RAM for that^^ Edited January 21, 2018 by IceBoosteR
IceBoosteR 10 Posted January 25, 2018 Author Posted January 25, 2018 Hi, has no one an idea or a fix for this?
Luke 38842 Posted January 25, 2018 Posted January 25, 2018 Please try the next release of emby server. Thanks !
IceBoosteR 10 Posted January 25, 2018 Author Posted January 25, 2018 Please try the next release of emby server. Thanks ! Ok but why? To be honest and I don't want to blame you or make you angry in any way, but you cannot say try the next release... If you can share some additional information if a root cause was found or WHY this behaviour will stop, this would be awesome. My problem is, that I cannot update emby "fast" or "just a few clicks". It is more like compiling a whole FreeBSD jail... So before I waste some more hours, information would be nice. Thanks for coming back tho
Luke 38842 Posted January 25, 2018 Posted January 25, 2018 Sorry, I had already suggested updating to the latest version. Did you do that?
IceBoosteR 10 Posted January 26, 2018 Author Posted January 26, 2018 Sorry, I had already suggested updating to the latest version. Did you do that? Hi Luke, as I have written, I have updated to 3.2.60.0 and the behaviour was still occuring as you can see from my previous post. I can make the effort and compile an new jail to 3.2.70.0 but I did not see why this behaviour would change... So I am here to work out a solution with you, as I think I am not the only one which might be affected. Cheers Ice
Luke 38842 Posted January 26, 2018 Posted January 26, 2018 The server is getting lighter with each new release so that's why I would suggest updating and attaching a new log if there is an issue. thanks.
IceBoosteR 10 Posted January 26, 2018 Author Posted January 26, 2018 Ok give me some time, I will report this back to you.
IceBoosteR 10 Posted January 26, 2018 Author Posted January 26, 2018 (edited) Hi I have tried varoius oltuions, I have to stay on 3.2.60.0 and report the log of the server. I will monitor the system processes what the hell Emby is doing. And yes, at the moment I cannot upgrade. Edit: so here are new logs, same behaviour, please help on this. And I could see that this only occurs when Emby is scanning the library. Disk ada0 is writing and deleting a lot of data... emby processes.txt emby LOG.txt Edited January 26, 2018 by IceBoosteR
Luke 38842 Posted February 2, 2018 Posted February 2, 2018 Until you're to update there's not much I can offer. You could try turning off dlna features in the server.
IceBoosteR 10 Posted February 2, 2018 Author Posted February 2, 2018 Mhh... DLNA is off Is there a way to create bugtickets or something similar? Do you have seen this behaviour on Windows/or somewhere else also? I think if not this is maybe related to some FreeBSD ports. There must be a solution to make the software better.
Luke 38842 Posted February 2, 2018 Posted February 2, 2018 The activity is improved a little in 3.2.70 and will be improved even more significantly in the release after that. thanks.
IceBoosteR 10 Posted March 4, 2018 Author Posted March 4, 2018 (edited) So this behaviour can now be seen on Linux (ubuntu server 16.10) with the newest version of emby 3.30.00 installed. Writing a bunch of data to local SSD, doing really nothing useful why scanning the library. This is FRUSTRATING... Edited March 4, 2018 by IceBoosteR
IceBoosteR 10 Posted March 4, 2018 Author Posted March 4, 2018 I think this can also be moved to linux, but nevertheless it seems to be massive logspam: lsof | grep -e "[[:digit:]]\+w" | grep Emby EmbyServe 1059 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 emby 43wR REG 252,0 628390 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1138 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1138 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1138 emby 43wR REG 252,0 628110 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1138 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1139 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1139 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1139 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1139 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1148 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1148 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1148 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1148 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1149 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1149 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1149 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1149 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1150 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1150 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1150 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1150 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1151 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1151 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1151 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1151 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1152 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1152 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1152 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1152 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1155 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1155 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1155 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1155 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1157 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1157 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1157 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1157 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1385 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1385 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1385 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1385 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1388 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1388 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1388 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1388 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1393 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1393 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1393 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1393 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1423 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1423 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1423 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1423 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1424 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1424 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1424 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1424 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1425 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1425 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1425 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1425 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1434 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1434 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1434 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1434 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 1747 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 1747 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 1747 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 1747 emby 149w FIFO 0,10 0t0 16507 pipe EmbyServe 1059 11700 emby 4w FIFO 0,10 0t0 16467 pipe EmbyServe 1059 11700 emby 11w FIFO 0,10 0t0 16471 pipe EmbyServe 1059 11700 emby 43wR REG 252,0 628250 2755316 /var/lib/emby/logs/server-63655723329.txt EmbyServe 1059 11700 emby 149w FIFO 0,10 0t0 16507 pipe But the actual log mentioned above is only some random information, which is updated every 5-10 seconds. Cannot believe it causes 40+ GB of overhead: 2018-03-04 01:50:06.377 Info ProviderManager: Saving image to /var/lib/emby/metadata/library/c0/c01a64ba944c6cd20f4bd5b3bccb00cf/poster.jpg
Luke 38842 Posted March 4, 2018 Posted March 4, 2018 Do you have any plugins installed? Plugins are able to write to the log so this could contribute to that. Try uninstalling all plugins. Then also make sure you haven't enabled any debug logging settings.
IceBoosteR 10 Posted March 4, 2018 Author Posted March 4, 2018 Hi Luke, no this is a fresh installation. No plugins, no debug logging, just the defaults. I will report back again if I have some more news. Maybe Linux has a different long time behaviour....
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