Search the Community

Occasionally, Docker EMBY will be terminated in this way Info App: All entry points have started s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. emby.log

Hi there I'm currently in the process of moving away from Plex to Emby, I've my reasons but please don't forget about this below, I don't want to hurt any sensibility. So I recently noticed on a movie that I had huge artefacts/jumps when looking a film on my Chromecast. Some informations about my setup: Hardware is a Minisforum MS-01 Core i9-13900H, 96GB RAM and 2 TB disk OS is Almalinux 9 server I run Emby & Plex instances on Docker on this computer, GPU is "passthroughed" (with: - /dev/dri/renderD128:/dev/dri/renderD128) Emby version is 4.8.8.0 I didn't install any extra drivers Test protocol: The hardware is the same, so are Docker passthrough settings for Emby & Plex Movie is always the same, so the sequence (in my case, it's Hunger Games last episode, when Katniss is going alone to Panem in the plane, hiding behind a crate (sequence @ 29:00) Movie file is in 4K HDR 10 HEVC I started to look a little bit deeper because I suspect transcoding quality issues and this is what I found so far: Emby in Quicksync transcoding : very bad quality, the worst probably, a lot of artifacts (forced by deselecting VAAPI from advanced settings) Emby in VAAPI transcoding - VAAPI HW tone mapping : really dark, almost impossible to see artifacts, so I'll will not retain this Emby in VAAPI transcoding - Extra-T OpenCL tone mapping with Hable algorithm: quite a lot of artifacts, flat spots in dark areas, jumps Emby in VAAPI transcoding - Extra-T OpenCL tone mapping with Reinhard algorithm: seems better than Hable, but not really good Now : Plex : Auto quality with slow transcoding preset : no issue My Emby test instance : VM with Nvidia GPU passthroughed from ESX host to VM to Docker instance, NVDEC & Hable : no issue either I've to precise that I could always watch my movie, there is no play issue, only quality but I'd like to sort that out. It is also hard to describe it, you really have to see it. So, where do we start?

Mon serveur emby tourne sous docker, j’ai récemment refait ma configuration et depuis je n’ai plus de nouvelles de tmdb et tvdb. J’essaie de récupérer des informations sur les films ou les séries et c’est impossible. autre point: l’adresse ip de tous mes « clients », c’est à dire moi avec des iP différentes et des users différents, indique l’adresse locale de mon serveur (192.168.1.47). no comprendo Merci de votre aide ! embyserver.txt

Hi everyone, I need some help with setting up an Emby Docker container on my Raspberry Pi 4 running Rocky Linux 9. I'm using the following docker-compose.yml: services: emby: image: emby/embyserver_arm64v8:4.9.0.30 environment: - UID=1000 - GID=998 - GIDLIST=39,998 volumes: - ./config:/config - /mnt/extdrivea:/mnt/extdrive - ./test:/mnt/test ports: - 8096:8096 - 8920:8920 devices: - /dev/dri:/dev/dri - /dev/vchiq:/dev/vchiq # MMAL/OMX on Raspberry Pi restart: unless-stopped I found that the GID for the video and render groups are as follows: getent group video | cut -d: -f3 39 getent group render | cut -d: -f3 998 However, I'm having an issue where I don't see the hardware acceleration option in the Emby menu. This is what I see in the Transcoding log: The issue is that I don't see the hardware acceleration option in the Emby menu. Can anyone please advise me on what might be wrong? What settings should I check to ensure that hardware acceleration is working correctly? >>>>>> Processing Plan Name CanDoInHW WillDoInHW Reason Copy video stream >> False False Software Codec VideoInput >> False False Not a hardware decoder VideoOutput >> False False Not a hardware encoder Copy video stream >> False False Software Codec I have purchased a subscription for this feature, and I want to ensure that hardware acceleration works properly. Can anyone please advise me on what might be wrong? What settings should I check to ensure that hardware acceleration is functioning correctly?

I know there are dozens of threads on this topic - I think I've read them all. I normally wouldn't post, but I spent an entire day trying to figure this out and I'm finally stuck. The Setup Dell R730 Poweredge server NVIDIA Tesla M60 "server" graphics card Dual Intel Xeon E5 CPUs Proxmox VE 8.1.4 running on the bare metal Ubuntu 22.04.4 LTS running as a VM Docker 25.0.3 running inside Ubuntu Emby (Premiere) 4.8.1.0 So obviously there are a lot of layers. However, I successfully managed to get the NVIDIA M60 all the way through to Docker. I can verify this by running the sample Docker workload provided by NVIDIA, from the Ubuntu host: docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi This works fine: This would suggest to me that, from the hardware all the way through to Docker, it's possible for the software running in the container to get a handle on the M60. This is confirmed in the emby logs that follow, where you can see e.g. ** "VendorName": "NVIDIA Corporation", "DeviceName": "GM204GL [Tesla M60]" ** in the logs, suggesting that the Emby code is getting pretty damn close to negotiating with the GPU. I see the same driver version whether running this command via the nvidia docker image or just natively on my host terminal; this is probably expected but just confirming. The Problem I've tried both the linuxserver.io and the official emby docker container, and neither of them give me the option to use the M60 for transcoding: Other Information As you will see in both the hardware_detection and the embyserver logs, there is a lot of wrestling with the GPU, trying to set it up. But for whatever reason, it just fails. I've tried googling the various errors but haven't gotten anywhere. Container configuration The NVIDIA container runtime is installed I've tried dozens of different configs in my docker-compose, but at this point I'm running with a simple config that seems to work for a lot of other people, and produces the same errors as all the more complicated setups I've tried. In this setup, group 44 is `video` and group 109 is `render` on the host. Any help is much appreciated. I am a few minutes away from giving up here embyserver.txthardware_detection-63844435256.txt

Hi, i done a docker -it watch your record directory -extract srt -convert .ts to mkv or mp4 -process comchap or comcut on it. if 2-3 persons can test it and give me feedback, that will be nice. https://hub.docker.com/r/chacawaca/post-recording please use it with a test directory for now, keep DELETE_TS = 1 if you want to keep your .ts file thanks you

Hi everyone, I'm trying to get fail2ban working for Emby / Docker. Currently running in Ubuntu Mint Ubuntu 24.04 and have docker set to map the /config/logs directory to a local folder on the host. As far as I can tell I've got everything setup right but the filter is not matching anything it seems and it never logs failed logins to the jail. Also I don't recall where I noted them but I did see some weird charters in some kind of fail2ban logs for Emby. They were non-printable or invisible characters but I don't know that those would affect the regex especially since the manual regex test is passing. Does anyone have any ideas or see something overly obvious that I'm missing? Also worth nothing I manually tested the regex pattern and it matches. Docker Compose to map logs to local directory version: "2.3" services: emby: image: emby/embyserver:beta container_name: embyserver runtime: nvidia # Expose NVIDIA GPUs network_mode: host # Enable DLNA and Wake-on-Lan environment: - UID=1000 # The UID to run emby as (default: 2) - GID=1000 # The GID to run emby as (default 2) - GIDLIST=1000 # A comma-separated list of additional GIDs to run emby as (default: 2) #44,992 - NVIDIA_VISIBLE_DEVICES=all - NVIDIA_DRIVER_CAPABILITIES=compute,utility,video volumes: - /home/r3al/Desktop/Docker/Emby/programdata/:/config # Configuration directory - /media/r3al/New Volume/TT/TV/:/mnt/tv # Media directory - /media/r3al/New Volume/TT/Movies/:/mnt/movies # Media directory - /media/r3al/New Volume/TT/Live TV Recordings/:/mnt/mixed # Media directory - "/home/r3al/Desktop/Docker/Emby/logs/:/config/logs" ports: - 8096:8096 # HTTP port devices: # - /dev/nvidia-uvm:/dev/nvidia-uvm # Added nvidia devices here # - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools # Added nvidia devices here # - /dev/nvidia-modeset:/dev/nvidia-modeset # Added nvidia devices here # - /dev/nvidiactl:/dev/nvidiactl # Added nvidia devices here # - /dev/nvidia0:/dev/nvidia0 # Added nvidia devices here - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes - /dev/dri/renderD128:/dev/dri/renderD128 restart: on-failure /etc/fail2ban/filter.d/emby.conf [Definition] failregex = "http/1.1 Response 401 to ‌<HOST>" /etc/fail2ban/jail.d/emby.local [emby] enabled = true port = 8096 filter = emby logpath = /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt maxretry = 3 findtime = 600 bantime = 43200 Working manual regex test sudo fail2ban-regex /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt "http/1.1 Response 401 to ‌<HOST>" Manual Regex test returns Running tests ============= Use failregex line : http/1.1 Response 401 to ‌<HOST> Use log file : /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt Use encoding : UTF-8 Results ======= Failregex: 14 total |- #) [# of hits] regular expression | 1) [14] http/1.1 Response 401 to ‌<HOST> `- Ignoreregex: 0 total Date template hits: |- [# of hits] date format | [339] {^LN-BEG}ExYear(?P<_sep>[-/.])Month(?P=_sep)Day(?:T| ?)24hour:Minute:Second(?:[.,]Microseconds)?(?:\s*Zone offset)? `- Lines: 474 lines, 0 ignored, 14 matched, 460 missed [processed in 0.23 sec] Other troubleshooting things sudo systemctl status fail2ban ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset: enabled) Active: active (running) since Sat 2024-08-24 21:14:29 EDT; 16min ago Docs: man:fail2ban(1) Main PID: 51845 (fail2ban-server) Tasks: 7 (limit: 18710) Memory: 20.0M (peak: 21.5M) CPU: 5.311s CGroup: /system.slice/fail2ban.service └─51845 /usr/bin/python3 /usr/bin/fail2ban-server -xf start Sudo fail2ban-client status Status |- Number of jail: 2 `- Jail list: emby, sshd sudo tail -f /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt 2024-08-25 01:30:00.040 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:30:00.040 Error Server: Access token is invalid or expired. 2024-08-25 01:30:00.040 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 3ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:35:00.122 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:35:00.122 Error Server: Access token is invalid or expired. 2024-08-25 01:35:00.122 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 2ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:36:59.424 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2024-08-25 01:40:00.076 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:40:00.076 Error Server: Access token is invalid or expired. 2024-08-25 01:40:00.076 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 3ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:43:48.212 Info Server: http/1.1 POST http://‌media.eternaltek.xyz‌/emby/Users/authenticatebyname?X-Emby-Client=Emby Web&X-Emby-Device-Name=Safari iOS&X-Emby-Device-Id=cdf1ca5b-4fe1-453d-a08b-22539010875d&X-Emby-Client-Version=4.9.0.29&X-Emby-Language=en-us. Source Ip: ‌172.58.127.8‌, Accept=application/json, Connection=close, Host=‌media.eternaltek.xyz‌, User-Agent=Mozilla/5.0 (iPhone; CPU iPhone OS 18_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1, Accept-Encoding=gzip, deflate, br, Accept-Language=en-US,en;q=0.9, Content-Type=application/x-www-form-urlencoded; charset=UTF-8, Origin=‌https://media.eternaltek.xyz:23606‌, Referer=‌https://media.eternaltek.xyz:23606/web/index.html‌, Content-Length=12, X-TLS-Cipher=TLS_AES_128_GCM_SHA256, X-TLS-Protocol=TLSv1.3, X-TLS-SNI-Host=media.eternaltek.xyz, X-Real-IP=‌172.58.127.8‌, X-Forwarded-For=‌172.58.127.8‌, X-Forwarded-Proto=https, X-Forwarded-Port=23606, X-Forwarded-Host=‌media.eternaltek.xyz‌, X-TLS-Client-Intercepted=Unknown, sec-fetch-site=same-origin, sec-fetch-mode=cors, sec-fetch-dest=empty, priority=u=3, i 2024-08-25 01:43:48.212 Error DefaultAuthenticationProvider: Invalid username or password. No user named Dfv exists 2024-08-25 01:43:48.213 Error UserManager: Error authenticating with provider Default *** Error Report *** Version: 4.9.0.29 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.8.0-41-generic (buildd@lcy02-amd64-100) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2. OS/Process: x64/x64 Framework: .NET 8.0.6 Runtime: system/System.Private.CoreLib.dll Processor count: 10 Data path: /config Application path: /system System.Exception: System.Exception: Invalid username or password. at Emby.Server.Implementations.Library.DefaultAuthenticationProvider.Authenticate(String username, String password, User resolvedUser) at Emby.Server.Implementations.Library.UserManager.AuthenticateWithProvider(IAuthenticationProvider provider, String username, String password, User resolvedUser, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: System.Threading.Tasks.Task`1[MediaBrowser.Controller.Authentication.ProviderAuthenticationResult] Authenticate(System.String, System.String, MediaBrowser.Controller.Entities.User) 2024-08-25 01:43:48.213 Info UserManager: Authentication request for Dfv has been denied. 2024-08-25 01:43:48.214 Warn Server: AUTH-ERROR: 172.58.127.8 - Invalid username or password entered. 2024-08-25 01:43:48.214 Error Server: Invalid username or password entered. 2024-08-25 01:43:48.214 Info Server: http/1.1 Response 401 to ‌172.58.127.8‌. Time: 3ms. POST http://‌media.eternaltek.xyz‌/emby/Users/authenticatebyname?X-Emby-Client=Emby Web&X-Emby-Device-Name=Safari iOS&X-Emby-Device-Id=cdf1ca5b-4fe1-453d-a08b-22539010875d&X-Emby-Client-Version=4.9.0.29&X-Emby-Language=en-us

Hey, I'm back again, was trying out Emby in August and ran out of time. I am now been running Emby since October 6 and having good success with on disk TV shows, Movies, and Live TV via m3u and XMLTvlisting and will buy a lifetime pass shortly, but am having trouble introducing a HDHomeRun - figured that was easier than using TVHeadend and my USB tuners. Environ: Raspberry 4B/8. Debian 64 bit. All up to date, Docker/docker-compose. I tried adding a working HDHomerun with a reserved IP to Emby. The auto-detect didn't work, but I wasn't surprised as Emby is not on the lan subnet, but behind docker and gluetun. But when I tried providing the IP address it just errored on trying to add. I figure it is the gluetun network stack. Gluetun knows what is local to the LAN and what should go out the VPN, but needs to be told of ports being used by dependant containers. I listed 8096 and 8920 for Emby, and that works fine.. Occasionally a Firestick Emby app gets confused and can't see the server after a Firestick restart, but a retry fixes that. I think I read that Emby is using udp to communicate with HDHomeRuns. I believe I would need to list the UDP port numbers in gluetun's configuration and rely on gluetun to deliver incoming dup back to the Emby container. I tried adding ports: - 65001:65001/udp to gluetun, but still no joy. Who can help a guy out? Docker Compose environ. Running Emby using gluetun's network providing me with a VPN tunnel through Nord. docker-compose.yml version: '2.0' services: // other containers snipped // qbittorrent, radarr, sonarr, jackett, apcupsd gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=nordvpn - VPN_TYPE=openvpn # or wireguard - OPENVPN_USER=<<secret>> - OPENVPN_PASSWORD=<<secret>> - SERVER_COUNTRIES=Canada ports: - 8096:8096 - 8920:8920 emby: #image: emby/embyserver:beta image: emby/embyserver_arm64v8 container_name: emby #network_mode: host network_mode: "service:gluetun" environment: - PUID=1000 - PGID=1000 - TZ=America/Toronto volumes: - /mnt/emby:/config - /mnt/television:/data/tvshows - /mnt/movies:/data/movies # - /opt/vc/lib:/opt/vc/lib #ports: # - 8096:8096 # - 8920:8920 restart: unless-stopped

hi! I have 4.8.3.0 installed using docker on Ubuntu Server 22.04.4 LTS. How do I troubleshoot an install that was previously working and decided to stop working? What I’ve confirmed is if I rename the root emby folder and force the server to recreate all its directories, the web interface comes up. If I put the old emby root directory back in place, the web server never starts. Here is the log file: 2024-04-20 00:19:59.630 Info Main: Application path: /system/EmbyServer.dll 2024-04-20 00:20:00.009 Info App: Setting default culture to en-US 2024-04-20 00:20:00.014 Info Main: Emby Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 2 Data path: /config Application path: /system 2024-04-20 00:20:00.014 Info Main: Logs path: /config/logs 2024-04-20 00:20:00.014 Info Main: Cache path: /config/cache 2024-04-20 00:20:00.014 Info Main: Internal metadata path: /config/metadata 2024-04-20 00:20:00.017 Info App: Emby Server Version: 4.8.3.0 2024-04-20 00:20:00.021 Info App: Loading assemblies 2024-04-20 00:20:00.072 Info App: File /config/plugins/Fanart.dll has version 1.0.16.0 2024-04-20 00:20:00.073 Info App: File /system/plugins/Fanart.dll has version 1.0.16.0 2024-04-20 00:20:00.073 Info App: File /config/plugins/MovieDb.dll has version 1.7.5.0 2024-04-20 00:20:00.073 Info App: File /system/plugins/MovieDb.dll has version 1.7.4.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/OMDb.dll has version 1.0.21.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/OMDb.dll has version 1.0.21.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/Emby.PortMapper.dll has version 1.2.4.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/Emby.PortMapper.dll has version 1.2.4.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/EmbyGuideData.dll has version 1.0.13.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/EmbyGuideData.dll has version 1.0.13.0 2024-04-20 00:20:00.075 Info App: File /config/plugins/StudioImages.dll has version 1.0.3.0 2024-04-20 00:20:00.075 Info App: File /system/plugins/StudioImages.dll has version 1.0.3.0 2024-04-20 00:20:00.075 Info App: File /config/plugins/MBBackup.dll has version 1.6.4.0 2024-04-20 00:20:00.075 Info App: File /system/plugins/MBBackup.dll has version 1.6.3.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/OpenSubtitles.dll has version 1.0.54.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/OpenSubtitles.dll has version 1.0.53.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/NfoMetadata.dll has version 1.0.80.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/NfoMetadata.dll has version 1.0.80.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/Tvdb.dll has version 1.4.9.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/Tvdb.dll has version 1.4.5.0 2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Dlna.dll has version 1.3.8.0 2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Dlna.dll has version 1.3.7.0 2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Webhooks.dll has version 1.0.35.0 2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Webhooks.dll has version 1.0.35.0 2024-04-20 00:20:00.091 Info App: Loading Fanart, Version=1.0.16.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Fanart.dll 2024-04-20 00:20:00.091 Info App: Loading MovieDb, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MovieDb.dll 2024-04-20 00:20:00.091 Info App: Loading OMDb, Version=1.0.21.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OMDb.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.PortMapper, Version=1.2.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.PortMapper.dll 2024-04-20 00:20:00.092 Info App: Loading statistics, Version=3.2.0.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Statistics.dll 2024-04-20 00:20:00.092 Info App: Loading EmbyGuideData, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /config/plugins/EmbyGuideData.dll 2024-04-20 00:20:00.092 Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /config/plugins/StudioImages.dll 2024-04-20 00:20:00.092 Info App: Loading MBBackup, Version=1.6.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MBBackup.dll 2024-04-20 00:20:00.092 Info App: Loading OpenSubtitles, Version=1.0.54.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OpenSubtitles.dll 2024-04-20 00:20:00.092 Info App: Loading NfoMetadata, Version=1.0.80.0, Culture=neutral, PublicKeyToken=null from /config/plugins/NfoMetadata.dll 2024-04-20 00:20:00.092 Info App: Loading Tvdb, Version=1.4.9.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Tvdb.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Dlna, Version=1.3.8.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Dlna.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Webhooks, Version=1.0.35.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Webhooks.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Api, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Web, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Model, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Common, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Controller, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Providers, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Photos, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Implementations, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.LiveTV, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.ActivityLog, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.MediaEncoding, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.LocalMetadata, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Notifications, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Web.GenericUI, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs.Dxva, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Connect, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Sync, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading EmbyServer, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.400 Info SqliteUserRepository: Sqlite version: 3.42.0 2024-04-20 00:20:00.402 Info SqliteUserRepository: Sqlite compiler options: ATOMIC_INTRINSICS=1,COMPILER=gcc-10.3.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_MATH_FUNCTIONS,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=127,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=1073741823,MAX_PAGE_SIZE=65536,MAX_SCHEMA_RETRY=25,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,OMIT_LOOKASIDE,SECURE_DELETE,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1 2024-04-20 00:20:00.402 Info SqliteUserRepository: Opening sqlite connection to /config/data/users.db 2024-04-20 00:20:00.417 Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal 2024-04-20 00:20:00.420 Info SqliteUserRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.508 Info ActivityRepository: Opening sqlite connection to /config/data/activitylog.db 2024-04-20 00:20:00.511 Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal 2024-04-20 00:20:00.511 Info ActivityRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.533 Info NetworkManager: Detecting local network addresses 2024-04-20 00:20:00.534 Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0 2024-04-20 00:20:00.534 Info NetworkManager: GatewayAddresses: 172.24.0.1 2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 172.24.0.2 2024-04-20 00:20:00.535 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo 2024-04-20 00:20:00.535 Info NetworkManager: GatewayAddresses: 2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 127.0.0.1 2024-04-20 00:20:00.602 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.24.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"}] 2024-04-20 00:20:00.606 Info SqliteDisplayPreferencesRepository: Opening sqlite connection to /config/data/displaypreferences.db 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.618 Info App: Adding HttpListener prefix http://+:8097/ 2024-04-20 00:20:00.671 Info AuthenticationRepository: Opening sqlite connection to /config/data/authentication.db 2024-04-20 00:20:00.673 Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal 2024-04-20 00:20:00.674 Info AuthenticationRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.690 Info SqliteItemRepository: Opening sqlite connection to /config/data/library.db 2024-04-20 00:20:00.698 Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA cache_size=-98304 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA page_size=4096 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.771 Info SqliteItemRepository: Init Complete 2024-04-20 00:20:01.109 Info App: Emby Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 2 Data path: /config Application path: /system 2024-04-20 00:20:01.110 Info App: Logs path: /config/logs 2024-04-20 00:20:01.110 Info App: Cache path: /config/cache 2024-04-20 00:20:01.110 Info App: Internal metadata path: /config/metadata 2024-04-20 00:20:01.110 Info App: Transcoding temporary files path: /config/transcoding-temp 2024-04-20 00:20:02.422 Info FfmpegManager: FFMpeg: /bin/ffmpeg 2024-04-20 00:20:02.422 Info FfmpegManager: FFProbe: /bin/ffprobe 2024-04-20 00:20:02.422 Info FfmpegManager: FFDetect: /bin/ffdetect 2024-04-20 00:20:02.431 Info Skia: SkiaSharp version: 2.88.0.0 2024-04-20 00:20:02.433 Info ImageProcessor: Adding image processor Skia 2024-04-20 00:20:02.465 Info libvips: NetVips version: 2.3.1.0 2024-04-20 00:20:02.465 Info ImageProcessor: Adding image processor libvips 2024-04-20 00:20:02.533 Info TaskManager: Daily trigger for Emby Server Backup set to fire at 04/21/2024 00:10:00, which is 1429.9577930983332 minutes from now. 2024-04-20 00:20:02.535 Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 04/20/2024 02:00:00, which is 99.95774068666667 minutes from now. 2024-04-20 00:20:02.882 Info TaskManager: Daily trigger for Rotate log file set to fire at 04/21/2024 00:00:00, which is 1419.951958945 minutes from now. 2024-04-20 00:20:02.908 Info TaskManager: Queueing task HardwareDetectionScheduledTask 2024-04-20 00:20:02.912 Info TaskManager: Executing Hardware Detection 2024-04-20 00:20:02.923 Info App: ServerId: 90c28209f84a4d6eb5b35a58d8d192c7 2024-04-20 00:20:02.961 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Execute: /bin/ffmpeg -hide_banner -version 2024-04-20 00:20:02.992 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint 2024-04-20 00:20:03.000 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.032 Info FfmpegManager: FfmpegValidator.Validate complete 2024-04-20 00:20:03.219 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.226789 seconds 2024-04-20 00:20:03.223 Info App: Starting entry point Emby.Server.Implementations.Networking.RemoteAddressEntryPoint 2024-04-20 00:20:03.228 Info App: Loading data from /config/data/wan.dat 2024-04-20 00:20:03.233 Info App: Entry point completed: Emby.Server.Implementations.Networking.RemoteAddressEntryPoint. Duration: 0.0098643 seconds 2024-04-20 00:20:03.234 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint 2024-04-20 00:20:03.237 Info App: Loading data from /config/data/connect.txt 2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0 2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0 2024-04-20 00:20:03.239 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.005443 seconds 2024-04-20 00:20:03.240 Info App: Core startup complete 2024-04-20 00:20:03.250 Info App: Starting entry point MovieDb.Security.PluginStartup 2024-04-20 00:20:03.251 Info App: Entry point completed: MovieDb.Security.PluginStartup. Duration: 0.0009738 seconds 2024-04-20 00:20:03.251 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding 2024-04-20 00:20:03.252 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0008323 seconds 2024-04-20 00:20:03.252 Info App: Starting entry point MBBackup.ServerEntryPoint 2024-04-20 00:20:03.252 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 6.32E-05 seconds 2024-04-20 00:20:03.252 Info App: Starting entry point NfoMetadata.EntryPoint 2024-04-20 00:20:03.253 Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0006206 seconds 2024-04-20 00:20:03.253 Info App: Starting entry point Tvdb.EntryPoint 2024-04-20 00:20:03.253 Info App: Entry point completed: Tvdb.EntryPoint. Duration: 6.14E-05 seconds 2024-04-20 00:20:03.253 Info App: Starting entry point Emby.Webhooks.MigrationEntryPoint 2024-04-20 00:20:03.263 Info App: Entry point completed: Emby.Webhooks.MigrationEntryPoint. Duration: 0.002926 seconds 2024-04-20 00:20:03.263 Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint 2024-04-20 00:20:03.265 Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0016933 seconds 2024-04-20 00:20:03.265 Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint 2024-04-20 00:20:03.269 Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint. Duration: 0.0031783 seconds 2024-04-20 00:20:03.269 Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint 2024-04-20 00:20:03.270 Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0006636 seconds 2024-04-20 00:20:03.270 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup 2024-04-20 00:20:03.283 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264 2024-04-20 00:20:03.284 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx 2024-04-20 00:20:03.291 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx 2024-04-20 00:20:03.295 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0248056 seconds 2024-04-20 00:20:03.295 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint 2024-04-20 00:20:03.296 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0007693 seconds 2024-04-20 00:20:03.296 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake 2024-04-20 00:20:03.297 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0002309 seconds 2024-04-20 00:20:03.297 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier 2024-04-20 00:20:03.299 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0018423 seconds 2024-04-20 00:20:03.299 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier 2024-04-20 00:20:03.311 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0117179 seconds 2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard 2024-04-20 00:20:03.312 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0004591 seconds 2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents 2024-04-20 00:20:03.313 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0006732 seconds 2024-04-20 00:20:03.313 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier 2024-04-20 00:20:03.314 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0002695 seconds 2024-04-20 00:20:03.314 Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint 2024-04-20 00:20:03.317 Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0032508 seconds 2024-04-20 00:20:03.318 Info App: Starting entry point Emby.LiveTV.EntryPoint 2024-04-20 00:20:03.322 Info LibraryMonitor: Watching directory with new FileSystemWatcher for /userdata/kodi.ddb/movies for item 4514 2024-04-20 00:20:03.325 Info LiveTV: Loading live tv data from /config/data/livetv/timers 2024-04-20 00:20:03.328 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json 2024-04-20 00:20:03.348 Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0297033 seconds 2024-04-20 00:20:03.348 Info App: Starting entry point Emby.LiveTV.RecordingNotifier 2024-04-20 00:20:03.352 Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0033374 seconds 2024-04-20 00:20:03.352 Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint 2024-04-20 00:20:03.357 Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0049484 seconds 2024-04-20 00:20:03.357 Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint 2024-04-20 00:20:03.359 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0015033 seconds 2024-04-20 00:20:03.359 Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint 2024-04-20 00:20:03.363 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.376 Info Notifications: Registering event nofitier Emby Server User Notifications 2024-04-20 00:20:03.382 Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0227096 seconds 2024-04-20 00:20:03.382 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint 2024-04-20 00:20:03.385 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0026962 seconds 2024-04-20 00:20:03.385 Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint 2024-04-20 00:20:03.385 Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0002086 seconds 2024-04-20 00:20:03.385 Info App: All entry points have started 2024-04-20 00:20:03.468 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 qsvencdec -print_format json 2024-04-20 00:20:03.490 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.560 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 nvencdec -print_format json 2024-04-20 00:20:03.566 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Process exited with code 1 - Failed 2024-04-20 00:20:03.917 Info CodecManager: CodecList: 2024-04-20 00:20:03.918 Info TaskManager: Hardware Detection Completed after 0 minute(s) and 1 seconds 2024-04-20 00:20:05.878 Info TaskManager: Queueing task PluginUpdateTask 2024-04-20 00:20:05.878 Info TaskManager: Executing Check for plugin updates 2024-04-20 00:20:05.881 Info TaskManager: Queueing task SystemUpdateTask 2024-04-20 00:20:05.882 Info TaskManager: Executing Check for application updates 2024-04-20 00:20:05.912 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2024-04-20 00:20:05.914 Info TaskManager: Queueing task SubtitleOcrDataTask 2024-04-20 00:20:05.914 Info TaskManager: Executing Download OCR Data 2024-04-20 00:20:05.946 Info TaskManager: Download OCR Data Completed after 0 minute(s) and 0 seconds 2024-04-20 00:20:06.157 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 seconds 2024-04-20 00:20:06.728 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 0 seconds and that’s it - it just halts after 6-7 seconds. Is there a way we can get the log file to be more verbose to see where it’s halting? Reminder: I can’t get into the web interface so we need to do this all on the command line. And another reminder: it doesn’t halt if I recreate the Emby root directories so it has something to do with my old library/config files (which currently is 100% stock, no extra plug-ins)

Hi guys, I am having trouble with the hardware acceleration in docker. I'm using the integrated graphics card of the Intel N100 and the system is Ubuntu server 22.04 LTS. My emby is 4.7.14.0 With the commands: getent group video | cut -d: -f3, I got 44 getent group render | cut -d: -f3, I got 109 So Here is my docker compose: emby: image: emby/embyserver:latest container_name: emby environment: - UID=1000 - GID=100 - GIDLIST=44,109 - TZ=Asia/Shanghai volumes: - /root/emby/config:/config - /root/emby/cache:/cache - /root/media:/media devices: - /dev/dri:/dev/dri ports: - 8096:8096 restart: unless-stopped After emby started, I found several errors in hardware_detection: Devices": [ { "DeviceIndex": 0, "DeviceInfo": { "VendorName": "Intel Corporation", "DeviceName": "Alder Lake-N [UHD Graphics]", "SubsytemVendorName": "Intel Corporation", "VendorId": 32902, "DeviceId": 18129, "SubsytemVendorId": 32902, "SubsytemDeviceId": 29296, "DevPath": "/sys/bus/pci/devices/0000:00:02.0", "DrmCard": "/dev/dri/card0", "DrmRender": "/dev/dri/renderD128", "IsEnabled": 1, "IsBootVga": 1, "Error": { "Number": -1, "Message": "Failed to initialize VA /dev/dri/renderD128. Error -1" } } } ], I also tried: ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -vf 'format=nv12|vaapi,hwupload' -c:v h264_vaapi output_VAAPI.mp4 It works in Ubuntu but not in Docker: Could you give me any advice? hardware_detection-63837216517.txt

Hi all I recently installed the Emby docker image on my synology DS918+ with 8 Gb ram. docker emby version: 4.7.14.0 All is working well, only if you open the plugins catalogue it keeps loading. In the logs i get the following error; 2023-11-27 10:54:08.548 Error HttpClient: Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out 2023-11-27 10:54:08.563 Error Server: Error processing request *** Error Report *** Version: 4.7.14.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 4.4.180+ (root@build3) (gcc version 8.5.0 (GCC) ) #42962 SMP Mon May 29 14:38:23 CST 2023 Framework: .NET 6.0.20 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 4 Data path: /config Application path: /system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. ---> System.TimeoutException: A task was canceled. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. I googled some, most (if not all) of the solutions mention the firewall, but I can ping https://www.mb3admin.com/admin/service/EmbyPackages.json from inside the docker container, so I think there are no issues here. If you don't have enough info, please let me know. Thanks in advance! emby_log.txt

Maybe someone can tell me why this is happening... My Unraid server crashed today. I'm running Emby in Docker. When I tracked the problem down, it was because I ran out of space on my 1TB cache drive. A little more digging led me to the transcoding-temp directory of Emby which is stored on the cache drive. There were almost 800K files totalling over 500GB of space. The files go back to May of 2019. A large file transfer caused the drive to fill up the rest of the way, and then crash the system. Shouldn't these files be cleaned up by Emby? Is there something in my Unraid/Docker config that could be causing the issue?

I want to know if it is possible to configure quicksync instead of vaapi with your official docker ?

Hi, Recently I bought a premium Emby subscription on decided to try hardware transcoding, after setting it up I give it a go but sadly some files doesn't start playing at all and the ones who do start only plays for about 10 seconds afterwards they stop. I tried to lower the quality and that way they play normally, but I would like to avoid that and always use the highest quality possible. I never had this issue before, without HW transcoding. I have Emby running on a docker container using the official image, the latest version. I can provide more information about the Docker setup if needed.p The server where Docker is running has a i7-10710U Processor, 16 gb of ram and a 500 gb SSD. Here's the server and ffmpeg log. Please let me know what other information I can provide! Thanks! embyserver.txt ffmpeg-transcode-62d0979d-8c11-43f4-bb36-4ed28f11f286_1.txt

Hi there, im hoping someone could provide some guidance for me on my new Emby Premium docker build. It's working, however I have this issue that needs resolving. Im pretty new to the docker and linux world for that matter. The issue is; Cant delete movies and shows from the Emby UI. Error: "There was an error deleting the item from Emby Server. Please check that Emby Server has write access to the media folder and try again." Docker Compose running on Ubuntu 22.04.1 host. I've read and understood as much as I can of these articles. If I could, I would grant read/write/execute to 'emby', but that user doesnt exist on the Ubuntu host. The permissions that I do have assigned allows Emby to play the media because the server is working great for playing movies and shows. drwxrwxrwx+ 4 dan dan 4096 Nov 27 16:47 content (root folder in my user folder where my media is) drwxrwxrwx+ 25 root root 4096 Dec 2 06:13 downloads (subfolder of content) drwxrwxrwx+ 4 root root 4096 Nov 27 16:47 media (subfolder of content) I just updated the owner of the downloads and media folders to be dan dan, rebooted and that didnt help drwxrwxrwx+ 25 dan dan 4096 Dec 2 06:13 downloads (subfolder of content) drwxrwxrwx+ 4 dan dan 4096 Nov 27 16:47 media (subfolder of content) Emby server log attached, as well as my compose yml. Thank you for any help. embyserver.txt docker-compose.yml

Hi, This is somewhat hard to tackle and to get 100% certainty, but I have a feeling EMBY hangs a complete linux node running on Docker. Setup: - Intel NUC, 16GB, 512GB SSD, CPU i5 - OS latest Alpine Linux distribution - Emby (latest production version) running in Docker (tried official image, tried Linuxserver.io image) - Running in a headless setup Problem: Runnng Emby in the setup (see above), keeps hanging the Intel NUC so that the NUC in complete unresponsive. No SSH, no Network responses. The server doesn't crash when: 1. Emby container is stopped (tested this for days) 2. Emby container is running but NO ONE connects (tested this for days) The server does crash when: People are watching video and after a while the server just stops responding. (within the same evening) I did memory tests, CPU tests on the NUC, but the hardware seems fine. Question: Can you help and point out ways to investigate this some more??

I've been running Emby with GPU transcoding for multiple years now but if i try to update past version 4.7.6.0 (Linuxserver docker) the container won't even finish the configuration but i can't come here and ask for help with someone elses container so i've been trying to resolve my issues with the official Emby/Embyserver container and i'm hoping for some help The container start fine but nvidia-smi is not found in the shell and the logs are showing: ffdetect_nvencdec Process exited with code 1 nCannot load libcuda.so.1\nError loading CUDA functions\n\n","Result":{ Configuration": "--cc=x86_64-emby-linux-gnu-gcc ...... }, "Error": { "Number": -1, "Message": "Operation not permitted" }, "Log": [ { "Level": 16, "Category": 0, "Message": "Cannot load libcuda.so.1" }, { "Level": 16, "Category": 0, "Message": "Error loading CUDA functions" And clicking advanced under hardware acceleration gives no options Host is Arch Linux 6.1.3-arch1-1, I've been trying to see if this works every few months so it has been tried with older kernels through those months. Emby premiere is enabled Gpu is a quadro p620p NVIDIA-SMI 525.78.01 Driver Version: 525.78.01 CUDA Version: 12.0 docker 1:20.10.22-1 (latest) libnvidia-container 1.5.1-1 libnvidia-container-tools 1.5.1-1 nvidia-container-runtime 3.5.0-2 nvidia-container-toolkit 1.5.1-1 I've previously used the official Emby container without issues but i have never before tried it with hardware encoding For the purpose of finding the issue i've been testing on a fresh install of the official Emby/Embyserver container from hub.docker with premium enabled I've tried other media servers to see if hardware encoding works there and it does I've tried to go backwards with the official Emby docker container but can't seem to find an older version that work with hardware acceleration I've tried to roll back my drivers to an older version with no luck nvidia-smi is not found when run from the containers shell I've seen an issue or two here that resemble mine but they either don't come to a conclusion, Have a different cuda errror or and have not attempted running other containers that requre GPU acceleration, Which works flawlessly for me docker-compose: embytest: image: emby/embyserver:latest hostname: embytest.docker container_name: embytest restart: always networks: - frontend # ports: # - 9096:9096 # - 9920:9920 mem_limit: 4g runtime: nvidia devices: - /dev/dri:/dev/dri deploy: resources: reservations: devices: - capabilities: [gpu] environment: - UID=${PUID} - GID=${PGID} - GIDLIST=985,989 - NVIDIA_VISIBLE_DEVICES=all volumes: - ${DOCKER_HOME}/embytest:/config - media:/mnt/media dns: - 1.1.1.1 - 1.0.0.1 How i configured my host to enable the nvidia-container-runtime Blacklisted nouveau added the kernel parameter (systemd.unified_cgroup_hierarchy=false) edited /etc/nvidia-container-runtime/config.toml (no-cgroups = false) rebuild the boot image added: /etc/docker/daemon.json with: rebooted { "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [] } } } installed the latest good nvidia driver that works with the nvidia patch patched nvidia rebooted gpu acceleration with the linuxserver docker would not work without this added to docker-compose: deploy: resources: reservations: devices: - capabilities: [gpu] hardware_detection-63808684426.txt embyserver(2).txt

I m currently running Emby version 4.6.4.0 inside Docker on Synology version 7.0.41890. I would like to eliminate the Docker component, and run the native Emby app that is found in the Synology package. For movies and TV shows, the metadata is in the save folders. For music and books, it is in the Mysql database. My libraries are huge. Does anyone have experience with this type of migration and if so what can I expect?

Hi. I am currently trying to get wake on lan working with the theater apps as my server is not running all the time anymore. My current server side setup is a docker host (Ubuntu 20.04) with the official docker container (emby server version 4.7.10.0) which is running in bridge mode and is connected to two internal networks (one for the reverse proxy and another one currently for the connection with ombi). I would prefer to keep it that way to have it all separated. Capturing the traffic between the server and app with wireshark it looks like the app sends two WOL packets to the MACs of the two network interfaces of the container which is obviously not correct with my setup. It would be great if there could be an input field in the server settings to override the automatically detected MAC addresses.

Host OS: Ubuntu Server 22.10 Docker version: Linuxserver/emby 4.7.9.0 I use traefik to expose ports 80/443 and retrieve ssl certs so all docker containers are reachable via emby.mydomain.net. Works as designed, but I cant for the life of me figure out who to get users connected remotely/via emby connect....can someone point me in the right direction? also, I need a port open on my firewall, right? emby: image: lscr.io/linuxserver/emby:latest container_name: emby ports: - 8096:8096 - 8920:8920 networks: traefik_web: ipv4_address: 172.18.0.27 restart: unless-stopped environment: - PUID=$PUID - PGID=$PGID - NVIDIA_VISIBLE_DEVICES=all runtime: nvidia volumes: - /metadata/embyconfig:/config - /metadata/embytranscode:/transcode - /data/media/movies:/data/movies - /data/media/tvshows:/data/tvshows - /data/media/4kmovies:/data/4kmovies labels: - "traefik.enable=true" ## HTTP Routers - "traefik.http.routers.kenemby-rtr.entrypoints=https" - "traefik.http.routers.kenemby-rtr.rule=Host(`kenemby.$DOMAINNAME`)" ## Middlewares - "traefik.http.routers.kenemby-rtr.middlewares=chain-authelia@file" ## HTTP Services - "traefik.http.routers.kenemby-rtr.service=kenemby-svc" - "traefik.http.services.kenemby-svc.loadbalancer.server.port=8096"

Emby Server 4.7.8.0 running in Docker on Unraid 6.11.1 via official Embyserver Docker image. Not sure why 4.7.8.0 is returned for :latest as there are newer version tagged (4.8.0.12 for example) but hopefully that's not important for this issue. Issue is ffmpeg is segfaulting immediately when transcoding TrueHD 7.1 audio . Log line from syslog: Oct 16 22:23:41 GServer kernel: ffmpeg[32298]: segfault at fffffffffffff100 ip 0000147f2aedf5b8 sp 0000147f27e04610 error 5 in libavcodec.so.59.21.100[147f2ab17000+18c6000] Oct 16 22:23:41 GServer kernel: Code: 55 1a 48 89 08 48 83 c0 08 48 39 c2 75 f4 e9 17 f8 ff ff 0f 1f 80 00 00 00 00 48 8b 44 24 58 48 8b b4 24 48 83 e0 fe 48 29 c6 <f3> 0f 6f 0e 0f 11 8c 24 92 01 00 00 e9 e6 f7 ff ff 0f 1f 80 00 00 Interestingly, this only occurs if the video stream is 4k HEVC HDR10 (playing direct stream so not transcoded). Segfault doesn't happen with standard 4k HEVC HDR video files and TrueHD7.1 audio. I don't have any other types of HDR to test. Containers are mkv. Here's the (hopefully) relevant part from the main log in the dashboard. I'm refraining from posting the entire log as it's absolutely spammed full of thousands of repeats of these lines: 2022-10-16 22:38:28.602 Info Server: http/1.1 Response 404 to host1. Time: 1ms. http://192.168.1.100:8096/emby/videos/153573/hls1/main/1548.ts?PlaySessionId=11c4e0d69eef430ab689d43a22c86c17 2022-10-16 22:38:28.610 Info Server: http/1.1 GET http://192.168.1.100:8096/emby/videos/153573/hls1/main/1549.ts?PlaySessionId=11c4e0d69eef430ab689d43a22c86c17. Accept=*/*, Connection=keep-alive, Host=192.168.1.100:8096, User-Agent=libmpv, Icy-MetaData=1 2022-10-16 22:38:28.610 Error Server: Error processing request *** Error Report *** Version: 4.7.8.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.19.14-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.39-slack151) #1 SMP PREEMPT_DYNAMIC Thu Oct 6 09:15:00 PDT 2022 Framework: .NET 6.0.8 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 16 Data path: /config Application path: /system System.IO.FileNotFoundException: System.IO.FileNotFoundException: Unable to find the specified file. at Emby.Server.MediaEncoding.Api.Hls.BaseHlsService.CreateRequestFromPlaySessionId(BaseSegmentRequest segmentRequest) at Emby.Server.MediaEncoding.Api.Hls.DynamicHlsService.Get(GetHlsSegment segmentRequest) at Emby.Server.Implementations.Services.ServiceController.Execute(HttpListenerHost appHost, Object requestDto, IRequest req) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath restPath, String responseContentType, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken) Source: Emby.Server.MediaEncoding TargetSite: System.Tuple`3[Emby.Server.MediaEncoding.Api.StreamRequest,System.String,MediaBrowser.Controller.Net.AuthorizationInfo] CreateRequestFromPlaySessionId(Emby.Server.MediaEncoding.Api.Hls.BaseSegmentRequest) I can see it says System.IO.FileNotFoundException, the file is obviously there and I can play the file fine with no playback issues when I select another audio stream line AC3 5.1. I have attached the transcode log in case that contains anything helpful. Thanks. ffmpeg-transcode-2ac1a4cd-5c5f-4f88-b3ac-ee5274870e73_1.txt

Good Day, I tried searching around but I am having issues after moving my Emby server from my PC to the Synology DS920+. I have a few friends that I allow remote access to my server to stream my content and it worked amazingly when it was set up on my PC. 1080 and 4k worked great. However, after moving everything to from my PC to the Synology, remote play has been extremely slow and buffering all the time. For someone to get uninterrupted stream they have to decrease the playback to 720 at 3Mbps. I am unsure what the issue is and below is all the software and hardware information. (Server streams fine locally on my network, its causing problems with outside networks.) PC (Use to run great on) i9 9900K 3.6 Ghz 32GB 3200Mhz Ram 2070 RTX Nvida GPU External 10TB HDD shucked to internal for storage 7200RPM NAS Synology DS920+ 24GB Ram 2x Seagate IronWolf Pro 16TB NAS Internal Hard Drive HDD 7200RPM (32TB) Internet VerizonFios 1G Speeds with a constant 800mbps Emby v4.7.5.0 Router has a 10Gbps LAN connection in which is what the Synology is hooked up to, I added port forwarding to the Emby Ports on the router to ensure outside connections didn't get blocked. I used Docker to install Emby on the Synology NAS device. As I type this, there are two people on my server trying to watch something and the CPU is sitting at 8% usage and the RAM is at 6%. I am unsure what other information is needed, but I am hopeful in working with the combined knowledge of the Emby form to lead me down the right path. Thank you very much in advance for your time.

+1 I am also having this issue - The amount of space it is using is out of control.

Hi guys, I'm afraid this has probably been asked before as I have tried to follow several of the posts on this forum. Namely: and I haven't setup a ssl cert yet but I am assuming this is not critical if I am testing things on port 80. My default.conf from /etc/nginx/conf.d/ is below. If I add anything above "server {" it stops working. I suspect it's something trivial like a missing } but I am at a loss to what. # Forward everything into Emby server { listen [::]:80; listen 80; server_name video.dyndns.org; proxy_hide_header X-Powered-By; add_header X-Xss-Protection "1; mode=block" always; add_header X-Content-Type-Options "nosniff" always; add_header Strict-Transport-Security "max-age=2592000; includeSubdomains" always; add_header X-Frame-Options "SAMEORIGIN" always; add_header 'Referrer-Policy' 'no-referrer'; add_header Content-Security-Policy "frame-ancestors dyndns.org video.dyndns.org;"; #add your domainname and all subdomains listed on your cert location / { proxy_pass http://192.168.1.83:8096; # Local emby ip and non SSL port proxy_hide_header X-Powered-By; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #Next three lines allow websockets proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } Any suggestions, as always, welcome

Hi guys, for reasons not worth explaining here I am currently without my dedicated server hardware. So I decided to install Docker to my Synology NAS and install the Emby image. My reasons for using the Docker Emby image and not the native Synology Emby app are various. DSM 6.2.4-25556 Update 2 Docker 20.10.3-0554 Emby latest (4.7.0.9) When I entered my premier key I got an error. After a bit of digging I found that if I turned off my Synology firewall then the key worked fine. Not ideal but to turn off the firewall for a few seconds while my premier key is validated and verified is not a deal breaker. What I found next is that when scanning my video library it doesn't download any metadata unless the firewall is off. I've tried a few different firewall rules but to no avail. Does anyone here have any ideas or the answer? Many thanks in advance! Container Log emby-1.html Container Settings emby.json embyserver.txt