tmedia 0 Posted August 13, 2020 Share Posted August 13, 2020 (edited) Hi guys, I am running the official EmbyServer docker version 4.4.3.0. This error used to happen in a past version and then was gone for a while but the last few days I am seeing the error again in my UNRAID server logs. The error is repeated twice each morning after the container is started after a backup: Aug 13 00:31:09 Tower kernel: ffdetect[22630]: segfault at 38 ip 000000000040412a sp 00007ffc68b5b0d0 error 4 in ffdetect[403000+c000] Is there a known way to fix this or is it something within the container that will have to be resolved? hardware_detection-63732875470.txt Edited August 13, 2020 by tmedia add hardware detection log Link to comment Share on other sites More sharing options...
Luke 37064 Posted August 14, 2020 Share Posted August 14, 2020 Hi there, is unraid up to date? Link to comment Share on other sites More sharing options...
tmedia 0 Posted August 14, 2020 Author Share Posted August 14, 2020 1 hour ago, Luke said: Hi there, is unraid up to date? Yes I'm on the stable branch 6.8.3 Link to comment Share on other sites More sharing options...
tmedia 0 Posted August 14, 2020 Author Share Posted August 14, 2020 I've read through what I could find via google but didn't come up with a definitive fix. Is it because the container is attempting to access something it doesn't have permission for or something else? Link to comment Share on other sites More sharing options...
Luke 37064 Posted September 22, 2020 Share Posted September 22, 2020 @tmedia can you please try the new Emby server 4.5 release and let me know how that compares? Thanks ! Link to comment Share on other sites More sharing options...
tmedia 0 Posted September 22, 2020 Author Share Posted September 22, 2020 Is this update available for the UNRAID docker? I just force checked for an update and it's still saying my 4.4.3.0 is up-to-date. Link to comment Share on other sites More sharing options...
tmedia 0 Posted September 23, 2020 Author Share Posted September 23, 2020 OK, I got the container updated and the error is no longer showing. Thank you guys! 9 hours ago, Luke said: @tmedia can you please try the new Emby server 4.5 release and let me know how that compares? Thanks ! Link to comment Share on other sites More sharing options...
tmedia 0 Posted September 24, 2020 Author Share Posted September 24, 2020 Well, it showed back up this morning... Sep 24 00:30:55 kernel: ffdetect[13708]: segfault at 38 ip 000000000040412a sp 00007ffdd3febad0 error 4 in ffdetect[403000+c000] Sep 24 00:30:55 kernel: Code: 84 5c 01 00 41 0f b6 6d 00 40 84 ed 75 b7 48 8b 34 24 48 8d 3d 4c af 00 00 31 c0 ff 15 27 5b 01 00 48 89 df ff 15 46 5c 01 00 <41> 0f b6 2c 24 40 84 ed 0f 84 93 00 00 00 4c 8d 35 b1 b2 00 00 eb Sep 24 00:30:55 kernel: ffdetect[13709]: segfault at 38 ip 000000000040412a sp 00007fff4fb4c700 error 4 in ffdetect[403000+c000] Sep 24 00:30:55 kernel: Code: 84 5c 01 00 41 0f b6 6d 00 40 84 ed 75 b7 48 8b 34 24 48 8d 3d 4c af 00 00 31 c0 ff 15 27 5b 01 00 48 89 df ff 15 46 5c 01 00 <41> 0f b6 2c 24 40 84 ed 0f 84 93 00 00 00 4c 8d 35 b1 b2 00 00 eb 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