hurricanehrndz 149 Posted June 23, 2017 Share Posted June 23, 2017 (edited) I was still getting the problem after removing the Docker, and deleting the emby folder, then reinstalling emby via community apps? However, it then dawned on me that there are two versions on community apps, and of course I have been using the wrong one, grrrrr! I've now installed the stable version and all is well again. Yes! On top of that, I don't believe the personal templates are ever rysnced with the ones listed on community apps, so when we make changes to the template you have to rebuild the container, by removing the "My" version and recreating from the community apps. Edited June 23, 2017 by hurricanehrndz Link to comment Share on other sites More sharing options...
TrainAss 22 Posted June 23, 2017 Share Posted June 23, 2017 There was a typo in the docker file in regards to expose the /config volume correctly. I'm sure this added to your issue. Would it be advisable to delete not only the image but the container as well and start them again from scratch for the beta channel? ( Have my Emby configs backed up so a restore will bring everything back to life quickly) Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted June 23, 2017 Share Posted June 23, 2017 Just tar up the /config folder and hope that it wasn't corrupted. Your issue had very little to do with the typo and more to do with the image name. Sent from my ONEPLUS A3000 using Tapatalk Link to comment Share on other sites More sharing options...
TrainAss 22 Posted June 24, 2017 Share Posted June 24, 2017 (edited) Ok, so I tried what hurricanehrndz suggested. Emby would make me run through the setup again, however when I'd reboot I'd get a bunch of exceptions stating that a link was missing. I decided to cut my losses and start again (thank goodness for backups). I nuked my Emby images and container and started over from nothing in that regard. Now when I attempt to launch EmbyServer (Beta or stable), I can't pull up the WebUI and the logs keeps filling with the attached two files, it's as if the server keeps restarting over and over. My OMV is 2.2.14, and I've patched and updated. I've attached the logs I have from Emby. My docker is as follows Client:Version: 17.05.0-ceAPI version: 1.29Go version: go1.7.5Git commit: 89658beBuilt: Thu May 4 22:13:40 2017OS/Arch: linux/amd64 Server:Version: 17.05.0-ceAPI version: 1.29 (minimum version 1.12)Go version: go1.7.5Git commit: 89658beBuilt: Thu May 4 22:13:40 2017OS/Arch: linux/amd64Experimental: false server-63633847919.txt unhandled_848be8f3-727c-42c2-bd73-39b51e73e645.txt Edited June 24, 2017 by TrainAss Link to comment Share on other sites More sharing options...
Luke 37095 Posted June 24, 2017 Author Share Posted June 24, 2017 @@TrainAss, that is currently an open issue on the beta channel. i should have beta up with a fix early on tomorrow. But that particular issue won't affect stable, so if you're having an issue there it is something different. Link to comment Share on other sites More sharing options...
TrainAss 22 Posted June 24, 2017 Share Posted June 24, 2017 @@TrainAss, that is currently an open issue on the beta channel. i should have beta up with a fix early on tomorrow. But that particular issue won't affect stable, so if you're having an issue there it is something different. OK, Thanks for the quick reply Luke. I'm good in the beta channel (have been for a while). I'll be patient. Thanks again for your hard work. Link to comment Share on other sites More sharing options...
hoppel118 37 Posted June 24, 2017 Share Posted June 24, 2017 My OMV is 2.2.14, and I've patched and updated. I've attached the logs I have from Emby. My docker is as follows By the way... In the omv forum I read that its recommended to use omv3 instead of omv2. There are some issues under omv2. Greetings Hoppel Link to comment Share on other sites More sharing options...
TrainAss 22 Posted June 24, 2017 Share Posted June 24, 2017 Thanks @@hoppel118. I upgraded to OMV3 today successfully, my containers are all running and working, however Emby is refusing to connect I've attached my logs from Emby. I've got Embyserver_beta installed. My docker is as follows Client:Version: 17.05.0-ceAPI version: 1.29Go version: go1.7.5Git commit: 89658beBuilt: Thu May 4 22:04:27 2017OS/Arch: linux/amd64 Server: Version: 17.05.0-ceAPI version: 1.29 (minimum version 1.12)Go version: go1.7.5Git commit: 89658beBuilt: Thu May 4 22:04:27 2017OS/Arch: linux/amd64Experimental: false OMV Ver. 3.0.80 Kernel 3.16.0-0.bpo.4-amd64 server-63633902028.txt unhandled_22c7890a-8f54-4101-a894-0d5a0514bfc2.txt Link to comment Share on other sites More sharing options...
Luke 37095 Posted June 24, 2017 Author Share Posted June 24, 2017 I've posted .12 beta which should resolve the Skia unhandled exception. Thanks. Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 3, 2017 Share Posted July 3, 2017 I don't see any updated images for stable or beta for like more than a week. Anyone sees the same? https://hub.docker.com/r/emby/embyserver/builds/ 1 Link to comment Share on other sites More sharing options...
Luke 37095 Posted July 3, 2017 Author Share Posted July 3, 2017 They'll be back soon. Thank you for your patience. Link to comment Share on other sites More sharing options...
TrainAss 22 Posted July 3, 2017 Share Posted July 3, 2017 I don't see any updated images for stable or beta for like more than a week. Anyone sees the same? https://hub.docker.com/r/emby/embyserver/builds/ Make sure that you're pulling Emby/Embyserver_beta Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 3, 2017 Share Posted July 3, 2017 (edited) They'll be back soon. Thank you for your patience. @@Luke, any estimate? This usually doesn't take that long, just the time to rebuild Edited July 3, 2017 by anderbytes Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 4, 2017 Share Posted July 4, 2017 What exactly is happening? Stable is out for days and Docker got nothing so far. Sent from my ASUS_Z017DA using Tapatalk Link to comment Share on other sites More sharing options...
Luke 37095 Posted July 4, 2017 Author Share Posted July 4, 2017 @@anderbytes thank you for your patience. Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted July 5, 2017 Share Posted July 5, 2017 Sure guys, I'm in the process of getting my build systems setup again. I've had recently changed jobs and hardware. I'm hoping to get it done by Friday at the latest, but hope to have something up sooner Sent from my ONEPLUS A3000 using Tapatalk 1 Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted July 5, 2017 Share Posted July 5, 2017 The internal update method should still work for docker. Please use that in the meantime Sent from my ONEPLUS A3000 using Tapatalk Link to comment Share on other sites More sharing options...
aptalca 70 Posted July 5, 2017 Share Posted July 5, 2017 What exactly is happening? Stable is out for days and Docker got nothing so far. Sent from my ASUS_Z017DA using Tapatalk You can recreate the container with EDGE=1 and it will update during each restart 1 Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted July 6, 2017 Share Posted July 6, 2017 Updates and builds are back up again. 1 Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 6, 2017 Share Posted July 6, 2017 Thanks folks. Link to comment Share on other sites More sharing options...
kugelzucker 1 Posted July 8, 2017 Share Posted July 8, 2017 (edited) hello, since i am not the only one using docker and emby and there is no raging mob here i guess i am doing something wrong. since i didnt find it by myself i am now here looking for help. installed docker on a fresh centos7, followed the instructions to forward IP traffic to the host (systemd specific) found on the docker-install-site https://docs.docker.com/engine/installation/linux/linux-postinstall/#ip-forwarding-problems)and started the installation of emby using the commands given on https://emby.media/docker-server.html as root for root. [root@sonne ~]# docker version Client: Version: 17.06.0-ce API version: 1.30 Go version: go1.8.3 Git commit: 02c1d87 Built: Fri Jun 23 21:20:36 2017 OS/Arch: linux/amd64 Server: Version: 17.06.0-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: 02c1d87 Built: Fri Jun 23 21:21:56 2017 OS/Arch: linux/amd64 Experimental: false [root@sonne ~]# docker info Containers: 1 Running: 1 Paused: 0 Stopped: 0 Images: 2 Server Version: 17.06.0-ce Storage Driver: overlay Backing Filesystem: xfs Supports d_type: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4 init version: 949e6fa Security Options: seccomp Profile: default Kernel Version: 3.10.0-514.26.2.el7.x86_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 15.35GiB Name: sonne.local ID: WHM6:EQZF:FT6P:WERI:YGKY:AIUO:RGOD:Q73F:T7B4:HPP5:MNO5:XIUS Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false i am running centos7 [root@sonne ~]# hostnamectl Static hostname: sonne.local Icon name: computer-desktop Chassis: desktop Machine ID: 0158544367224c2bb2c77105d4d0a270 Boot ID: ad9d4220f321451cb1dec518e5f74426 Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-514.26.2.el7.x86_64 Architecture: x86-64 i cant connect to emby from a remote host, nor do i see any open ports on the docker host itself using nmap nmap -sT -O localhost selinux is disabled as well [root@sonne ~]# getenforce Permissive any hints or things i could try are greatly appreciated. Edited July 8, 2017 by kugelzucker Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 8, 2017 Share Posted July 8, 2017 First of all, you are using nmap on the wrong interface. Using it on localhost won't tell you anything, as only points to the loopback address. The best way to look for open ports is using command "netstat" or "ss" and greping for "LISTEN" Sent from my ASUS_Z017DA using Tapatalk Link to comment Share on other sites More sharing options...
anderbytes 139 Posted July 8, 2017 Share Posted July 8, 2017 My preferred command: ss -anoe | grep LISTEN Sent from my ASUS_Z017DA using Tapatalk Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted July 8, 2017 Share Posted July 8, 2017 This might be a docker issue, which version are you using? For simplicity the container is created with the network set to host. The latest release of docker destroys the ipv6 stack making localhost unreasovable and the Network acts wonky. Sent from my ONEPLUS A3000 using Tapatalk Link to comment Share on other sites More sharing options...
kugelzucker 1 Posted July 9, 2017 Share Posted July 9, 2017 My preferred command: ss -anoe | grep LISTEN Sent from my ASUS_Z017DA using Tapatalk alright, will look into that ... here is the output of ss [root@sonne ~]# ss -anoe | grep LISTEN u_str LISTEN 0 100 public/pickup 27651 * 0 u_str LISTEN 0 128 /run/lvm/lvmetad.socket 13864 * 0 u_str LISTEN 0 128 /run/systemd/journal/stdout 7769 * 0 u_str LISTEN 0 128 /var/run/docker.sock 26212 * 0 u_str LISTEN 0 100 private/rewrite 27665 * 0 u_str LISTEN 0 100 public/qmgr 27658 * 0 u_str LISTEN 0 100 public/flush 27680 * 0 u_str LISTEN 0 100 private/bounce 27668 * 0 u_str LISTEN 0 100 public/showq 27695 * 0 u_str LISTEN 0 100 private/defer 27671 * 0 u_str LISTEN 0 100 private/trace 27674 * 0 u_str LISTEN 0 128 /var/run/docker/metrics.sock 26738 * 0 u_str LISTEN 0 100 private/verify 27677 * 0 u_str LISTEN 0 128 /var/run/docker/libcontainerd/docker-containerd.sock 26226 * 0 u_str LISTEN 0 100 private/proxymap 27683 * 0 u_str LISTEN 0 100 private/proxywrite 27686 * 0 u_str LISTEN 0 100 private/smtp 27689 * 0 u_str LISTEN 0 100 private/relay 27692 * 0 u_str LISTEN 0 100 private/error 27698 * 0 u_str LISTEN 0 100 private/retry 27701 * 0 u_str LISTEN 0 100 private/discard 27704 * 0 u_str LISTEN 0 100 private/local 27707 * 0 u_str LISTEN 0 100 private/virtual 27710 * 0 u_str LISTEN 0 100 private/lmtp 27713 * 0 u_str LISTEN 0 100 private/anvil 27716 * 0 u_str LISTEN 0 100 private/scache 27719 * 0 u_str LISTEN 0 100 public/cleanup 27655 * 0 u_str LISTEN 0 128 /run/systemd/private 9105 * 0 u_str LISTEN 0 128 /run/docker/libnetwork/6b4e6bdf3e775c6e59868583eb21fc02269df92645e9e45bf017f0d4d9328c59.sock 27795 * 0 u_seq LISTEN 0 128 /run/udev/control 14518 * 0 u_str LISTEN 0 100 private/tlsmgr 27662 * 0 u_str LISTEN 0 128 /var/run/dbus/system_bus_socket 19166 * 0 u_str LISTEN 0 128 /run/lvm/lvmpolld.socket 14063 * 0 tcp LISTEN 0 128 *:22 *:* ino:24348 sk:ffff880411ee8000 <-> tcp LISTEN 0 100 127.0.0.1:25 *:* ino:25599 sk:ffff880415300000 <-> tcp LISTEN 0 128 :::22 :::* ino:24357 sk:ffff88041d218000 v6only:1 <-> tcp LISTEN 0 100 ::1:25 :::* ino:25600 sk:ffff88041e748000 v6only:1 <-> Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now