Jump to content

emby constantly restarting using docker


sluggo

Recommended Posts

Hello,

 

Sorry if this post does not contain enough info for troubleshooting, I'll do my best.

I'm using openmediavault 4.1.6 which is running on Debian 9.4. I've installed emby using the docker container emby/embyserver

 

Emby seems to work but I could hear my server harddrive constantly churning so I looked at the docker info on openmediavault and the status is always something "up 53 seconds" or "up 4 seconds'.  It never seems to be up for more than a minute.

 

I've attached a couple of log files from docker.  Below is a screenshot showing the environment variables I set in the docker plugin.

 

5b020f97c2091_embyvariables.png

 

Here is the output from the container details (from openmediavault):

[
    {
        "Id": "sha256:e465d2065cdac2c7f3eccd8fd50ab14d78b7cdf3b29f02f5ab99b0a504050524",
        "RepoTags": [
            "emby/embyserver:latest"
        ],
        "RepoDigests": [
            "emby/embyserver@sha256:2bf4b76927e541c4790f8cddf6b7511f10680a76491ccbad5292b8a3117c4fd7"
        ],
        "Parent": "",
        "Comment": "",
        "Created": "2018-05-07T15:58:46.706136952Z",
        "Container": "b75c48d1923bc68523bbb0872f1634922133f7e15769298ffeac248626e11bcc",
        "ContainerConfig": {
            "Hostname": "b75c48d1923b",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "1900/udp": {},
                "7359/udp": {},
                "8096/tcp": {},
                "8920/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "LANG=en_US.UTF-8",
                "FONTCONFIG_PATH=/etc/fonts",
                "ICU_DATA=/share/icu/59.1",
                "LD_LIBRARY_PATH=/lib:/lib/samba:/system",
                "LIBVA_DRIVERS_PATH=/lib/dri",
                "UID=2",
                "GID=2",
                "GIDLIST=2"
            ],
            "Cmd": [
                "/bin/sh",
                "-c",
                "#(nop) ",
                "ENTRYPOINT [\"/init\"]"
            ],
            "ArgsEscaped": true,
            "Image": "sha256:5714ca1003aebeea8c63550dc5e30f21f281bebc50fa500baf7c9e1ba179138a",
            "Volumes": {
                "/config": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "/init"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Emby LLC <apps@[member="Emby.media"]>"
            }
        },
        "DockerVersion": "18.04.0-ce",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "1900/udp": {},
                "7359/udp": {},
                "8096/tcp": {},
                "8920/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "LANG=en_US.UTF-8",
                "FONTCONFIG_PATH=/etc/fonts",
                "ICU_DATA=/share/icu/59.1",
                "LD_LIBRARY_PATH=/lib:/lib/samba:/system",
                "LIBVA_DRIVERS_PATH=/lib/dri",
                "UID=2",
                "GID=2",
                "GIDLIST=2"
            ],
            "Cmd": null,
            "ArgsEscaped": true,
            "Image": "sha256:5714ca1003aebeea8c63550dc5e30f21f281bebc50fa500baf7c9e1ba179138a",
            "Volumes": {
                "/config": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "/init"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Emby LLC <apps@[member="Emby.media"]>"
            }
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 208380077,
        "VirtualSize": 208380077,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/20e16cd2d0b7c53da651e0cb896ccd019038f5573cc50b47bfe5b9f248555e8e/diff:/var/lib/docker/overlay2/52002252664d969ed2eb4151d0de4b83c125d5163457b2aaea39ae904fbe2c6e/diff:/var/lib/docker/overlay2/63d17f041a5c28b8240ccbcd57a7ad6f97cbcfd3e8f2315e66f742c436185470/diff:/var/lib/docker/overlay2/317120fd9fe99aaf796ab63158f7b5a8b427b5dc5b72cf3d41d78fa4f4654f0d/diff",
                "MergedDir": "/var/lib/docker/overlay2/5f5a358dc6e6aa6ebf50e0bd225f16e1883b467da90976d61ed4849adf8e45f0/merged",
                "UpperDir": "/var/lib/docker/overlay2/5f5a358dc6e6aa6ebf50e0bd225f16e1883b467da90976d61ed4849adf8e45f0/diff",
                "WorkDir": "/var/lib/docker/overlay2/5f5a358dc6e6aa6ebf50e0bd225f16e1883b467da90976d61ed4849adf8e45f0/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:0271b8eebde3fa9a6126b1f2335e170f902731ab4942f9f1914e77016540c7bb",
                "sha256:4c752d379674f81a579202b7822bd7ea3ddb4af97e1476fea274b27065973d03",
                "sha256:00fddc56f2aada8d5b80729be6355c2fd613eda198655d83c3f3886061153f7a",
                "sha256:5b9b2e70291cc7df3650d13852462514c17188b67f73219df59e3c7990d7794d",
                "sha256:d8d91af87be16ea4fe4fbde416bb48dc1bac06af5925a95ec47e5c52905e2c2a"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

Any help on this is appreciated, thanks.

emby-docker-log.zip

Link to post
Share on other sites
Luke

Unfortunately the logs don't indicate anything obvious. Does OMV have any system logs that might be useful?

Link to post
Share on other sites

Ok, I checked the OMV system log which gives some info:

May 21 10:24:57 openmediavault monit[635]: 'filesystem_srv_dev-disk-by-label-Disk1' space usage 91.3% matches resource limit [space usage>85.0%]
May 21 10:25:07 openmediavault dockerd[31604]: time="2018-05-21T10:25:06-07:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/c0c92671fbdf0affd7a87a6c3b0783cf707ffa8e2edeea431d97fe29e72c46f2/shim.sock" debug=false module="containerd/tasks" pid=17579
May 21 10:27:11 openmediavault kernel: [827965.642491] EmbyServer[17845]: segfault at 0 ip 00007fd738a245c0 sp 00007fd6877fa298 error 4 in libc-2.17.so[7fd7389b2000+1aa000]
May 21 10:27:16 openmediavault dockerd[31604]: time="2018-05-21T10:27:16-07:00" level=info msg="shim reaped" id=c0c92671fbdf0affd7a87a6c3b0783cf707ffa8e2edeea431d97fe29e72c46f2 module="containerd/tasks"
May 21 10:27:16 openmediavault dockerd[31604]: time="2018-05-21T10:27:16.560138156-07:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
May 21 10:27:17 openmediavault dockerd[31604]: time="2018-05-21T10:27:17-07:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/c0c92671fbdf0affd7a87a6c3b0783cf707ffa8e2edeea431d97fe29e72c46f2/shim.sock" debug=false module="containerd/tasks" pid=18112

Link to post
Share on other sites
Luke

Is OMV up to date? I will have to double check but I think we need a higher version of libc than 2.17

Link to post
Share on other sites

I have a brand new install with the latest build AFAIK.  OMV 4.1.6 with Linux kernel 4.14.

If there is something newer than that, I'm not sure how to get it.

 

It looks like my libc version is 2.24.

root@openmediavault:~# ldd --version
ldd (Debian GLIBC 2.24-11+deb9u3) 2.24

Link to post
Share on other sites
Luke

This looks like a situation similar to what happened on terramaster for a while, a combination of runtime + libc + kernel that doesn't work well together on some hardware. It ultimately ended up resolving itself after updating third party libraries.

 

Your best bet is to try the docker beta with the .NET Core 2.1 runtime, as soon as we've pushed that to Docker beta. And that will hopefully be sometime this week. Thanks.

Link to post
Share on other sites
  • 2 weeks later...

Thanks.

How do I use the docker beta?  I tried to pull from emby/embyserver_beta but that didn't work for me.

 

beta is actually one of the available tags on the emby/embyserver container. please let us know if this helps. thanks.

Link to post
Share on other sites

Hey Guys,

 

Ive got the same Problem on the same OS. Everything worked fine until the recent updates in the docker images.

I had to downgrade the Image to 3.4.0.4 to get it working again... All above that ends in an endless restart of the container either latest or beta.

 

There is an error in my docker log that caused the failure and i will post that log as soon as I get home.

 

When i googled the error I came to corefx in github saying the error will be fixed in 2.0.3...

 

Anyways I upload the log as soon as I can! Thanks for the help.

Link to post
Share on other sites

Hey Guys,

 

Ive got the same Problem on the same OS. Everything worked fine until the recent updates in the docker images.

I had to downgrade the Image to 3.4.0.4 to get it working again... All above that ends in an endless restart of the container either latest or beta.

 

There is an error in my docker log that caused the failure and i will post that log as soon as I get home.

 

When i googled the error I came to corefx in github saying the error will be fixed in 2.0.3...

 

Anyways I upload the log as soon as I can! Thanks for the help.

 

Please see how to report a problem. thanks.

Link to post
Share on other sites

beta is actually one of the available tags on the emby/embyserver container. please let us know if this helps. thanks.

 

Okay, I tried running the beta.  Both emby/embyserver:latest and beta are crashing

 

Jun 16 16:15:24 openmediavault kernel: [1805672.622592] EmbyServer[11834]: segfault at 0 ip 00007f5f564345c0 sp 00007f5edaaad298 error 4 in libc-2.17.so[7f5f563c2000+1aa000]

embyserver.zip

emby docker log.zip

Link to post
Share on other sites

I don't see any specific updates to libc.  I have the updated openmediavault package.

ldd --version returns:  (Debian GLIBC 2.24-11+deb9u3) 2.24

Link to post
Share on other sites

Although I have compiled kernels in the past, I don't feel comfortable with doing this for OMV.  They have not released an updated kernel (4.17?) for OMV.  I will wait for the kernel update and try again and update this thread - although I don't know how often they update the kernel for OMV....

Link to post
Share on other sites
  • 2 years later...
ojessie

Hi,

unfortunately, I've to bring up this issue again. I'm having the same problem. Running emby on OMV 5.6.4.1 on portainer 2.1.1. Now and then there is a complete reset of emby. Meaning starting from scratch. Anyone have an idea how to fix it. 

Thanks. 

Link to post
Share on other sites
Luke
7 hours ago, ojessie said:

Hi,

unfortunately, I've to bring up this issue again. I'm having the same problem. Running emby on OMV 5.6.4.1 on portainer 2.1.1. Now and then there is a complete reset of emby. Meaning starting from scratch. Anyone have an idea how to fix it. 

Thanks. 

Hi there, please attach the emby server log from when this happens. Thanks 

Link to post
Share on other sites
  • 2 weeks later...
ojessie

@Luke

Update ... no further resetting's since deactivating watchtower ... I think that caused the problem.

Best

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...