Jump to content

Core dumped in ffprobe


Recommended Posts

Posted

Under my synology i see line for process 
 

Quote

bin/mono system/EmbyServer.exe -programdata ...

so seems emby is not compiled natively. Why it is done so? Because it is C#-based or smth?

Posted

Hi, is this an older model synology?

Posted

Many mine mp4 files are failed to be parsed for information with next line:
 

Quote

2024-06-18T06:36:46+03:00 ice_home_nas coredump[6087]: Process ffprobe[6086](/volume2/@appstore/EmbyServer/bin/ffprobe) dumped core on signal [4]. Core file [/volume1/@ffprobe.synology_armada370_414slim.42962.core.gz]. Cmdline [/var/packages/EmbyServer/target/bin/ffprobe -i file:/volume1/path/to/mpeg/MOV02443.MPG -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data ]

2024-06-18T06:48:53+03:00 ice_home_nas coredump[9202]: Process ffprobe[9201](/volume2/@appstore/EmbyServer/bin/ffprobe) dumped core on signal [4]. Core file [/volume1/@ffprobe.synology_armada370_414slim.42962.core.gz]. Cmdline [/var/packages/EmbyServer/target/bin/ffprobe -i file:/volume1/backup_hdd//volume1/path/to/other_mp4/some.mp4 -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data ]

Beta is taken from 
https://github.com/MediaBrowser/Emby.Releases/releases/download/4.9.0.24/emby-server-synology7-mono_4.9.0.24_armv7_legacy.spk

Model: DS414slim

Dump added

@ffprobe.synology_armada370_414slim.42962.core.gz

Posted

Hi please attach the complete Emby server log. Thanks.

Posted

OK so for these older models the server runs using the mono runtime. 

ffmpeg, sqlite, and other libraries that we use are compiled natively.

Posted (edited)

Please, find logs attached. Note, that my device DS414slim doesn't run code natively as stated here.
Use case: just try to open video online
More information about failed videos (from VLC):
 

server_logs.zip

CodecInfo.png

Edited by icegood
Posted

Hi, I see you installed the armv7 package but are you sure this is an armv7 NAS?

Happy2Play
Posted
3 minutes ago, Luke said:

Hi, I see you installed the armv7 package but are you sure this is an armv7 NAS?

It is a Marvell Armada 370 88F6707 1.2 GHz CPU which suggests our Armv7_Legacy build.

And the others guys chart.

image.png.ea121bc8e1ceed066647458c182d5827.png

I can only assume it falls under the all others Legacy builds.

image.png.8e51de053ee26a322448b4d0d5ff7131.png

 

Posted

Are you able to run the 4.7 version from Synology package center? Before attempting to use an older version you'll need to delete the server data folder to make a fresh start:

/var/packages/EmbyServer/var

 

Posted (edited)

with 4.7.14.0 from synology community it works and video/audio info for failed files is successfully parsed:
video:
 

Quote
Title480p MPEG1VIDEO
CodecMPEG1VIDEO
Level-99
Resolution640x480
Aspect Ratio4:3
InterlacedNo
Framerate25
Bitrate105 mbps
Bit Depth8 bit
Pixel Formatyuv420p
Reference Frames1

audio:
 

Quote
TitleUnd MP2 mono
CodecMP2
Layoutmono
Channels1 ch
Bitrate64 kbps
Sample Rate32,000 Hz
DefaultNo

Something went wrong in newer version since no stream info present in UI for the same files

Edited by icegood
more info
Posted

OK thanks, so now we know the results from 4.7 and 4.9. Can you try 4.8 from our website?

Happy2Play
Posted
33 minutes ago, icegood said:

with 4.7.14.0 from synology community it works and video/audio info for failed files is successfully parsed:
video:
 

audio:
 

Something went wrong in newer version since no stream info present in UI for the same files

Devs/platform builder would have to comment but will guess there becomes a compatibility issue proceeding as I believe as of 4.9.0.8 there is a netcore change.  So these older platforms may be limited.

I guess your next test would be seeing if you can upgrade to 4.8 as it is still on netcore 6.

Posted

Checked against latest stable 4.8.8.0 - doesn't work.
 

Quote
2024-06-21 01:04:31.482 Error App: Error in ffprobe
*** Error Report ***
Version: 4.8.8.0
Command line: /volume2/@appstore/EmbyServer/system/EmbyServer.exe -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -defaultdirectory /volume1/Public -updatepackage emby-server-synology7-mono_{version}_armv7_legacy.spk -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -nolocalportconfig -noskia -ignore_vaapi_enabled_flag
Operating system: Linux version 3.2.101 (root@build3) (gcc version 8.5.0 (GCC) ) #42962 Mon May 29 14:34:16 CST 2023
Framework: Mono: 6.12.0.182 (tarball Thu Jan 19 10:28:52 PM UTC 2023)
OS/Process: X86/X86
Runtime: volume2/@appstore/EmbyServer/lib/mono/4.5/mscorlib.dll
Processor count: 1
Data path: /var/packages/EmbyServer/var
Application path: /volume2/@appstore/EmbyServer/system
Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Error running ffprobe: -i file:"/path/to/file/DSC-H50/MOV07979.MPG" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
at Emby.Server.MediaEncoding.Probing.MediaProbeManager.GetMediaInfoInternal (System.String inputPath, System.String primaryPath, MediaBrowser.Model.MediaInfo.MediaProtocol protocol, System.String userAgent, System.Boolean extractChapters, System.String probeSizeArgument, System.Boolean isAudio, System.Boolean hasMixedProtocols, System.Threading.CancellationToken cancellationToken) [0x001dd] in <59b0c601cefc4f678dca703e2fad3041>:0
at Emby.Providers.MediaInfo.FFProbeVideoInfo.ProbeVideo[T] (MediaBrowser.Controller.Providers.MetadataResult`1[T] metadataResult, MediaBrowser.Controller.Providers.MetadataRefreshOptions options, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions, System.Threading.CancellationToken cancellationToken) [0x0026b] in <5fe95be693194ddcbd71be16078d00c8>:0
at Emby.Providers.Manager.MetadataService`2[TItemType,TIdType].RunCustomProvider (MediaBrowser.Controller.Providers.ICustomMetadataProvider`1[TItemType] provider, MediaBrowser.Controller.Providers.MetadataResult`1[T] itemResult, System.String logName, MediaBrowser.Controller.Providers.MetadataRefreshOptions options, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions, Emby.Providers.Manager.RefreshResult refreshResult, System.Threading.CancellationToken cancellationToken) [0x000df] in <5fe95be693194ddcbd71be16078d00c8>:0
Source: mscorlib
TargetSite: Void Throw()
 
2024-06-21 01:04:31.740 Info App: ProcessRun 'StreamTranscode 57d6f7' Execute: /var/packages/EmbyServer/target/bin/ffmpeg -y -copyts -start_at_zero -i "/path/to/file/DSC-H50/MOV07979.MPG" -vn -an -sn -max_delay 5000000 -avoid_negative_ts disabled -f segment -map_metadata -1 -map_chapters -1 -segment_format mpegts -segment_list "/var/packages/EmbyServer/var/transcoding-temp/DF6BE4/DF6BE4.m3u8" -segment_list_type m3u8 -segment_time 00:00:03.000 -segment_list_entry_prefix hls/DF6BE4/ -segment_start_number 0 -individual_header_trailer 0 -write_header_trailer 0 "/var/packages/EmbyServer/var/transcoding-temp/DF6BE4/DF6BE4_%d.ts"
2024-06-21 01:04:32.430 Info App: ProcessRun 'StreamTranscode 57d6f7' Process exited with code 132 - Failed
2024-06-21 01:04:32.445 Error Server: Error processing request
*** Error Report ***
Version: 4.8.8.0
Command line: /volume2/@appstore/EmbyServer/system/EmbyServer.exe -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -defaultdirectory /volume1/Public -updatepackage emby-server-synology7-mono_{version}_armv7_legacy.spk -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -nolocalportconfig -noskia -ignore_vaapi_enabled_flag
Operating system: Linux version 3.2.101 (root@build3) (gcc version 8.5.0 (GCC) ) #42962 Mon May 29 14:34:16 CST 2023
Framework: Mono: 6.12.0.182 (tarball Thu Jan 19 10:28:52 PM UTC 2023)
OS/Process: X86/X86
Runtime: volume2/@appstore/EmbyServer/lib/mono/4.5/mscorlib.dll
Processor count: 1
Data path: /var/packages/EmbyServer/var
Application path: /volume2/@appstore/EmbyServer/system
Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Error starting ffmpeg
-y -copyts -start_at_zero -i "/path/to/file/DSC-H50/MOV07979.MPG" -vn -an -sn -max_delay 5000000 -avoid_negative_ts disabled -f segment -map_metadata -1 -map_chapters -1 -segment_format mpegts -segment_list "/var/packages/EmbyServer/var/transcoding-temp/DF6BE4/DF6BE4.m3u8" -segment_list_type m3u8 -segment_time 00:00:03.000 -segment_list_entry_prefix hls/DF6BE4/ -segment_start_number 0 -individual_header_trailer 0 -write_header_trailer 0 "/var/packages/EmbyServer/var/transcoding-temp/DF6BE4/DF6BE4_%d.ts"
 
 
 
 
 
at Emby.Server.MediaEncoding.Api.BaseStreamingService.StartFfMpeg (Emby.Server.MediaEncoding.Api.StreamState state, System.String outputPath, System.Threading.CancellationToken cancellationToken, System.Boolean acquireResources) [0x006b3] in <59b0c601cefc4f678dca703e2fad3041>:0
at Emby.Server.MediaEncoding.Api.Hls.BaseHlsService.ProcessRequest (Emby.Server.MediaEncoding.Api.StreamState state, Emby.Server.MediaEncoding.Api.StreamRequest request) [0x001d8] in <59b0c601cefc4f678dca703e2fad3041>:0
at Emby.Server.MediaEncoding.Api.Hls.DynamicHlsService.Get (Emby.Server.MediaEncoding.Api.Hls.GetLiveHlsStream request) [0x00212] in <59b0c601cefc4f678dca703e2fad3041>:0
at Emby.Server.Implementations.Services.ServiceController.GetTaskResult (System.Threading.Tasks.Task task) [0x00081] in <f1f641b7295f4057b4606b39fbea98af>:0
at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync (Emby.Server.Implementations.HttpServer.HttpListenerHost httpHost, MediaBrowser.Controller.IServerApplicationHost appHost, MediaBrowser.Model.Services.IRequest httpReq, MediaBrowser.Model.Services.IResponse httpRes, MediaBrowser.Model.IO.IStreamHelper streamHelper, Emby.Server.Implementations.Services.RestPath restPath, System.String responseContentType, System.Threading.CancellationToken cancellationToken) [0x0018d] in <f1f641b7295f4057b4606b39fbea98af>:0
at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler (MediaBrowser.Model.Services.IRequest httpReq, System.ReadOnlyMemory`1[T] urlString, System.ReadOnlyMemory`1[T] localPath, System.Threading.CancellationToken cancellationToken) [0x00acb] in <f1f641b7295f4057b4606b39fbea98af>:0
Source: mscorlib
TargetSite: Void Throw()

 

Happy2Play
Posted

I guess the question becomes it 4.7.14.0 the last working version that will work on these Legacy systems?

Or is this issue specific to FFMPEG v5.0 and v5.1?

 

Posted
8 minutes ago, Happy2Play said:

I guess the question becomes it 4.7.14.0 the last working version that will work on these Legacy systems?

Or is this issue specific to FFMPEG v5.0 and v5.1?

 

No the issue is most likely that we've updated some library to a newer version and the DS414Slim can't handle it. That's usually what this sort of issue comes down to.

I will check with our build developer. 

This is a 2014 NAS !!

Happy2Play
Posted
4 minutes ago, Luke said:

This is a 2014 NAS !!

True and last OS update is Version: 7.1.1-42962 Update 6 last year. 

 

Posted

nice. Will wait once you release smth. If you need more tests on slim414 - let me know...

  • 2 weeks later...
icegood
Posted

Still doesn't work. As i see you use crosstool-ng to generate native parts. Could you please share defcionfig for it and my platform (marvel armada 370) so I will check, whether generated code really creates code against my CPU? Wouldn't it break your NDA? 

For now I run  ffmgeg directly from your emby-ffmpeg:

Quote

#!/bin/sh

APP_DIR=/var/packages/EmbyServer/target
#APP_DIR2=/volume2/@appstore/EmbyServer_4.7.14.0

export FONTCONFIG_PATH=$APP_DIR/etc/fonts
export LD_LIBRARY_PATH=$APP_DIR/lib
export PCI_IDS_PATH=$APP_DIR/share/hwdata/pci.ids
export SSL_CERT_FILE=$APP_DIR/etc/ssl/certs/ca-certificates.crt

cd $APP_DIR || exit 1

exec bin/ffmpeg "$@"
 

script and obtained "illegal instruction". So it is a problem with either instruction generation or inconsistency between ffmpeg and libraries...

  • 3 weeks later...
Posted

Hi, have you tried the 4.8 build that was released in Synology package center?

  • 2 weeks later...
Posted

no ,i hadn't checked. However, i found something interest in your libraries of ver_4.9.0.26.

My CPU is:

Quote

Architecture:           armv7l
  Byte Order:           Little Endian
CPU(s):                 1
  On-line CPU(s) list:  0
Vendor ID:              Marvell
  Model name:           PJ4/PJ4b
    Model:              1
    Thread(s) per core: 0
    Core(s) per socket: 0
    Socket(s):          0
    Stepping:           0x1
    BogoMIPS:           1196.85
    Flags:              swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 tls
 


readelf -A ffmpeg is:

Quote

Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "7-A"
  Tag_CPU_arch: v7
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3-D16
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: int
  Tag_CPU_unaligned_access: v6
 

and it looks OK. But readelf -A libavcodec.so:
 

Quote

Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "7-A"
  Tag_CPU_arch: v7
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3
  Tag_Advanced_SIMD_arch: NEONv1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_enum_size: int
  Tag_CPU_unaligned_access: v6

Why the hell you substitute library with another ABI? My proc doesn't have neon instructions and flag 

  Tag_Advanced_SIMD_arch: NEONv1 is very suspicious!

alucryd
Posted

Our toolchain is fine, always has been. Unfortunately we don't live in a perfect world, especially when it comes to cross compiling. Some libraries will happily modify your build flags without telling you, the culprit is either an updated or new library, just need to find which one.

alucryd
Posted

4 evil libs were identified and tamed. The next beta should work fine, we should be able to backport these in a new stable later on.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...