Serviio

Posted: **Fri Feb 23, 2024 3:49 pm**

Hello,

In the distant past I've had Serviio working, now at somepoint it has failed to launch the console. I've updated to 2.3 and the results are much the same but fails to start the server.

I've a QNAP 439-II Pro and having checked the log, it seems its falling over finding ffmpeg.

2024-02-23T14:49:50,198 INFO [PluginCompilerThread] Looking for plugins at /share/MD0_DATA/.qpkg/Serviio/plugins
2024-02-23T14:49:50,205 INFO [PluginCompilerThread] Started looking for plugins
2024-02-23T14:49:50,210 INFO [UpdateChecker] Checking if a new version is available
2024-02-23T14:49:50,217 INFO [PluginCompilerThread] Finished looking for plugins
2024-02-23T14:49:50,316 ERROR [MediaServer] An unexpected error occurred. Ending the application. Message: FFMPEG not found. Serviio will not work properly.
java.lang.ExceptionInInitializerError: null
at org.serviio.MediaServer.main(MediaServer.java:147) ~[serviio.jar:?]
Caused by: java.lang.RuntimeException: FFMPEG not found. Serviio will not work properly.
at org.serviio.external.FFMPEGWrapper.loadFFmpegInfo(FFMPEGWrapper.java:123) ~[serviio.jar:?]
at org.serviio.external.FFMPEGWrapper.<clinit>(FFMPEGWrapper.java:96) ~[serviio.jar:?]
... 1 more

thing is, ffmpeg is in the serviio directory and runs ?

[/share/MD0_DATA/.qpkg/Serviio/log] # ffmpeg
ffmpeg version 0.8.10, Copyright (c) 2000-2011 the FFmpeg developers
built on Jan 31 2024 02:51:44 with gcc 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
configuration: --prefix=/opt/cross-project/x86/sys-root/usr --disable-static --enable-shared --disable-yasm --enable-gpl --disable-encoder=snow --disable-decoder=ac3 --disable-decoder=ac3_fixed --disable-decoder=eac3 --disable-decoder=dca --disable-decoder=truehd --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-encoder=dca --disable-decoder=snow
libavutil 51. 9. 1 / 51. 9. 1
libavcodec 53. 8. 0 / 53. 8. 0
libavformat 53. 5. 0 / 53. 5. 0
libavdevice 53. 1. 1 / 53. 1. 1
libavfilter 2. 23. 0 / 2. 23. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

any help would be greatly appreciated.

Posted: **Fri Feb 23, 2024 7:38 pm**

If I'm seeing that correctly, your copy of FFMPEG is in the Serviio/log folder. That is not the correct location. At least on my Windows installs, FFMPEG is in the Serviio/lib folder, and that is where Serviio expects it to be. There is a configuration entry for the system file that can point to an alternate location for FFMPEG, but it's really best to keep it where it belongs.

Posted: **Fri Feb 23, 2024 11:35 pm**

Thanks for the reply. I've moved on since my earlier post. In answer to your question yes your observation was right I happened to be in the wrong directory when I happened to run it. The actual location and the default 2.3 install for ffmpeg on the QNAP is in the Serviio root directory, I've not moved ffmpeg.

It does appear to point to serviio not seeing the location thou, so with that in mind i installed static versions of ffmpeg and ffserver into my /usr/bin $PATH and got better results in that the log has moved on past the ffmpeg error but presented a new one.

The console loads up regularly now, but the status retuens "server does not appear to be running", with a degree of malformed screen tags for the fields i.e {{'tab_status_renderer_table_device_name' | translate}}

2024-02-23T23:04:02,184 WARN [ServiioStatusService] Returning error code to the REST layer: Bad Request (400) - The request could not be understood by the server due to malformed syntax
2024-02-23T23:04:06,908 INFO [FileDeltaWatcher] Using 'sun.nio.fs.LinuxWatchService' for delta scan
2024-02-23T23:04:18,603 INFO [FeedUpdaterWorker] Started looking for information about online resources
2024-02-23T23:04:18,610 INFO [RepositoriesStatusCoordinator$RepositoriesStatusThread] Started checking repositories status
2024-02-23T23:04:18,759 INFO [LocalLibraryManager] Starting automatic library scan
2024-02-23T23:04:18,764 INFO [LibraryDeltaScanner] Starting the library delta scan
2024-02-23T23:04:18,769 INFO [PlaylistMaintainerWorker] Started looking for playlist changes
2024-02-23T23:04:27,333 WARN [ServiioStatusService] Returning error code to the REST layer: Bad Request (400) - The request could not be understood by the server due to malformed syntax

EDIT: OK, it seems the server is working (checked a DLNA app on my iPhone and serviio was listed) so tried Chrome on my mac and looks OK, so its Safari issue. Still I'd like to know what the Bad Request (400) is !?

Posted: **Fri Feb 23, 2024 11:48 pm**

With the way the NAS companies have modified their operating systems, I'm not surprised Serviio is now encountering issues. Since I don't use a NAS, and have no experience with the way their OS operates, I'll need to defer this to someone with more experience. I will remind you that the Serviio developer does not create the NAS builds. He provides the Windows/Mac/Linux builds and others make the changes needed to run on a NAS. I'm going to move this thread into the NAS subfolder, where someone with more knowledge in this area might be able to assist.

Posted: **Sat Feb 24, 2024 12:04 am**

Thanks, I didn't know that.

Been on this 12 hours or so now and finally some success, its now indexing

. Seems the server is working (checked a DLNA app on my iPhone and serviio was listed) so tried Chrome on my mac and looks OK, so its a Safari issue. Still I'd like to know what the Bad Request (400) is !? so hopefully the NAS guys will be able to help

Serviio

failing to find ffmpeg on QNAP ?

failing to find ffmpeg on QNAP ?

Re: failing to find ffmpeg on QNAP ?

Re: failing to find ffmpeg on QNAP ?

Re: failing to find ffmpeg on QNAP ?

Re: failing to find ffmpeg on QNAP ?