FFmpeg invocation error following Synology DSM update
|
04-07-2014, 09:17
Post: #1
|
|||
|
|||
FFmpeg invocation error following Synology DSM update
Hi Simon, I updated my DS710+ to DSM 5.0-4493 Update 2 last night and noticed that minimserver is no longer being seen by my naim kit.
Checked the log and have the following error: "Streamer: test invocation of FFmpeg failed to complete" Do I need to reinstall something following the update, or has the update broken something? regards Nick |
|||
04-07-2014, 11:57
(This post was last modified: 04-07-2014 12:01 by simoncn.)
Post: #2
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
(04-07-2014 09:17)stampie Wrote: Hi Simon, I updated my DS710+ to DSM 5.0-4493 Update 2 last night and noticed that minimserver is no longer being seen by my naim kit. I am on the same firmware level and I'm not seeing this problem. This might happen if the CPU or HDD is very busy with other activity when MinimServer is started. You could try rebooting the NAS to see if this fixes it. If you still get the problem after a reboot, log in to the NAS using SSH and type the command: ffmpeg What output do you get? |
|||
04-07-2014, 12:07
Post: #3
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
(04-07-2014 11:57)simoncn Wrote:(04-07-2014 09:17)stampie Wrote: Hi Simon, I updated my DS710+ to DSM 5.0-4493 Update 2 last night and noticed that minimserver is no longer being seen by my naim kit. I had the very same error message two times right after updating the DSM firmware on my DS211. For me, stopping and starting MinimServer from the Synology package center fixed the problem. |
|||
04-07-2014, 12:16
(This post was last modified: 04-07-2014 12:16 by simoncn.)
Post: #4
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
(04-07-2014 12:07)winxi Wrote: I had the very same error message two times right after updating the DSM firmware on my DS211. For me, stopping and starting MinimServer from the Synology package center fixed the problem. This suggests that other CPU or HDD activity while MinimServer was starting is the cause of the problem. You will get this message if MinimStreamer doesn't get a response from FFmpeg within approximately 3 seconds. It's likely that the update is creating significant CPU or HDD activity during the first reboot after the update was applied. |
|||
04-07-2014, 12:19
Post: #5
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
Problem persists: FFmpeg output below:
ffmpeg version 2.0.2 Copyright © 2000-2013 the FFmpeg developers built on Apr 14 2014 16:42:11 with gcc 4.6.3 (crosstool-NG 1.17.0) configuration: --prefix=/usr/syno --incdir='${prefix}/include/ffmpeg' --arch=i686 --target-os=linux --cross-prefix=/usr/local/i686-pc-linux-gnu/bin/i686-pc-linux-gnu- --enable-cross-compile --enable-optimizations --enable-pic --enable-gpl--enable-shared --disable-static --enable-version3 --enable-nonfree --enable-libfaac --enable-encoders --enable-pthreads --disable-bzlib --disable-protocol=rtp --disable-muxer=image2 --disable-muxer=image2pipe --disable-swscale-alpha --disec --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libmp3lame --disable-decoder=amrnb --disable-encoder=zmbv --disable-encoder=dca --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-decoder=dca--disable-decoder=eac3 --disable-decoder=truehd --cc=/usr/local/i686-pc-linux-gnu/bin/i686-pc-linux-gnu-ccache-gcc --enable-yasm --enable-libx264 --enable-encoder=libx264 libavutil 52. 38.100 / 52. 38.100 libavcodec 55. 18.102 / 55. 18.102 libavformat 55. 12.100 / 55. 12.100 libavdevice 55. 3.100 / 55. 3.100 libavfilter 3. 79.101 / 3. 79.101 libswscale 2. 3.100 / 2. 3.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 3.100 / 52. 3.100 Hyper fast Audio and Video encoder usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}... regards Nick |
|||
04-07-2014, 12:41
Post: #6
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
The option of turning Minimserver off and on within package centre has now worked for me.
Will I need to do this everytime I reboot the NAS though going forward? It hasn't happen with earlier version of the DSM Nick |
|||
04-07-2014, 16:34
Post: #7
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
(04-07-2014 12:41)stampie Wrote: The option of turning Minimserver off and on within package centre has now worked for me. It seems that the new version of DSM is doing something on startup that is consuming more CPU or HDD resources than previous versions. This is delaying the reponse from FFmpeg. I'm slightly surprised, as FFmpeg is responding in 26 ms on my DS713+. I will increase the maximum timeout value from about 3 seconds to about 20 seconds. This should be sufficient to prevent this problem. |
|||
06-07-2014, 22:02
Post: #8
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
Just a quick update on this topic.
I experienced this problem on a DS710+. This evening I have updated my DS214play, and did not experience any problems at all. Nick |
|||
28-07-2014, 10:35
Post: #9
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
I am seeing this message a lot recently, every time I rescan after adding new music. Restarting fixes it, but often not on the first attempt. I only have a DS110j - could it be its CPU is not powerful enough to cope with a rescan on top of whatever DSM is doing at the time?
|
|||
28-07-2014, 11:56
Post: #10
|
|||
|
|||
RE: FFmpeg invocation error following Synology DSM update
(28-07-2014 10:35)scrutney2 Wrote: I am seeing this message a lot recently, every time I rescan after adding new music. Restarting fixes it, but often not on the first attempt. I only have a DS110j - could it be its CPU is not powerful enough to cope with a rescan on top of whatever DSM is doing at the time? A fix for this problem will be available soon. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)