Jump to content

Docker

Luke

By Luke
in Linux

 Share

Recommended Posts

Sergio

Sergio   4

Posted
Posted

Good morning. Dear Luke, as my loss where several megs in size and I was connected using Tapatalk, I sent them via PM to hurricane. Perhaps I was to sleep at that hours yesterday.

 

@hurricanehdz: nope, it happened all the time during the play of the entire star trek ds9 (7 seasons) and also films. Those are old known files that I already played thousands of times before.

This happens from two versions ago.

 

Enviado desde mi A0001 mediante Tapatalk

Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted (edited)

 

Seems like is an issue with the latest release of ffmpeg. I will see about obtaining rebuilding the container with an older static build.

 

Sent from my ONEPLUS A3000 using Tapatalk

Edited by hurricanehrndz
Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted (edited)

For the people having troubles with ffmpeg please execute the following command to update ffmpeg within the container. 

docker exec -it emby-server bash -c 'zypper --non-interactive in curl; \                                                                                                                                        ⏎
curl -sL https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz | \
tar -C /bin --extract -J --wildcards "*/ffmpeg" --wildcards "*/ffprobe" --strip-components=1'

Please test the files that were giving you issues. Report back.

Edited by hurricanehrndz
Link to comment
Share on other sites
soniCron

soniCron   5

Posted
Posted

Oy, nevermind.

 

Downgraded to 3.1.4 and it works fine.

 

For anyone interested:

docker exec -it emby-server bash -c 'zypper --non-interactive in curl; \                                                                                                                                        ⏎
curl -sL https://johnvansickle.com/ffmpeg/releases/ffmpeg-3.1.4-64bit-static.tar.xz | \
tar -C /bin --extract -J --wildcards "*/ffmpeg" --wildcards "*/ffprobe" --strip-components=1'

For what it's worth, looks like the stream isn't correct/intact until after ffmpeg is done encoding. I'm not sure what's going on, but reading from it before it's encoding = failure, but letting it finish or cancelling it rewrites the header and then the stream is playable.

Link to comment
Share on other sites
Sergio

Sergio   4

Posted
Posted

Thanks for the feedback. ffmpeg will be downgraded on base image.

You said that you saw something wrong in the header of the file that failed me in the logs. Could this be what you saw?

If not I would continue diagnosing my network and server. [emoji6]

 

Enviado desde mi A0001 mediante Tapatalk

Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted (edited)

You said that you saw something wrong in the header of the file that failed me in the logs. Could this be what you saw?

If not I would continue diagnosing my network and server. [emoji6]

 

Enviado desde mi A0001 mediante Tapatalk

When I read through your log, ffmpeg mention an issue with the header of some of your files. This could be a bug in the latest release of ffmpeg.

Edited by hurricanehrndz
  • Like 1
Link to comment
Share on other sites
  • 2 weeks later...
Sergio

Sergio   4

Posted
Posted

Yesterday I replaced the container because some strange thing was happening, I could use emby with the apps but the web interface was offline.

Well, with a new one I can say the above issue was corrected. I played some files yesterday without issues.
 

But at nighttime something happened and my emby installation started to say that the username or password for all my users where wrong. This morning I dropped and reinstalled the container, but now I doesn't start. The probabilities of being something not related to emby are high, but as I'm using exactly all the same configuration and folders, I'll post it here. Perhaps you know whats happening.

 

I create my container with:

docker run --name emby-server --restart=unless-stopped \
    --net=host -e auto_update_on=true \
    -e APP_UID=1016 -e APP_GID=1011 \
    -e TZ=Europe/Madrid -e LANG=es_ES.UTF-8 \
    -v /media/virtservices/docker-data/emby:/config \
    -v /media/storage:/media/storage \
    -d emby/embyserver

The executing user and group are media:media

# getent passwd
media:x:1016:1011::/home/media:/usr/sbin/nologin

# getent group
media:x:1011:sergio,media

# ll /media/virtservices/docker-data
drwxrwx--- 15 media      media     4,0K feb  7  2016 emby

# ll /media
drwxrwxr-x 11 media users 4,0K dic 11 20:04 storage
drwxrwxr-x  8 root  root  4,0K dic 11 20:25 virtservices

this hasn't changed, that I know.

 

This is the log I get when I create and run the container

m2016-12-13T10:07:53.547323790Z [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
e2016-12-13T10:07:53.565662479Z [s6-init] ensuring user provided files have correct perms...exited 0.
W2016-12-13T10:07:53.566033953Z [fix-attrs.d] applying ownership & permissions fixes...
32016-12-13T10:07:53.566894751Z [fix-attrs.d] done.
[2016-12-13T10:07:53.567156480Z [cont-init.d] executing container initialization scripts...
L2016-12-13T10:07:53.567580483Z [cont-init.d] 01-conf-onetime: executing... 
H2016-12-13T10:07:53.607356008Z [cont-init.d] 01-conf-onetime: exited 0.
L2016-12-13T10:07:53.607788636Z [cont-init.d] 02-user-onetime: executing... 
H2016-12-13T10:07:53.792127082Z [cont-init.d] 02-user-onetime: exited 0.
O2016-12-13T10:07:53.792528430Z [cont-init.d] 03-upgrade-onetime: executing... 
K2016-12-13T10:07:53.794137299Z [cont-init.d] 03-upgrade-onetime: exited 0.
32016-12-13T10:07:53.794465656Z [cont-init.d] done.
>2016-12-13T10:07:53.794808627Z [services.d] starting services
22016-12-13T10:07:53.797683691Z [services.d] done.
P2016-12-13T10:07:53.860765658Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:54.809191780Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:55.810577272Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:56.819372777Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:57.813328950Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:58.814251951Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:07:59.820645047Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:00.822151335Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:01.817241141Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:02.818778971Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:03.820109184Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:04.821331233Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:05.822519217Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:06.825168547Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:07.825499808Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:08.831935335Z su: failed to execute /bin/sh: Permission denied
P2016-12-13T10:08:09.838370654Z su: failed to execute /bin/sh: Permission denied
.....

The media user never had login.

Do anyone know what may be wrong there?

 

(I'm runing Debian Jessie with systemd)

Link to comment
Share on other sites
anderbytes

anderbytes   139

Posted
Posted

What happens if you just run a new container from scratch? Without using the current volumes.

 

If a brand new container also fails to start... it may be something related to your docker user or installation

Link to comment
Share on other sites
Sergio

Sergio   4

Posted
Posted

It's working again. But I had to completely erase the /var/lib/docker folder, the docker-data/emby folder, then create the docker configuration and emby container from scratch and then transfer my emby configurations from a backup.

 

I suppose it was something on my docker installation. Perhaps.... I was using a symlink to move the docker configuration folder and now I setup a bind in fstab,

 

One little thing... for transferring the configuration I simply dumped the old config folder. I removed a ffmpeg symlink that was there, and several other temp things. What else I can safely remove for cleaning without loosing metadata and config?

Link to comment
Share on other sites
mgworek

mgworek   121

Posted
Posted

I updated my docker to the latest beta and now it won't start. It doesn't create a emby log but here is what the docker log is saying.

 

"[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done."

Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted

@@mgworek

 

Thank you. Well aware, there is many changes going into the containers right now to support arm. Sorry for the trouble. It should be sorted soon.

Link to comment
Share on other sites
mgworek

mgworek   121

Posted
Posted

I went back to the stable build just to get up and running. I then downloaded the beta and and this time it loaded. Not sure if the docker was update between my attempts but working now.

 

Thanks!

Link to comment
Share on other sites
Sergio

Sergio   4

Posted
Posted

Sad to say that for me, the transcoding abort is still there.

I'm uploading logs from a playing session that stopped two times.

Also there are plenty of errors while emby is starting, It could be so helpful if you can see what plugin or module is causing it. I see it can be something with an old plugin not having the right catalog for the class injector. So simply uninstalling can do the trick.

 

emby-jump.zip

Link to comment
Share on other sites
Pancho

Pancho   9

Posted
Posted
Server Version 3.0.8500.0 (runs on Unraid 6.2.4 Docker)

 

 

Hurricane,

 

Early this morning I noticed there was an update for my EmbyServer currently running (Running production releases only).  After updating via the GUI interface, my server now shows 3.1.0.0. BETA installed.    In addition, below this is another message (see attached pic): 

 

A new version of Emby Server is available!

Version 3.1.259 is now available for download.

 

 

Manually updating the docker (docker exec EmbyServer update) via the console doesn't work either, I am still stuck with the beta release.    I believe the update may have incorrectly pulled the beta down and not the latest release.  

 

Can you investigate?   

 

Thanks.

 

Pancho

 

post-688-0-74016400-1482078440_thumb.jpg

Link to comment
Share on other sites
teiva

teiva   18

Posted
Posted

Hi,

 

I tried to do an update and apparently messed something up. I probably should not have forced the remove on my container. I should really go through some docker tutorials, but I figured it's a fundamental someone could point out quickly. 

 

~$ sudo docker rm -f <containerID>

~$ sudo docker exec emby-server update
Error response from daemon: No such container: emby-server

~$ systemctl status emby-server.service
● emby-server.service - Emby Media Server
Loaded: loaded (/etc/systemd/system/emby-server.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Sun 2016-12-18 09:22:50 PST; 18s ago
Process: 3175 ExecStartPre=/usr/bin/docker pull emby/embyserver:latest (code=killed, signal=TERM)

Dec 18 09:22:32 avocado docker[3175]: 33046b3b32fa: Pulling fs layer
Dec 18 09:22:32 avocado docker[3175]: 8f5cd8a98a50: Pulling fs layer
Dec 18 09:22:32 avocado docker[3175]: 650d4863e9f8: Pulling fs layer
Dec 18 09:22:32 avocado docker[3175]: 650d4863e9f8: Waiting
Dec 18 09:22:32 avocado docker[3175]: 8f5cd8a98a50: Verifying Checksum
Dec 18 09:22:32 avocado docker[3175]: 8f5cd8a98a50: Download complete
Dec 18 09:22:50 avocado systemd[1]: emby-server.service: Start-pre operation timed out. Terminating.
Dec 18 09:22:50 avocado systemd[1]: Failed to start Emby Media Server.
Dec 18 09:22:50 avocado systemd[1]: emby-server.service: Unit entered failed state.
Dec 18 09:22:50 avocado systemd[1]: emby-server.service: Failed with result 'timeout'.

~$ docker ps -all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
~$ docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
emby/embyserver latest a2e6e3cd4c0f 5 weeks ago 681.9 MB
emby/embyserver <none> d8925dfdae7d 8 weeks ago 681.9 MB
emby/embyserver <none> e8db73a21f89 9 weeks ago 590.3 MB
emby/embyserver <none> 270443911717 10 weeks ago 592 MB
hello-world latest c54a2cc56cbb 5 months ago 1.848 kB

Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted (edited)

 

Server Version 3.0.8500.0 (runs on Unraid 6.2.4 Docker)
 
 
Hurricane,
 
Early this morning I noticed there was an update for my EmbyServer currently running (Running production releases only).  After updating via the GUI interface, my server now shows 3.1.0.0. BETA installed.    In addition, below this is another message (see attached pic): 
 
A new version of Emby Server is available!
Version 3.1.259 is now available for download.
 
 
Manually updating the docker (docker exec EmbyServer update) via the console doesn't work either, I am still stuck with the beta release.    I believe the update may have incorrectly pulled the beta down and not the latest release.  
 
Can you investigate?   
 
Thanks.
 
Pancho

 

Not sure what to happen. Please know in the future though that updates take time to propagate through the build services we employ.  I will look through the update script and ensure it is working accordingly. I will post back an update.

Edited by hurricanehrndz
Link to comment
Share on other sites
hurricanehrndz

hurricanehrndz   149

Posted
Posted (edited)

Not sure what to happen. Please know in the future though that updates take time to propagate through the build services we employ.  I will look through the update script and ensure it is working accordingly. I will post back an update.

I looked through the scripts it is all good from our end. Perhaps unRAID changed how they apply updates. Perhaps they no longer filter via a tag. I'm not sure.

 

Looking through the list of builds on the hub, I can see that the build prior the latest stable, was the beta and it's version is 259 something. Please remember to be patient, that updates take time. It takes approximately 4 hours after the release has been tagged on github.

 

I'm only speculating here, but I think unRAID now updates to whatever the latest build was and ignores the tag. I check the release notes for 6.2.4 and don't see anything about the update mechanism being changed.

Edited by hurricanehrndz
Link to comment
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
 Share
Go to topic listing
×
×
  • Create New...