Timeout while deploying recipe #2

New Issue

2023-01-19T10:17:17Z

aadil commented

2023-01-19 10:17:17 +00:00

I tried deploying this recipe on two servers, they timed out with this error:

~ took 16s 
❯ abra app deploy focalboard.aadils.computer
WARN[0005] no versions detected, using latest commit    
WARN[0005] no published release discovered for focalboard 
+-----------------+------------+-------------+----------------------------+----------+
|     SERVER      |   RECIPE   |   CONFIG    |           DOMAIN           | VERSION  |
+-----------------+------------+-------------+----------------------------+----------+
| aadils.computer | focalboard | compose.yml | focalboard.aadils.computer | b3857dbc |
+-----------------+------------+-------------+----------------------------+----------+
? continue with deployment? Yes
FATA[0017] lookup focalboard.aadils.computer on 127.0.0.53:53: read udp 192.168.18.109:45856->5.1.66.255:53: i/o timeout

I tried deploying this recipe on two servers, they timed out with this error: ``` ~ took 16s ❯ abra app deploy focalboard.aadils.computer WARN[0005] no versions detected, using latest commit WARN[0005] no published release discovered for focalboard +-----------------+------------+-------------+----------------------------+----------+ | SERVER | RECIPE | CONFIG | DOMAIN | VERSION | +-----------------+------------+-------------+----------------------------+----------+ | aadils.computer | focalboard | compose.yml | focalboard.aadils.computer | b3857dbc | +-----------------+------------+-------------+----------------------------+----------+ ? continue with deployment? Yes FATA[0017] lookup focalboard.aadils.computer on 127.0.0.53:53: read udp 192.168.18.109:45856->5.1.66.255:53: i/o timeout ```

decentral1se commented

2023-01-19 10:52:52 +00:00

Seen it happen a few times, did it still deploy? Not sure exactly how I solved this before. Some of these errors are often v obscure and directly threaded back from the docker daemon but not all fatal to the deployment.

aadil commented

2023-01-19 10:54:24 +00:00

Nope, didn't deploy. I ran abra app ps --watch and it said the app isn't running.

Nope, didn't deploy. I ran `abra app ps --watch` and it said the app isn't running.

decentral1se commented

2023-01-19 11:00:56 +00:00

Is this happening every time you try to deploy?

https://github.com/docker-archive/classicswarm/issues/1185 seems to suggest that this is the connection to the swarm timing out somehow in the middle of the request and then the internals don't init a retry? Hard to tell if this is related here but seems like. You could poll the daemon logs (search up online how, journalctl outta do it?) while running the deployment and see if you see a timeout on that side?

Is this happening every time you try to deploy? https://github.com/docker-archive/classicswarm/issues/1185 seems to suggest that this is the connection to the swarm timing out somehow in the middle of the request and then the internals don't init a retry? Hard to tell if this is related here but seems like. You could poll the daemon logs (search up online how, journalctl outta do it?) while running the deployment and see if you see a timeout on that side?

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/focalboard#2