You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metrics server starts when the container starts. I can visit the metrics endpoint and see the the data. So when a tunnel is started and the metrics server can't run because there is already a metrics server running on that port. The tunnel fails to start. Ducked the error without finding much for help.
The docker starts without issues. Going to localhost:49312/metrics shows
# HELP build_info Build and version information
# TYPE build_info gauge
build_info{goversion="go1.17.7",revision="",type="",version="2022.2.1"} 1
# HELP cloudflared_tunnel_active_streams Number of active streams created by all muxers.
# TYPE cloudflared_tunnel_active_streams gauge
cloudflared_tunnel_active_streams 0
# HELP cloudflared_tunnel_concurrent_requests_per_tunnel Concurrent requests proxied through each tunnel
# TYPE cloudflared_tunnel_concurrent_requests_per_tunnel gauge
cloudflared_tunnel_concurrent_requests_per_tunnel 0
# HELP cloudflared_tunnel_ha_connections Number of active ha connections
# TYPE cloudflared_tunnel_ha_connections gauge
cloudflared_tunnel_ha_connections 0
# HELP cloudflared_tunnel_request_errors Count of error proxying to origin
# TYPE cloudflared_tunnel_request_errors counter
[Redacted for brevity]
Within the docker shell I start the tunnel using...
cloudflared tunnel --config /home/cloudflared/.cloudflared/config.yml run cloud
and it fails due to the metrics address already in use.
2022-02-21T06:02:26Z INF Starting tunnel tunnelID=[REDACTED]
2022-02-21T06:02:26Z INF Version 2022.2.1
2022-02-21T06:02:26Z INF GOOS: linux, GOVersion: go1.17.7, GoArch: amd64
2022-02-21T06:02:26Z INF Settings: map[config:/home/cloudflared/.cloudflared/config.yml cred-file:/home/cloudflared/.cloudflared/[REDACTED].json credentials-file:/home/cloudflared/.cloudflared/REDACTED.json]
2022-02-21T06:02:26Z INF Environmental variables map[TUNNEL_DNS_ADDRESS:0.0.0.0 TUNNEL_DNS_PORT:5053 TUNNEL_DNS_UPSTREAM:https://u6ko3ti7wp.cloudflare-gateway.com/dns-query TUNNEL_METRICS:0.0.0.0:49312 TUNNEL_ORIGIN_CERT:/home/cloudflared/.cloudflared/cert.pem]
2022-02-21T06:02:26Z INF cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a service: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/run-as-service
2022-02-21T06:02:26Z INF Generated Connector ID: [REDACTED]
2022-02-21T06:02:26Z INF Initial protocol http2
2022-02-21T06:02:26Z ERR Error opening metrics server listener error="listen tcp 0.0.0.0:49312: bind: address already in use"
Error opening metrics server listener: listen tcp 0.0.0.0:49312: bind: address already in use
Expected behaviour
The metrics server should only need to start once. Either when the docker comes up or when the tunnel is created, but not at both times.
Configuration
Docker version (type docker --version) : 20.10.11, build dea9396
Docker compose version if applicable (type docker-compose --version) : 1.25.0, build unknown
Behaviour
Metrics server starts when the container starts. I can visit the metrics endpoint and see the the data. So when a tunnel is started and the metrics server can't run because there is already a metrics server running on that port. The tunnel fails to start. Ducked the error without finding much for help.
Steps to reproduce this issue
This is my docker file.
The docker starts without issues. Going to localhost:49312/metrics shows
Within the docker shell I start the tunnel using...
and it fails due to the metrics address already in use.
Expected behaviour
The metrics server should only need to start once. Either when the docker comes up or when the tunnel is created, but not at both times.
Configuration
docker --version
) : 20.10.11, build dea9396docker-compose --version
) : 1.25.0, build unknownuname -a
) : Linux truenas-scale.local 5.10.81+truenas x86_64 GNU/Linuxdocker-compose.yml
,.env
, ...Docker info
The text was updated successfully, but these errors were encountered: