Jump to content

ffprobe timeout causing very large logs

Aquid

By Aquid
in Linux

 Share

Recommended Posts

Aquid

Aquid   0

Posted
Posted

Hi,

 
I have Emby server on a Raspberry Pi 3B+ with DietPi and whenever certain video files are scanned (HEVC codec is the only similarity I noticed) my embyserver logs are growing by the size of the video file. After taking a closer look at the logs, it appears to be a problem with ffprobe. Whenever ffprobe is ran, it times out and I receive following error: 
2019-02-20 02:38:50.029 Debug MediaEncoder: Ffprobe -i file:"/path/myvideo.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-02-20 02:38:50.029 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /opt/emby-server/bin/ffprobe -i file:"/path/myvideo.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-02-20 02:38:50.085 Info MediaEncoder: ProcessRun 'ffprobe' Started.
2019-02-20 02:39:20.103 Error MediaEncoder: Timeout while running Ffprobe -i file:"/path/myvideo.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-02-20 02:39:20.654 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 137
2019-02-20 02:39:25.278 Error MediaEncoder: ProcessRun 'ffprobe' Output:
	{
	    "streams": [
	        {
	            "index": 0,
	            "codec_name": "hevc",
	            "codec_long_name": "H.265 / HEVC (High Efficiency Video Coding)",
	            "profile": "Main 10",
	            "codec_type": "video",
	            "codec_time_base": "1001/24000",
	            "codec_tag_string": "[0][0][0][0]",
	            "codec_tag": "0x0000",
	            "width": 1440,
	            "height": 1080,
	            "coded_width": 1440,
	            "coded_height": 1080,
	            "has_b_frames": 2,
	            "sample_aspect_ratio": "1:1",
	            "display_aspect_ratio": "4:3",
	            "pix_fmt": "yuv420p10le",
	            "level": 120,
	            "color_range": "tv",
	            "refs": 1,
	            "r_frame_rate": "24000/1001",
	            "avg_frame_rate": "24000/1001",
	            "time_base": "1/1000",
	            "start_pts": 0,
	            "start_time": "0.000000",
	            "extradata": "\n00000000: 0102
followed by a lot of data, which I assume to be the video in some form.
 
This happens during library scans and also when I try to play one of these files. In the latter case the file won't even start playing until the timeout occurs. During playback there are no problems.
 

 

which doesn't appear to be resolved yet.
 
After doing a clean reinstall of Emby server several times I tried downgrading to different versions. Everything works fine in 3.5.2.0 and 3.5.3.0: logs are kept small and playback begins immediately. On 4.0.0.2 and above, I get these issues.
 
A workaround I use right now is downgrading to 3.5.3.0, doing a successful library scan, then upgrading to 4.0.2.0 and playback works fine.

 

Link to comment
Share on other sites
Aquid

Aquid   0

Posted
  • Author
Posted (edited)

Here you go. The log is actually not quite as big as the video file, more like one fifth of the size. But that still makes the logs fill up too quickly (which is a pain on a 8GB SD). 

Also tried removing every plugin installed, same result.

embyserver-63686280283.txt

Edited by Aquid
Link to comment
Share on other sites
Aquid

Aquid   0

Posted
  • Author
Posted

I just tried out the latest beta (version 4.1.0.8) and unfortunately I still receive the exact same error.

What I additionally noticed is that not only playback is affected, but the whole server becomes unresponsive for about 30 seconds every time this timeout occurs.

Also, Emby's RAM usage spikes up to 100% in those moments, as opposed to usually about 10%.

Link to comment
Share on other sites
Aquid

Aquid   0

Posted
  • Author
Posted

I tried the new update 4.1.0.10 to see if this was fixed, but now emby server won't even start:

root@DietPi:~# systemctl status emby-server.service 
● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-02-27 07:00:04 GMT; 1min 49s ago
  Process: 1620 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=126)
 Main PID: 1620 (code=exited, status=126)

Feb 27 07:00:04 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just a
Feb 27 07:00:04 DietPi systemd[1]: emby-server.service: Main process exited, code=exited, status=126/
Feb 27 07:00:04 DietPi systemd[1]: emby-server.service: Unit entered failed state.
Feb 27 07:00:04 DietPi systemd[1]: emby-server.service: Failed with result 'exit-code'.

I found some older threads with a similar problem: https://emby.media/community/index.php?/topic/43279-update-ubuntu-16041-and-emby-emby-don´t-start/

where the solution was completely removing and reinstalling emby server. Did not work for me unfortunately, same result.

 

Also I can't find out the ffprobe version this time. No logs exists and when I try to run ffprobe:

root@DietPi:/opt/emby-server/bin# /opt/emby-server/bin/ffprobe 
-bash: /opt/emby-server/bin/ffprobe: No such file or directory

even though the file exists:

root@DietPi:/opt/emby-server/bin# ls -alh
total 356K
drwxr-xr-x 2 root root 4.0K Feb 27 06:59 .
drwxr-xr-x 8 root root 4.0K Feb 27 06:58 ..
-rwxr-xr-x 1 root root  896 Aug 21  2017 emby-server
-rwxr-xr-x 1 root root  38K Aug 21  2017 ffdetect
-rwxr-xr-x 1 root root 190K Aug 21  2017 ffmpeg
-rwxr-xr-x 1 root root 109K Aug 21  2017 ffprobe

And finally, these are all the contents of /var/lib/emby, which does not seem right to me:

root@DietPi:/var/lib/emby# ls -alh
total 20K
drwxr-xr-x  2 emby emby 4.0K Feb 27 07:13 .
drwxr-xr-x 20 root root 4.0K Feb 27 07:00 ..
-rw-r--r--  1 emby emby  220 May 15  2017 .bash_logout
-rw-r--r--  1 emby emby 3.5K Mar 13  2018 .bashrc
-rw-r--r--  1 emby emby  675 May 15  2017 .profile

I guess I should wait for the next update, or is there something I can do now?

Link to comment
Share on other sites
Aquid

Aquid   0

Posted
  • Author
Posted

I can confirm that with the updated .deb for version 4.1.0.10 I am not experiencing this issue anymore.

Great work and thanks for the 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
Go to topic listing
×
×
  • Create New...