New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build #137 has some DNS / tracker connectivity issues #49

Open
neo21670 opened this Issue Sep 8, 2018 · 15 comments

Comments

Projects
None yet
10 participants
@neo21670

neo21670 commented Sep 8, 2018

Host OS: Debian 9 (OMV 4 default)
Docker: latest CE stable

I am updating my containers with watchtower. Today, build 137 was pushed on Docker Hub and I noticed my torrents were down with the tracker status 'name: tracker unavailable' for all possible trackers. I verified and trackers were up and running and were accessible from any other client. Both container, host and hypervisor clocks are in sync and updated by NTP hourly.

I tried restarting the container and the VM hosting Docker. Neither bore any results - after restart all trackers were slowly polled and were unreachable. From the container I can ping any trackers so it doesn't seem to be a network connectivity issue. I have not tried other operations.

Considering these I rolled back to build 136. Startup with previous configuration had no issues, all my settings were retained. After everything loaded, all tracker statuses were back to normal 'name: Announce OK'.

@leomoty

This comment has been minimized.

Show comment
Hide comment
@leomoty

leomoty Sep 8, 2018

I have noticed the same, also rolled back to 136. Running Fedora Server 28 with Docker CE.

leomoty commented Sep 8, 2018

I have noticed the same, also rolled back to 136. Running Fedora Server 28 with Docker CE.

@yoyellow

This comment has been minimized.

Show comment
Hide comment
@yoyellow

yoyellow Sep 9, 2018

Same issue; rolled back to 136 fixed it. running latest docker on latest debian.

yoyellow commented Sep 9, 2018

Same issue; rolled back to 136 fixed it. running latest docker on latest debian.

@neo21670

This comment has been minimized.

Show comment
Hide comment
@neo21670

neo21670 Sep 9, 2018

I am totally unsure about the origins but would like to note, that some other container that experienced a similiar issue back then had its OpenSSL upgraded to a newer one with hardened default setting. Worth checking

neo21670 commented Sep 9, 2018

I am totally unsure about the origins but would like to note, that some other container that experienced a similiar issue back then had its OpenSSL upgraded to a newer one with hardened default setting. Worth checking

@leomoty

This comment has been minimized.

Show comment
Hide comment
@leomoty

leomoty Sep 9, 2018

Albeit I am not familiar, lsiobase/alpine:edge (which docker-deluge points to) is using libressl2.7.

leomoty commented Sep 9, 2018

Albeit I am not familiar, lsiobase/alpine:edge (which docker-deluge points to) is using libressl2.7.

@noxzobax

This comment has been minimized.

Show comment
Hide comment
@noxzobax

noxzobax Sep 11, 2018

same here.

[INFO ] 10:46:21 server:650 Starting server in PID 210.
[INFO ] 10:46:21 server:664 serving on 0.0.0.0:8112 view at http://127.0.0.1:8112
[INFO ] 10:46:21 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:28 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:28 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 server:681 Shutting down webserver

rollback to the version 136, everything is fine

noxzobax commented Sep 11, 2018

same here.

[INFO ] 10:46:21 server:650 Starting server in PID 210.
[INFO ] 10:46:21 server:664 serving on 0.0.0.0:8112 view at http://127.0.0.1:8112
[INFO ] 10:46:21 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:21 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:26 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:28 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 10:46:28 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 10:46:29 server:681 Shutting down webserver

rollback to the version 136, everything is fine

@aaomidi

This comment has been minimized.

Show comment
Hide comment
@aaomidi

aaomidi Sep 12, 2018

Same here.

aaomidi commented Sep 12, 2018

Same here.

@luchtgitaar

This comment has been minimized.

Show comment
Hide comment
@luchtgitaar

luchtgitaar commented Sep 14, 2018

+1

@leomoty

This comment has been minimized.

Show comment
Hide comment
@leomoty

leomoty Sep 18, 2018

Did anyone test build #138? It seems to be available now. I'll try when I get home.


Edit: still broken

leomoty commented Sep 18, 2018

Did anyone test build #138? It seems to be available now. I'll try when I get home.


Edit: still broken

@yoyellow

This comment has been minimized.

Show comment
Hide comment
@yoyellow

yoyellow Sep 20, 2018

issue persist in 138, rollback to 136 still required for working DNS

yoyellow commented Sep 20, 2018

issue persist in 138, rollback to 136 still required for working DNS

@gderf

This comment has been minimized.

Show comment
Hide comment
@gderf

gderf Sep 21, 2018

I also had to roll back as far as Tag:136. Tags 137, 138, and latest are broken.

gderf commented Sep 21, 2018

I also had to roll back as far as Tag:136. Tags 137, 138, and latest are broken.

@JigSawFr

This comment has been minimized.

Show comment
Hide comment
@JigSawFr

JigSawFr Sep 21, 2018

Same problem, need to roll back to 136

JigSawFr commented Sep 21, 2018

Same problem, need to roll back to 136

@OmgImAlexis

This comment has been minimized.

Show comment
Hide comment
@OmgImAlexis

OmgImAlexis Sep 21, 2018

@sparklyballs can you please look into this.

OmgImAlexis commented Sep 21, 2018

@sparklyballs can you please look into this.

@gderf

This comment has been minimized.

Show comment
Hide comment
@gderf

gderf Sep 22, 2018

Seems to be fixed in 139.

Thanks!

gderf commented Sep 22, 2018

Seems to be fixed in 139.

Thanks!

@ben-ba

This comment has been minimized.

Show comment
Hide comment
@ben-ba

ben-ba Sep 27, 2018

all versions above 136 (137,138,139) doesn't work for me, because the daemon (deluged) won't start.
Config files core.conf and auth are missing.

EDIT: the only thing i discovered is the following difference (all versions since 136 have the same code base); but the transmission image have the same "missing hostname" and works...

docker image ls

REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
linuxserver/deluge         latest              c04260f43b5c        5 days ago          174MB
linuxserver/deluge         138                 59339d848316        12 days ago         174MB
linuxserver/deluge         137                 5466ba8a8a5a        2 weeks ago         173MB
linuxserver/deluge         136                 b10ca6dd3a3e        3 weeks ago         173MB
linuxserver/transmission   latest              a7bb669d2504        5 weeks ago         36.2MB

  docker image inspect c04260f43b5c | grep Hostname
            "Hostname": "520616b5d24b",
            "Hostname": "",

  docker image inspect 59339d848316 | grep Hostname
            "Hostname": "c0506cec584e",
            "Hostname": "",

  docker image inspect 5466ba8a8a5a | grep Hostname
            "Hostname": "4d23870246d9",
            "Hostname": "",

  docker image inspect b10ca6dd3a3e | grep Hostname
            "Hostname": "b57c893839d0",
            "Hostname": "b57c893839d0“,

  docker image inspect a7bb669d2504 | grep Hostname
            "Hostname": "0db7a0508b6d",
            "Hostname": "",

ben-ba commented Sep 27, 2018

all versions above 136 (137,138,139) doesn't work for me, because the daemon (deluged) won't start.
Config files core.conf and auth are missing.

EDIT: the only thing i discovered is the following difference (all versions since 136 have the same code base); but the transmission image have the same "missing hostname" and works...

docker image ls

REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
linuxserver/deluge         latest              c04260f43b5c        5 days ago          174MB
linuxserver/deluge         138                 59339d848316        12 days ago         174MB
linuxserver/deluge         137                 5466ba8a8a5a        2 weeks ago         173MB
linuxserver/deluge         136                 b10ca6dd3a3e        3 weeks ago         173MB
linuxserver/transmission   latest              a7bb669d2504        5 weeks ago         36.2MB

  docker image inspect c04260f43b5c | grep Hostname
            "Hostname": "520616b5d24b",
            "Hostname": "",

  docker image inspect 59339d848316 | grep Hostname
            "Hostname": "c0506cec584e",
            "Hostname": "",

  docker image inspect 5466ba8a8a5a | grep Hostname
            "Hostname": "4d23870246d9",
            "Hostname": "",

  docker image inspect b10ca6dd3a3e | grep Hostname
            "Hostname": "b57c893839d0",
            "Hostname": "b57c893839d0“,

  docker image inspect a7bb669d2504 | grep Hostname
            "Hostname": "0db7a0508b6d",
            "Hostname": "",
@noxzobax

This comment has been minimized.

Show comment
Hide comment
@noxzobax

noxzobax Sep 30, 2018

Still the same problem with the version 140 (same if I add missing conf file):

[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] 10-adduser: executing...
usermod: no changes

User uid: 911
User gid: 911

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[INFO ] 12:43:34 configmanager:70 Setting config directory to: /config
[INFO ] 12:43:34 ui:124 Deluge ui 1.3.15
[INFO ] 12:43:34 ui:127 Starting web ui..
[WARNING ] 12:43:35 config:364 Unable to open config file /config/web.conf: [Errno 2] No such file or irectory: '/config/web.conf'
[WARNING ] 12:43:35 config:364 Unable to open config file /config/hostlist.conf.1.2: [Errno 2] No such
file or directory: '/config/hostlist.conf.1.2'
[WARNING ] 12:43:35 config:423 Unable to open config file: /config/hostlist.conf.1.2 because: [Errno 2] No such file or directory: '/config/hostlist.conf.1.2'
[WARNING ] 12:43:35 config:443 Unable to backup old config...
[INFO ] 12:43:35 server:666 Starting server in PID 215.
[INFO ] 12:43:35 server:679 Serving on 0.0.0.0:8112 view at http://0.0.0.0:8112
[INFO ] 12:43:56 auth:327 Login success (ClientIP 172.17.0.1)
[INFO ] 12:43:58 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 12:43:58 client:217 Connecting to daemon at 127.0.0.1:58846..
[WARNING ] 12:43:58 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[WARNING ] 12:43:58 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[INFO ] 12:44:00 client:217 Connecting to daemon at 127.0.0.1:58846..
[WARNING ] 12:44:00 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[WARNING ] 12:44:03 config:423 Unable to open config file: /config/web.conf because: [Errno 2] No such file or directory: '/config/web.conf'
[WARNING ] 12:44:03 config:443 Unable to backup old config...

noxzobax commented Sep 30, 2018

Still the same problem with the version 140 (same if I add missing conf file):

[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] 10-adduser: executing...
usermod: no changes

User uid: 911
User gid: 911

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[INFO ] 12:43:34 configmanager:70 Setting config directory to: /config
[INFO ] 12:43:34 ui:124 Deluge ui 1.3.15
[INFO ] 12:43:34 ui:127 Starting web ui..
[WARNING ] 12:43:35 config:364 Unable to open config file /config/web.conf: [Errno 2] No such file or irectory: '/config/web.conf'
[WARNING ] 12:43:35 config:364 Unable to open config file /config/hostlist.conf.1.2: [Errno 2] No such
file or directory: '/config/hostlist.conf.1.2'
[WARNING ] 12:43:35 config:423 Unable to open config file: /config/hostlist.conf.1.2 because: [Errno 2] No such file or directory: '/config/hostlist.conf.1.2'
[WARNING ] 12:43:35 config:443 Unable to backup old config...
[INFO ] 12:43:35 server:666 Starting server in PID 215.
[INFO ] 12:43:35 server:679 Serving on 0.0.0.0:8112 view at http://0.0.0.0:8112
[INFO ] 12:43:56 auth:327 Login success (ClientIP 172.17.0.1)
[INFO ] 12:43:58 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 12:43:58 client:217 Connecting to daemon at 127.0.0.1:58846..
[WARNING ] 12:43:58 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[WARNING ] 12:43:58 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[INFO ] 12:44:00 client:217 Connecting to daemon at 127.0.0.1:58846..
[WARNING ] 12:44:00 client:220 Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused.
[WARNING ] 12:44:03 config:423 Unable to open config file: /config/web.conf because: [Errno 2] No such file or directory: '/config/web.conf'
[WARNING ] 12:44:03 config:443 Unable to backup old config...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment