[solved] Builds stuck in pending state for drone:1.1.0

I have deployed drone on docker swarm with following configuration.

version: ‘3.5’

networks:
drone:
driver: overlay
attachable: true
traefik_public:
external: true
driver: overlay

volumes:
drone-data:
external: true

services:

drone-server:
image: “drone/drone:1.1.0”
logging:
driver: json-file
options:
max-size: “10m”
max-file: “3”
networks:
- traefik_public
- drone
environment:
- DRONE_SERVER_HOST=drone.domain.in
- DRONE_SERVER_PROTO=https
- DRONE_TLS_AUTOCERT=false
- DRONE_AGENTS_ENABLED=true
- DRONE_BITBUCKET_CLIENT_ID=xxxxx
- DRONE_BITBUCKET_CLIENT_SECRET=xxxxxx
- DRONE_RPC_SECRET=d859a7aa9453f47ff567939024b0f7c2
- DRONE_DATABASE_DRIVER=mysql
- DRONE_DATABASE_DATASOURCE=xxxx:xxxxx@tcp(xx.xx.xx.xx:3306)/drone?parseTime=true
- DRONE_LOGS_DEBUG=true
- DRONE_USER_CREATE=cccccc:octocat,machine:false,admin:true,token:55f24eb3d61ef6ac5e83d550178638dc
volumes:
- drone-data:/var/lib/drone/
deploy:
placement:
constraints:
- node.role==manager
replicas: 1
labels:
- “traefik.backend=drone-server”
- “traefik.frontend.rule=Host:drone.domain.in”
- “traefik.frontend.entryPoints=http”
- “traefik.port=80”
- “traefik.docker.network=traefik_public”
- “traefik.enable=true”
endpoint_mode: dnsrr
mode: replicated

drone-agent:
image: “drone/agent:1.1.0”
logging:
driver: json-file
options:
max-size: “10m”
max-file: “3”
networks:
- drone
environment:
- DRONE_PLUGIN_PULL=true
- DRONE_LOGS_DEBUG=true
- DRONE_RPC_SERVER=http://drone-server
- DRONE_RPC_SECRET=d859a7aa9453f47ff567939024b0f7c2
- DRONE_RUNNER_CAPACITY=3
depends_on:
- drone-server
volumes:
- /var/run/docker.sock:/var/run/docker.sock
deploy:
replicas: 3
mode: replicated

Agent Logs :

{“arch”:“amd64”,“level”:“debug”,“machine”:“002aa291582e”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-28T19:43:13Z”}
{“arch”:“amd64”,“level”:“debug”,“machine”:“002aa291582e”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-28T19:43:14Z”}

Server Logs:

{“level”:“info”,“msg”:“main: internal scheduler enabled”,“time”:“2019-04-28T19:42:04Z”}
{“build.limit”:15000,“expires”:“0001-01-01T00:00:00Z”,“kind”:“trial”,“level”:“debug”,“msg”:“main: license loaded”,“repo.limit”:0,“time”:“2019-04-28T19:42:04Z”,“user.limit”:0}
{“acme”:false,“host”:“drone.domain.in”,“level”:“info”,“msg”:“starting the http server”,“port”:":80",“proto”:“https”,“time”:“2019-04-28T19:42:04Z”,“url”:“https://drone.domain.in”}
{“interval”:“30m0s”,“level”:“info”,“msg”:“starting the cron scheduler”,“time”:“2019-04-28T19:42:04Z”}

The most common root cause for builds stuck in pending is agent-to-server connectivity issues. You can use the following guide to triage connectivity issues, which also describes the information that is required to provide support: Builds are Stuck in Pending Status.

However, since you are using Docker Compose and you are presumably installing everything on the same server, I should point out that you do not need to use agents at all. Instead you can configure the server to run without agents, in single-machine mode, as described in the docs at https://docs.drone.io/installation/bitbucket-cloud/single-machine/

I am using docker stack, as i have a docker swarm cluster of 12 machines. So my Drone server is running on one of the master and I allocated 3 worker nodes for drone agent and distributed in my cluster. I debugged it by attaching a container on same network(overlay) as drone system is running , i am able to ping as well as telnet to port 80 of my drone server using service name. I don’t know why agent are not able to pick build as per agent logs they are polling the server queue for getting build instructions.

{“arch”:“amd64”,“level”:“debug”,“machine”:“002aa291582e”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-28T19:43:13Z”}

This is not a single machine deployment. Indeed i am using docker-compose but with deploy instruction which work in swarm cluster. Earlier i was using version of drone 0.8.0 . Which is working flawlessly. But as i upgrade to 1.1.0 it ran into problem. My whole repo build pipeline. Now I am stuck with upgrade.

The link I mentioned above describes how to debug, and the information requires to assist. See Builds are Stuck in Pending Status

Hi bradrydzewski,

I have gone through your suggested link and enabled trace logging on both server and agents. And find that server is miss reconfigured somehow. I am running drone setup in docker swarm cluster. I have a url configured to send request to drone server in following fashion

“web-url —> nginx gateway (only https enabled) ----> traefik gateway (swarm cluster gateway —> drone server container”.

Let say i have a url drone.domain.com. So i configured

  • DRONE_SERVER_HOST=https://drone.domain.in (i was hopping this would be host url where drone server is listening from web browser). As i am running this setup in container, so do i have to provide container hostname (which i can’t as it is dynamic ). Please clarify it
  • DRONE_SERVER_PROTO=http

server configuration is as follow:

environment:
- DRONE_SERVER_HOST=drone.domain.in
- DRONE_SERVER_PROTO=https
- DRONE_TLS_AUTOCERT=false
- DRONE_AGENTS_ENABLED=true
- DRONE_BITBUCKET_CLIENT_ID=xxxxxxxxxxxxxxxxxxxx
- DRONE_BITBUCKET_CLIENT_SECRET=xxxxxxxxxxxxxxxxxxx
- DRONE_RPC_SECRET=yyyyyyyyyyyyyyyyyyyyyyyy
- DRONE_DATABASE_DRIVER=mysql
- DRONE_DATABASE_DATASOURCE=drone:password@tcp(xxx.xxx.xxx.xxx:3306)/drone
- DRONE_LOGS_TRACE=true
- DRONE_USER_CREATE=goelprateek:octocat,machine:false,admin:true,token:55f24eb3d61ef6ac5e83d550178638dc
- HTTPS_PROXY=http://xxx.xx.xxx.xxx:3128
- HTTP_PROXY=http://xxx.xx.xxx.xxx:3128

I hereby attaching logs from server

drone_drone-server.1.04odf5a3x5es@node10.docker.com | license: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | authn:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | token: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | agent:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | enabled: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cron:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | disabled: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | interval: 30m0s
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cloning:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | alwaysauth: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | username: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | password: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | image: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | pull: IfNotExists
drone_drone-server.1.04odf5a3x5es@node10.docker.com | database:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | driver: mysql
drone_drone-server.1.04odf5a3x5es@node10.docker.com | datasource: drone:password@tcp(xxx.xx.xx.xx:3306)/drone?parseTime=true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | datadog:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | enabled: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: https://stats.drone.ci/api/v1/series
drone_drone-server.1.04odf5a3x5es@node10.docker.com | token: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | docker:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | config: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | http:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | allowedhosts: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | hostsproxyheaders: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | sslredirect: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | ssltemporaryredirect: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | sslhost: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | sslproxyheaders: {}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | stsseconds: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | stsincludesubdomains: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | stspreload: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | forcestsheader: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | browserxssfilter: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | framedeny: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | contenttypenosniff: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | contentsecuritypolicy: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | referrerpolicy: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | jsonnet:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | enabled: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | logging:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | trace: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | color: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | pretty: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | text: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | proxy:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | addr: https://drone.domain.in
drone_drone-server.1.04odf5a3x5es@node10.docker.com | host: drone.domain.in
drone_drone-server.1.04odf5a3x5es@node10.docker.com | proto: https
drone_drone-server.1.04odf5a3x5es@node10.docker.com | registration:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | closed: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | registries:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | password: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | repository:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | filter: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | runner:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | local: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | image: drone/controller:1.0.0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | platform: linux/amd64
drone_drone-server.1.04odf5a3x5es@node10.docker.com | os: linux
drone_drone-server.1.04odf5a3x5es@node10.docker.com | arch: amd64
drone_drone-server.1.04odf5a3x5es@node10.docker.com | kernel: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | variant: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | machine: 0c1d8c30c01f
drone_drone-server.1.04odf5a3x5es@node10.docker.com | capacity: 2
drone_drone-server.1.04odf5a3x5es@node10.docker.com | labels: {}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | volumes: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | networks: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | devices: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | privileged: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | environ: {}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | limits:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | memswaplimit: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | memlimit: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | shmsize: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cpuquota: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cpushares: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cpuset: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | nomad:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | enabled: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | datacenters:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - dc1
drone_drone-server.1.04odf5a3x5es@node10.docker.com | namespace: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | region: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | prefix: drone-job-
drone_drone-server.1.04odf5a3x5es@node10.docker.com | image: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | imagepull: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | memory: 1024
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cpu: 500
drone_drone-server.1.04odf5a3x5es@node10.docker.com | kube:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | enabled: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | namespace: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | path: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | url: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | ttl: 300
drone_drone-server.1.04odf5a3x5es@node10.docker.com | serviceaccountname: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | pullpolicy: Always
drone_drone-server.1.04odf5a3x5es@node10.docker.com | image: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | rpc:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secret: d859a7aa9453f47ff567939024b0f7c2
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | host: drone.domain.in
drone_drone-server.1.04odf5a3x5es@node10.docker.com | proto: https
drone_drone-server.1.04odf5a3x5es@node10.docker.com | s3:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | bucket: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | prefix: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | pathstyle: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secrets:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | password: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | addr: https://drone.domain.in
drone_drone-server.1.04odf5a3x5es@node10.docker.com | host: drone.domain.in
drone_drone-server.1.04odf5a3x5es@node10.docker.com | port: :80
drone_drone-server.1.04odf5a3x5es@node10.docker.com | proto: https
drone_drone-server.1.04odf5a3x5es@node10.docker.com | acme: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | cert: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | key: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | session:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | timeout: 720h0m0s
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secret: eRrbTLF2Gn4cz8zyadJrITWTFkbXBa41
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secure: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | status:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | disabled: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | name: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | users:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | create:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | username: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | machine: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | admin: true
drone_drone-server.1.04odf5a3x5es@node10.docker.com | token: 55f24eb3d61ef6ac5e83d550178638dc
drone_drone-server.1.04odf5a3x5es@node10.docker.com | filter: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | minage: 0s
drone_drone-server.1.04odf5a3x5es@node10.docker.com | webhook:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: []
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | yaml:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | endpoint: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | secret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | bitbucket:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientid: eFvdcZ7ZRtSRZHf9Le
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientsecret: xCKaqbZGqCVxyZ2B3m6fGPB676D8zfQQ
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | gitea:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientid: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientsecret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | scope:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - repo
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - repo:status
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - user:email
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - read:org
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | github:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: https://github.com
drone_drone-server.1.04odf5a3x5es@node10.docker.com | apiserver: https://api.github.com
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientid: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientsecret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | scope:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - repo
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - repo:status
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - user:email
drone_drone-server.1.04odf5a3x5es@node10.docker.com | - read:org
drone_drone-server.1.04odf5a3x5es@node10.docker.com | ratelimit: 0
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | gitlab:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: https://gitlab.com
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientid: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | clientsecret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | gogs:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | stash:
drone_drone-server.1.04odf5a3x5es@node10.docker.com | server: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | consumerkey: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | consumersecret: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | privatekey: “”
drone_drone-server.1.04odf5a3x5es@node10.docker.com | skipverify: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com | debug: false
drone_drone-server.1.04odf5a3x5es@node10.docker.com |
drone_drone-server.1.04odf5a3x5es@node10.docker.com | {“level”:“info”,“msg”:“main: internal scheduler enabled”,“time”:“2019-04-29T04:45:42Z”}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | {“build.limit”:15000,“expires”:“0001-01-01T00:00:00Z”,“kind”:“trial”,“level”:“debug”,“msg”:“main: license loaded”,“repo.limit”:0,“time”:“2019-04-29T04:45:42Z”,“user.limit”:0}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | {“interval”:“30m0s”,“level”:“info”,“msg”:“starting the cron scheduler”,“time”:“2019-04-29T04:45:42Z”}
drone_drone-server.1.04odf5a3x5es@node10.docker.com | {“acme”:false,“host”:“drone.serviceurl.in”,“level”:“info”,“msg”:“starting the http server”,“port”:":80",“proto”:“https”,“time”:“2019-04-29T04:45:42Z”,“url”:“https://drone.domain.in”}

Please confirm as rpc is taking host as drone.domain.in and proto as https with port 80. which i think is wrong.

Drone Agent Configuration:

  • DRONE_PLUGIN_PULL=true
  • DRONE_LOGS_TRACE=true
  • DRONE_RPC_SERVER=http://drone-server
  • DRONE_RPC_SECRET=d859a7aa9453f47ff567939024b0f7c2
  • DRONE_RUNNER_CAPACITY=3
  • HTTP_PROXY=http://xxx.xx.xxx.xxx:3128
  • HTTPS_PROXY=http://xxx.xx.xxx.xxx:3128

Drone Agent Logs:

{“arch”:“amd64”,“level”:“debug”,“machine”:“02dc064a851a”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-29T05:26:00Z”}
[DEBUG] POST http://drone-server/rpc/v1/request
[ERR] POST http://drone-server/rpc/v1/request request failed: Post http://drone-server/rpc/v1/request: context deadline exceeded
{“arch”:“amd64”,“level”:“debug”,“machine”:“02dc064a851a”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-29T05:26:00Z”}
[DEBUG] POST http://drone-server/rpc/v1/request
[ERR] POST http://drone-server/rpc/v1/request request failed: Post http://drone-server/rpc/v1/request: context deadline exceeded
{“arch”:“amd64”,“level”:“debug”,“machine”:“02dc064a851a”,“msg”:“runner: polling queue”,“os”:“linux”,“time”:“2019-04-29T05:26:00Z”}
[DEBUG] POST http://drone-server/rpc/v1/request
[DEBUG] POST http://drone-server/rpc/v1/request (status: 503): retrying in 1s (30 left)

I see in your logs a 503 service unavailable error. This error code does not come from Drone. This status code is not used anywhere in the Drone source code. The only possible error codes that Drone will send are 400, 401, 404, 409, 500 and 524 which can be audited and verified in this source file.

[DEBUG] POST http://drone-server/rpc/v1/request (status: 503): retrying in 1s (30 left)

This would imply the request never even makes it to the Drone server. If the connection were successful you would see an entry in the server logs for manager: request queue item. Perhaps there is some intermediate networking software that is intercepting the request, and returning the 503? Either way, it is clear the request is not making it to Drone.

Hi bradrydzewski,

Thanks fore replying, I have described my setup in above reply. Can u please go through that. And please clarify DRONE_SERVER_HOST is it container hostname or callback url configured in bitbucket OAuth.

DRONE_SERVER_HOST is the public hostname, e.g. DRONE_SERVER_HOST=company.drone.io. If this were set incorrectly you would not be able to properly configure webhooks. Please note that this value does not have any bearing on the agent’s ability to connect with the server.

Maybe the problem is that you setup HTTP_PROXY variables which is intercepting and routing agent-to-server requests through the proxy? Perhaps you need to add the drone server address to NO_PROXY?

Either way the trace logs you provided make it clear that the http request to http://drone-server/rpc/v1/request is being intercepted by something else that is returning a 503. This is where I recommend you focus your debugging efforts.

For a time being i removed my http_proxy , now no request forward to proxy, i am using overlay network of docker swarm, Which mean it drone-agent is able to communicate drone-server using its service name. that’s what i assigned using

  • DRONE_RPC_SERVER=http://drone-server

I am getting status 524 . This means that drone-agent not able to contact drone-server.

Earlier I have same setup for drone:0.8.0 and it was running without any problem.

Hi bradrydzewski,

Thanks for you valuable support. There was problem with proxy settings only, agent is hitting proxy server instead of overlay. now builds are picked up as soon as request from webhook.

Just want to confirm about drone-server environment DRONE_ESCALATE which i used in version 0.8.0 is it deprecated , as i haven’t found any documentation for this in version 1.1.0