kong网关无法连接consul的8600端口

问答 / 1 / 11 / 创建于 2年前

所有服务都写在docker中，包括Postgres、kong、konga、consul，如果不配置kong的dns_resolver，一切都正常，konga能访问，新增service也正常，在Postgres当中也能查到数据，访问consul的8500界面也能行。
但是配置了dns_resolver后看日志一直提示连接127.0.0.1:8600失败，以下为docker-comspoe.yml文件部分内容（只贴出相关的kong和consul）：

version: "3.7"

volumes:
  kong_data: {}
networks:
  kong-net:

services:

  #######################################
  # Kong: The API Gateway
  #######################################
  kong:
    image: kong/kong-gateway:2.8.1.1-alpine
    restart: on-failure
    networks:
      - kong-net
    environment:
      - KONG_DATABASE=postgres
      - KONG_PG_HOST=kong-database
      - KONG_PG_USER=kong
      - KONG_PG_PASSWORD=kongpass
      - KONG_PROXY_ACCESS_LOG=/dev/stdout
      - KONG_ADMIN_ACCESS_LOG=/dev/stdout
      - KONG_PROXY_ERROR_LOG=/dev/stderr 
      - KONG_ADMIN_ERROR_LOG=/dev/stderr
      # KONG_PROXY_LISTEN: 0.0.0.0:8000
      # KONG_PROXY_LISTEN_SSL: 0.0.0.0:8443
      - KONG_ADMIN_LISTEN=0.0.0.0:8001
      # - KONG_DNS_RESOLVER=127.0.0.1:8600
      - KONG_ADMIN_GUI_URL=http://localhost:8002
    volumes:
      - ./kong.conf:/etc/kong/kong.conf.default
    depends_on:
      - kong-database
    healthcheck:
      test: ["CMD", "kong", "health"]
      interval: 10s
      timeout: 10s
      retries: 10
    ports:
      - "8000:8000"
      - "8001:8001"
      - "8002:8002"
      - "8003:8004"
      - "8004:8004"
      - "8443:8443"
      - "8444:8444"
      - "8445:8445"
  #######################################
  # Consul: Consul
  #######################################
  consul:
    image: hashicorp/consul:latest
    networks:
      - kong-net
    command: agent -dev -client=0.0.0.0
    ports:
      - "8300:8300"
      - "8301:8301"
      - "8302:8302"
      - "8500:8500"
      - "8600:8600"
      - "8600:8600/udp"

[lua] clients.lua:28: [openid-connect] failed to get from node cache: [postgres] [cosocket] DNS resolution failed: dns lookup pool exceeded retries (1): failed to receive reply from UDP server 127.0.0.1:8600: connection refused. Tried: [ "(short)kong-database:(na) - cache-miss", "kong-database:33 - cache-miss/scheduled/querying/try 1 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/scheduled/querying/try 2 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/dns lookup pool exceeded retries (1): failed to receive reply from UDP server 127.0.0.1:8600: connection refused", "kong-database:1 - cache-miss/scheduled/querying/try 1 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/scheduled/querying/try 2 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/dns lookup pool exceeded retries (1): failed to receive reply from UDP server 127.0.0.1:8600: connection refused", "kong-database:5 - cache-miss/scheduled/querying/try 1 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/scheduled/querying/try 2 error: failed to receive reply from UDP server 127.0.0.1:8600: connection refused/dns lookup pool exceeded retries (1): failed to receive reply from UDP server 127.0.0.1:8600: connection refused" ], context: ngx.timer

[error] 2089#0: *259098 [lua] init.lua:317: execute(): DNS resolution failed: dns lookup pool exceeded retries (1): timeout. Tried: [ "(short)goods-web.service.consul:(na) - cache-miss","goods-web.service.consul:33 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout", "goods-web.service.consul:1 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout", "goods-web.service.consul:5 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout"], client: 192.168.3.101, server: kong, request: "GET /v1 HTTP/1.1", host: "192.168.3.102:8000"

;; reply from unexpected source: 172.18.0.1#8600, expected 192.168.3.102#8600 ;; reply from unexpected source: 172.18.0.1#8600, expected 192.168.3.102#8600 ;; reply from unexpected source: 172.18.0.1#8600, expected 192.168.3.102#8600 ; <<>> DiG 9.16.29 <<>> @192.168.3.102 -p 8600 goods-web.service.consul SRV ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

讨论数量: 11

meigo

121 声望

报错贴一下把

2年前评论

meitian （楼主）

- KONG_DNS_RESOLVER=127.0.0.1:8600

放开试一下把　看下能不能解决参考一下 cloud.tencent.com/developer/ask/so...

这篇文章我看了，应该是使用consul以后docker自带的dns服务都失效了，然后这些用服务名称代替IP地址的方式就都失效了。

docker ps 一下　看下容器有没有启动　看有没有端口映射之类的　　要不就卸载重新来一遍把　

我现在kong能连接consul了，但是设置kong的service为goods-web.service.consul后无法访问，看kong的日志dns都解析出服务地址了，但就是访问不了。你看一下日志，192.168.3.101就是我的商品服务的地址。

meigo （作者）

@meitian 是通过192.168.3.102这台机子访问的吗　　先在本机访问　如果本机可以访问到　那有可能就是网关的问题了

是我理解错了，这里面的192.168.3.101不是解析出来的地址，是我浏览器主机的地址，我进入kong的docker中使用了一下dig命令

dig @192.168.3.102 -p 8600 goods-web.service.consul SRV

结果如下：

192.168.3.102是我虚拟机的地址，172.18.0.1应该是提供dns解析的docker内置的服务器。

用 192.168.3.102:8600去访问一下看这个提示是这样子的

zero123

@meitian 请问怎么解决的？我也遇到同样的问题

vapor

课程读者 7 声望

有解决的么

1年前评论

讨论应以学习和精进为目的。请勿发布不友善或者负能量的内容，与人为善，比聪明更重要！

帮助

kong网关无法连接consul的8600端口

- KONG_DNS_RESOLVER=127.0.0.1:8600

社区赞助商

关于 LearnKu

资源推荐

服务提供商

其他信息

kong网关无法连接consul的8600端口

- KONG_DNS_RESOLVER=127.0.0.1:8600

社区赞助商

关于 LearnKu

资源推荐

服务提供商

其他信息

请登录