Emby Crashing on fresh install of OMV

[Burlypenguin 0]

Hello,

I have started setting up a new OMV 5 server and I tried to install OMV through Portainer.

Here is the stack I used:

---
version: "2.1"
services:
  emby:
    image: linuxserver/emby
    container_name: emby
    environment:
      - PUID=998
      - PGID=100
      - TZ=America/Toronto
      - UMASK_SET=022 #optional
    volumes:
      - /srv/b58bf38d-6f77-4e02-b0ca-3c74f0762449/Config/Emby:/config
      - /srv/b58bf38d-6f77-4e02-b0ca-3c74f0762449/TV:/data/tvshows
      - /srv/b58bf38d-6f77-4e02-b0ca-3c74f0762449/Movies:/data/movies
      - /media/transcode:/transcode #optional
      #- /opt/vc/lib:/opt/vc/lib #optional
    ports:
      - 8096:8096

    restart: unless-stopped

The container shows that it is running but I am unable to connect to Emby. It looks like the server starts, crashes, then starts again. I have attached the entire log file but this is the start of it right up to the first error:

2020-07-19 14:18:50.694 Info Main: Application path: /app/emby/EmbyServer.dll
2020-07-19 14:18:50.940 Info Main: Emby
    Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe -restartexitcode 3
    Operating system: Unix 5.6.0.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///app/emby/System.Private.CoreLib.dll
    System.Environment.Version: 3.1.2
    Processor count: 12
    Program data path: /config
    Application directory: /app/emby
2020-07-19 14:18:50.982 Info App: Application version: 4.4.3.0
2020-07-19 14:18:50.984 Info App: Loading assemblies
2020-07-19 14:18:51.012 Error App: Error getting version number from /config/plugins/OMDb.dll
    *** Error Report ***
    Version: 4.4.3.0
    Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe -restartexitcode 3
    Operating system: Unix 5.6.0.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///app/emby/System.Private.CoreLib.dll
    System.Environment.Version: 3.1.2
    Processor count: 12
    Program data path: /config
    Application directory: /app/emby
    System.IO.IOException: System.IO.IOException: No such device

 

Some other info. If you need anything else please let me know.

The output of docker version:

Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:45:50 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:44:21 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

 

The output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 3
  Running: 2
  Paused: 0
  Stopped: 1
 Images: 3
 Server Version: 19.03.12
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.6.0-0.bpo.2-amd64
 Operating System: Debian GNU/Linux 10 (buster)
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 23.48GiB
 Name: Verbatium.ffa.lan
 ID: EKX5:E5W3:PAVS:U6T3:MNJ2:UWJX:T27B:DTK4:YQEW:SZ5G:PWV3:NNYO
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

 

embyserver-63730765131.txt

[Luke 42079]

Hi, that's strange. @BAlGaInTl have you seen this on omv before?

[Burlypenguin 0]

I managed to get it running by using this command:

docker run -d --volume /srv/Group/Config/Emby:/config --volume /srv/Data/Movies:/mnt/Movies --volume /srv/Data/TV:/mnt/TV --device /dev/dri/renderD128:/dev/dri --publish 8096:8096 --publish 8920:8920 --env UID=998 --env GID=100 --env GIDLIST=107 emby/embyserver:latest

Still can't get it working through Portainer. I really have no clue where to look for the problem.

[Luke 42079]

Thanks for the feedback.

[Burlypenguin 0]

I found the problem because of a typo. When I am using Portainer, my config is located at

/srv/b58bf38d-6f77-4e02-b0ca-3c74f0762449/Config/Emby

When I used docker it was

/srv/Group/Config/Emby

 

Now the portainer path is a unionfs that is using snapraid with a "most free space" policy. It looks like Emby doesn't like that. Did I miss that in a note somewhere?

[BAlGaInTl 288]

On 7/20/2020 at 1:50 AM, Luke said:

Hi, that's strange. @BAlGaInTl have you seen this on omv before?

Luke,

I never saw this, but I switched over to Unraid some time ago.

On 7/22/2020 at 10:56 PM, Burlypenguin said:

I found the problem because of a typo. When I am using Portainer, my config is located at

/srv/b58bf38d-6f77-4e02-b0ca-3c74f0762449/Config/Emby

When I used docker it was

/srv/Group/Config/Emby

 

Now the portainer path is a unionfs that is using snapraid with a "most free space" policy. It looks like Emby doesn't like that. Did I miss that in a note somewhere?

Glad that you got it figured out.