Search the Community

Hi, it looks like emby-server is running (`systemctl status emby-server` and `ps aux|grep emby` both show the server running). But when I try to navigate to `localhost:8086` I get the error that the connection for localhost is refused. I am running a freshly installed version of Manjaro-XFCE. Looking in the `embyserver.txt` file in /var/lib/private/emby/logs, I see a few processes that failed out with errors: ``` 2023-02-08 22:09:56.670 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /usr/bin/ffdetect-emby -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json 2023-02-08 22:09:56.760 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 139 - Failed 2023-02-08 22:09:56.812 Error VaapiCodecProvider: Error running ffdetect for vaencdec - ffdetect version 5.0.0-emby_2022_05_07 Copyright (c) 2018-2022 softworkz for Emby LLC built with gcc 8.3.0 (crosstool-NG 1.24.0) configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffdetect-x64/staging --pkg-config=pkg-config --disable-debug --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-vdpau --enable-libdrm --enable-libmfx --enable-vaapi --extra-libs='-ldrm -lva -lva-drm -ldl -lm -pthread' --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --disable-shared --enable-static libavutil 57. 19.100 / 57. 19.100 Begin GetVaAdapterInfo Found 17 device entries Begin get_nodes Found 2 drm entries End GetVaAdapterInfo 2023-02-08 22:09:56.812 Error VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Output: 2023-02-08 22:09:56.812 Error VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Error Output: ffdetect version 5.0.0-emby_2022_05_07 Copyright (c) 2018-2022 softworkz for Emby LLC built with gcc 8.3.0 (crosstool-NG 1.24.0) configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffdetect-x64/staging --pkg-config=pkg-config --disable-debug --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-vdpau --enable-libdrm --enable-libmfx --enable-vaapi --extra-libs='-ldrm -lva -lva-drm -ldl -lm -pthread' --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --disable-shared --enable-static libavutil 57. 19.100 / 57. 19.100 Begin GetVaAdapterInfo Found 17 device entries Begin get_nodes Found 2 drm entries End GetVaAdapterInfo 2023-02-08 22:09:56.817 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Execute: /usr/bin/ffdetect-emby -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 qsvencdec -print_format json 2023-02-08 22:09:56.907 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code 139 - Failed 2023-02-08 22:09:56.957 Error QuickSyncCodecProvider: Error running ffdetect for qsvencdec - ffdetect version 5.0.0-emby_2022_05_07 Copyright (c) 2018-2022 softworkz for Emby LLC built with gcc 8.3.0 (crosstool-NG 1.24.0) configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffdetect-x64/staging --pkg-config=pkg-config --disable-debug --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-vdpau --enable-libdrm --enable-libmfx --enable-vaapi --extra-libs='-ldrm -lva -lva-drm -ldl -lm -pthread' --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --disable-shared --enable-static libavutil 57. 19.100 / 57. 19.100 Begin GetVaAdapterInfo Found 17 device entries Begin get_nodes Found 2 drm entries End GetVaAdapterInfo 2023-02-08 22:09:56.957 Error QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Output: 2023-02-08 22:09:56.957 Error QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Error Output: ffdetect version 5.0.0-emby_2022_05_07 Copyright (c) 2018-2022 softworkz for Emby LLC built with gcc 8.3.0 (crosstool-NG 1.24.0) configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffdetect-x64/staging --pkg-config=pkg-config --disable-debug --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-vdpau --enable-libdrm --enable-libmfx --enable-vaapi --extra-libs='-ldrm -lva -lva-drm -ldl -lm -pthread' --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --disable-shared --enable-static libavutil 57. 19.100 / 57. 19.100 Begin GetVaAdapterInfo Found 17 device entries Begin get_nodes Found 2 drm entries End GetVaAdapterInfo ``` When I run: `$ /usr/bin/ffdetect-emby -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json`, I don't see any errors or failed msgs. Any ideas or suggestions to get past this issue and up and running? Thks.

I see the option for shutdown in the server dashboard...

Hi all, I'm facing an interesting problem by using the FireTV 1.3.19a app: When I navigate to Live-TV and click on "TV prgramm" (doesn't know how it is called in english, in german it is called "TV Programmübersicht") to see an EPG, the app is just showing the circle spinner. I tried to wait about 20 minutes and then I cancelled this. When I connect to web GUI of the same emby server, everything works fine. The EPG shows up after 3-4 seconds. Im using NextPVR on the same machine where emby server runs and all is running in my LAN. I have attached log files. One log file is where Im using the WebGui and one log is showing a try to use FireTV emby app. My server version is 3.2.1.0 and the NextPVR plugin has version 3.0.6143.20454 Background: I have another physical machine with WIndows 7 and Windows Media Center and ServerWMC, which I used before and with this setup the FireTV app shows the EPG without any problem. The new server with NextPVR ist running Windows 10 and will replace the Windows 7 server. Need help here. Thank you. Update: I found log of NextPVR and attached an sample to this post. It does show requests for the same SID and no errors. So emby server is asking about EPG data I think..... Log-FireTV-EPG-problem.txt Log-WebGUI-EPG-problem.txt Log-NextPVR-EPG-problem.txt