mgworek 121 Posted December 7, 2017 Share Posted December 7, 2017 I mentioned this last week in the Testing .NET topic but didn't get any response. It is happening more often now. Docker running on unraid. I go into a movie, edit images. When I go to delete or add a image it crashes the server. If I start the server, I can't even edit that movies images anymore, it crashes as soon as I try. It was happening to only a couple of movies but now its happening to more movies. Logged attached. Here is the error in unraid when it happens. "Dec 7 05:47:38 Tower kernel: EmbyServer[17924]: segfault at 0 ip 000015240ad625c0 sp 000015236abde688 error 4 in libc-2.17.so[15240acf0000+1aa000]" server-63648240440.txt Link to comment Share on other sites More sharing options...
alucryd 216 Posted December 7, 2017 Share Posted December 7, 2017 Hmm, segfault in glibc, possibly the worst thing that could happen. Only solution I see is to switch to a more recent glibc just for docker. Please stay tuned. Link to comment Share on other sites More sharing options...
armsby 1 Posted December 7, 2017 Share Posted December 7, 2017 (edited) I have the same issue on ubuntu 17.xx it happens when loading images for collections or anything with missing images Edited December 7, 2017 by armsby 1 Link to comment Share on other sites More sharing options...
Luke 37064 Posted December 7, 2017 Share Posted December 7, 2017 I have the same issue on ubuntu 17.xx it happens when loading images for collections or anything with missing images hi @@armsby, you probably don't have the same issue. please see how to report a problem. thanks ! Link to comment Share on other sites More sharing options...
armsby 1 Posted December 7, 2017 Share Posted December 7, 2017 as reported here https://emby.media/community/index.php?/topic/53531-server-keeps-crashing-when-opening-collections/ Link to comment Share on other sites More sharing options...
alucryd 216 Posted December 7, 2017 Share Posted December 7, 2017 (edited) @@mgworek BTW, does any other version work, like the previous mono image? I haven't had any similar report yet, that could be caused by faulty RAM. Edited December 7, 2017 by alucryd Link to comment Share on other sites More sharing options...
Luke 37064 Posted December 7, 2017 Share Posted December 7, 2017 @@mgworek BTW, does any other version work, like the previous mono image? I haven't had any similar report yet, that could be caused by faulty RAM. @@alucryd, mono is on imagemagick still so the comparison is probably apples to oranges. Link to comment Share on other sites More sharing options...
alucryd 216 Posted December 7, 2017 Share Posted December 7, 2017 Hmm, right. Link to comment Share on other sites More sharing options...
mgworek 121 Posted December 7, 2017 Author Share Posted December 7, 2017 (edited) I wasn't sure if I could go back to the stable from the .NET version. If I can, I will give it a try. Thanks. Edited December 7, 2017 by mgworek 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