Jump to content

ffprobe errors on Raspberry Pi 3 when scanning library


embidia
 Share

Recommended Posts

embidia

I'm getting a bunch of ffprobe error in my logs when Emby is scanning the library and at some point the system becomes overloaded and hangs. It scans 10 to 30 items correctly, then becomes unresponsive. Each item throws an error.

 

I have tried the suggested builds for ffmpeg (https://johnvansickle.com/ffmpeg/) and I've tried compiling it on the Pi. I get the same errors. I don't know if these errors are the cause for the overloading and hanging.

 

I'm using the latest emby-server and mono 4.8.1.

 

This is a typical error:

2017-05-12 13:22:53.4285 Debug App: Running FFProbeProvider for smb://dd-wrt/blue/kodi/movies/xx.mp4
2017-05-12 13:22:53.4285 Debug MediaEncoder: ffprobe -i "smb://dd-wrt/blue/kodi/movies/xx.mp4" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format
2017-05-12 13:22:54.1954 Error App: Error in ffprobe
	*** Error Report ***
	Version: 3.2.15.0
	Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh
	Operating system: Unix 4.9.24.7
	64-Bit OS: False
	64-Bit Process: False
	Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Wed Apr 12 12:47:01 UTC 2017)
	Processor count: 4
	Program data path: /var/lib/emby-server
	Application directory: /usr/lib/emby-server/bin
	System.Exception: ffprobe failed - streams and format are both null.
	  at MediaBrowser.MediaEncoding.Encoder.MediaEncoder+<GetMediaInfoInternal>c__async2.MoveNext () [0x00187] in <f5a4bf3a7ff54e6a821f5228b0c5fe2e>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.MediaInfo.FFProbeVideoInfo+<GetMediaInfo>c__async1.MoveNext () [0x00102] in <840b94d084fb49ffaff74b10e89ad590>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.MediaInfo.FFProbeVideoInfo+<ProbeVideo>c__async0`1[T].MoveNext () [0x00321] in <840b94d084fb49ffaff74b10e89ad590>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.Manager.MetadataService`2+<RunCustomProvider>c__async7[TItemType,TIdType].MoveNext () [0x000db] in <840b94d084fb49ffaff74b10e89ad590>:0 
	System.Exception
	  at MediaBrowser.MediaEncoding.Encoder.MediaEncoder+<GetMediaInfoInternal>c__async2.MoveNext () [0x00187] in <f5a4bf3a7ff54e6a821f5228b0c5fe2e>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.MediaInfo.FFProbeVideoInfo+<GetMediaInfo>c__async1.MoveNext () [0x00102] in <840b94d084fb49ffaff74b10e89ad590>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.MediaInfo.FFProbeVideoInfo+<ProbeVideo>c__async0`1[T].MoveNext () [0x00321] in <840b94d084fb49ffaff74b10e89ad590>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	  at MediaBrowser.Providers.Manager.MetadataService`2+<RunCustomProvider>c__async7[TItemType,TIdType].MoveNext () [0x000db] in <840b94d084fb49ffaff74b10e89ad590>:0 

What may I be doing wrong?

 

Thanks!

Link to comment
Share on other sites

embidia

I've been trying to fix this for days and, of course, five minutes after posting here I found the fix. Ffprobe couldn't get the info from a samba share directly. So, after mounting the share as a local drive I don't see this kind of error in the logs any more. I can't tell if the server will be overloaded anyway yet.

 

Nothing to see here, move along! :-)

Link to comment
Share on other sites

@@embidia, we've recently added native smb support to emby, however we need to update our installation instructions to mention that ffmpeg needs to be compiled with smb support. That is why you were getting that error. What you've done is fine as a workaround though. Thanks !

  • Like 1
Link to comment
Share on other sites

embidia

Thanks, it's good to know. I didn't compile ffmpeg with samba support.

 

The server still crashes and burns. Some other errors are popping up in the logs but I'm not sure they're enough to be the main culprit. I'm resetting my pi and slowly progressing through indexing all the library. Hopefully when it's done it won't keep crashing as often.

Link to comment
Share on other sites

embidia

Just a followup. I switched to Dietpi as OS and my RPI 3 works much better than with the regular Jessie. I have Sonarr+Radarr+Transmission+Emby working fairly well. Love emby! Thanks for your generosity.

Link to comment
Share on other sites

tdiguy

Just a followup. I switched to Dietpi as OS and my RPI 3 works much better than with the regular Jessie. I have Sonarr+Radarr+Transmission+Emby working fairly well. Love emby! Thanks for your generosity.

I have been trying to get dietpi to work but i have had nothing but headaches trying to set it up. Was there a process you can point me to? I found it weird, it seems dietpi does not work well on my 64gig microsd card and the 2gig almost worked.

Link to comment
Share on other sites

embidia

I have been trying to get dietpi to work but i have had nothing but headaches trying to set it up. Was there a process you can point me to? I found it weird, it seems dietpi does not work well on my 64gig microsd card and the 2gig almost worked.

Well, to be honest. yesterday I finally removed emby-server from my pi. "Fairly well" wasn't enough. Emby was causing the pi to hang randomly and I wanted it to work unattended for weeks. I had to restart emby-server or reboot maybe daily or every other day. When it worked it worked fine but I couldn't figure out what the problem was.

 

So now I'm bypassing emby and using Sonarr, Radarr, and Transmission on the pi, and I'm pointing Kodi directly to the samba share. I still like emby very much but I can't make it work flawlessly on the pi.

 

As to diepi, I didn't do anything special, just installed it. I like the managing tools it comes with. With them, It's very simple to configure and use the pi.

 

I'm sorry I can't be of much help.

Link to comment
Share on other sites

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
 Share

×
×
  • Create New...