Luke 42077 Posted January 20, 2019 Posted January 20, 2019 Hi there @@sonicattack can you please attach an emby server log? thanks.
Luke 42077 Posted January 20, 2019 Posted January 20, 2019 Nevermind, you opened a new topic, so we'll help you there. Thanks.
bungee91 133 Posted January 30, 2019 Posted January 30, 2019 I am running emby server v4 on an proxmox host as an unprivileged LXC (Ubuntu 18.04.1) (Hardware acceleration is set to off). Art upgrading to v4 I got segfaults on startup emby service (but everything is working fine). See dmesg: [ 77.693060] ffdetect[19621]: segfault at 60 ip 0000000000403a38 sp 00007ffe857501e0 error 4 in ffdetect[400000+15000] [ 77.767348] ffdetect[19627]: segfault at 60 ip 0000000000403a38 sp 00007ffdd6602030 error 4 in ffdetect[400000+15000] And if am trying to call ffdetect I got his: root@emby:/opt/emby-server/bin# ./ffdetect ./ffdetect: error while loading shared libraries: libavutil.so.56: cannot open shared object file: No such file or directory (Likely not the best place for this, but...) I am getting these same messages in my system log on UnRAID. No apparent issues per se, just bold red in my log since it comes up as a segfault. I see the following in my UnRAID system log: Jan 28 02:07:11 Server kernel: ffdetect[30107]: segfault at 60 ip 0000000000403a38 sp 00007fffebb1bd70 error 4 in ffdetect[400000+15000] Jan 28 02:07:11 Server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Jan 28 02:07:11 Server kernel: ffdetect[30110]: segfault at 60 ip 0000000000403a38 sp 00007ffd851d3c80 error 4 in ffdetect[400000+15000] Jan 28 02:07:11 Server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 This is what shows in the Emby Server log: 2019-01-28 02:07:11.021 Info SoftwareCodecInfoProvider: h264, libx264, libx264 Software Encoder, V-E-libx264 2019-01-28 02:07:11.021 Info SoftwareCodecInfoProvider: mpeg4, mpeg4, MPEG-4 part 2 Software Encoder, V-E-mpeg4 2019-01-28 02:07:11.021 Info SoftwareCodecInfoProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3) Software Encoder, V-E-msmpeg4 2019-01-28 02:07:11.021 Info SoftwareCodecInfoProvider: vp8, libvpx, libvpx VP8, V-E-libvpx 2019-01-28 02:07:11.040 Info VaapiCodecInfoProvider: ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json vaencdec 2019-01-28 02:07:11.041 Info VaapiCodecInfoProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json vaencdec 2019-01-28 02:07:11.047 Info VaapiCodecInfoProvider: ProcessRun 'ffdetect_vaencdec' Started. 2019-01-28 02:07:11.050 Info VaapiCodecInfoProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 139 2019-01-28 02:07:11.057 Info App: Entry point completed: Emby.Server.MediaEncoding.Encoder.MediaEncoderEntryPoint. Duration: 0.2613416 seconds 2019-01-28 02:07:11.057 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint 2019-01-28 02:07:11.103 Error VaapiCodecInfoProvider: Error running ffdetect for vaencdec - 2019-01-28 02:07:11.109 Info QuickSyncCodecInfoProvider: ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json qsvencdec 2019-01-28 02:07:11.110 Info QuickSyncCodecInfoProvider: ProcessRun 'ffdetect_qsvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json qsvencdec 2019-01-28 02:07:11.119 Info QuickSyncCodecInfoProvider: ProcessRun 'ffdetect_qsvencdec' Started. 2019-01-28 02:07:11.121 Info QuickSyncCodecInfoProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code 139 2019-01-28 02:07:11.174 Error QuickSyncCodecInfoProvider: Error running ffdetect for qsvencdec - 2019-01-28 02:07:11.180 Info NvidiaCodecInfoProvider: ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json nvencdec 2019-01-28 02:07:11.181 Info NvidiaCodecInfoProvider: ProcessRun 'ffdetect_nvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 0 -show_error -show_log 48 -print_format json nvencdec 2019-01-28 02:07:11.189 Info NvidiaCodecInfoProvider: ProcessRun 'ffdetect_nvencdec' Started. 2019-01-28 02:07:11.192 Info NvidiaCodecInfoProvider: ProcessRun 'ffdetect_nvencdec' Process exited with code 1 @@Luke let me know if you want the complete log to help in diagnosing.
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