Page 1 of 1

New can't find ffmpeg error

PostPosted: Thu May 15, 2014 12:13 am
by walnut23
I've been running serviio on Freebsd for a couple of years, building it and its dependencies out of the FreeBSD ports collection. I'm currently running FreeBSD 10.0-STABLE. When I updated the system recently and built the latest serviio I started having problems. Specifically, it's the old "can't find ffmpeg" issue - the log says

2014-05-14 16:59:49,202 ERROR [ProcessExecutor] Fatal error in process starting: Cannot run program "/usr/local/bin/ffmpeg": error=2, No such file or directory
java.io.IOException: Cannot run program "/usr/local/bin/ffmpeg": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at org.serviio.external.ProcessExecutor.run(ProcessExecutor.java:135)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:184)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
... 1 more

Of course ffmpeg is installed at /usr/local/bin:

% which ffmpeg
/usr/local/bin/ffmpeg
% ffmpeg -version
ffmpeg version 2.1.1

and I've had a "-D" in my startup to set the ffmpeg location, as described elsewhere on this site, for quite some time.

Why else would serviio choke and not be able to find the ffmpeg executable?

Re: New can't find ffmpeg error

PostPosted: Thu May 15, 2014 6:22 pm
by zip
access rights?

Re: New can't find ffmpeg error

PostPosted: Fri May 16, 2014 12:15 am
by walnut23
Unfortunately it doesn't look like it:

% ls -l /usr/local/bin/ffmpeg
-rwxr-xr-x 1 root wheel 179760 Apr 28 22:13 /usr/local/bin/ffmpeg*

Re: New can't find ffmpeg error

PostPosted: Tue May 20, 2014 5:53 am
by walnut23
This turned out to be an OpenJDK7 issue. Updating my system today and the ports notes mention that there was an issue with the last release of OpenJDK7, deinstall and install the new version to clean it up properly. After that (along with wiping Serviio data again) Serviio is back to indexing properly.