For any reason this is not taking effect for me. I’ve added the lines to my docker-compose file but relay is still trying to resolve the IPv6 for the service name.
root@basecamp /srv/sentry # docker-compose config
networks:
default: {}
sentry-proxy:
external: true
name: nginx-proxy_sentry
services:
relay:
depends_on:
kafka:
condition: service_started
redis:
condition: service_started
image: getsentry/relay:20.12.1
restart: unless-stopped
sysctls:
net.ipv6.conf.all.disable_ipv6: '1'
volumes:
- read_only: true
source: /srv/sentry/geoip
target: /geoip
type: bind
- read_only: true
source: /srv/sentry/relay
target: /work/.relay
type: bind
The error is still the same:
2020-12-29T23:17:54Z [relay_server::actors::upstream] ERROR: authentication encountered error: could not send request to upstream
caused by: could not send request using actix-web client
caused by: Failed to connect to host: Failed resolving hostname: no record found for name: web type: AAAA class: IN
caused by: Failed resolving hostname: no record found for name: web type: AAAA class: IN
caused by: Failed resolving hostname: no record found for name: web type: AAAA class: IN
2020-12-29T23:18:08Z [relay_server::actors::upstream] WARN: Network outage, scheduling another check in 60s
Looking up the DNS (IPv4) from the container itself using dig
works:
root@07af2dcb0fac:/work# dig web
; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> web
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19165
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;web. IN A
;; ANSWER SECTION:
web. 600 IN A 172.27.0.21
;; Query time: 0 msec
;; SERVER: 127.0.0.11#53(127.0.0.11)
;; WHEN: Tue Dec 29 23:22:02 UTC 2020
;; MSG SIZE rcvd: 40
Github Issue: https://github.com/getsentry/onpremise/issues/608
Same Topic here in the forum: How to troubleshoot: There is 1 issue with your system configuration