C
Coder.com2mo ago
<_<

Building template is stuck queued

No builds for templates have been done for the past day or two but when I tried to update a template and build it is stuck queued with no progress
No description
35 Replies
Codercord
Codercord2mo ago
<#1332197314965671978>
Category
Help needed
Product
Coder (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
<_<
<_<OP2mo ago
ill check the server logs because i assume that will have something
Phorcys
Phorcys2mo ago
which way did you use to install Coder?
<_<
<_<OP2mo ago
i run it under docker, using a compose file
services:
coder:
container_name: coder
hostname: coder
image: ghcr.io/coder/coder:v2.18.3
restart: always
depends_on:
- postgres
env_file:
- .env
expose:
- "7080"
group_add:
- "999"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
services:
coder:
container_name: coder
hostname: coder
image: ghcr.io/coder/coder:v2.18.3
restart: always
depends_on:
- postgres
env_file:
- .env
expose:
- "7080"
group_add:
- "999"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
Phorcys
Phorcys2mo ago
please do!
<_<
<_<OP2mo ago
trying to find the most relevent logs because theres lots are there any keywords i should look for?
Phorcys
Phorcys2mo ago
look for "provisioner" but you can send the full log too
<_<
<_<OP2mo ago
<_<
<_<OP2mo ago
pretty sure this is all of it because the template version audit oh wait maybe its a visual bug? i think it did build
Phorcys
Phorcys2mo ago
could you send full logs? this doesn't really have any errors in it
<_<
<_<OP2mo ago
i clicked resources and now output is not clickable
No description
<_<
<_<OP2mo ago
and i just noticed success up here
No description
<_<
<_<OP2mo ago
could it be just visuals?
Phorcys
Phorcys2mo ago
yes, could be check under "versions" in your template's settings to see if a new version was pushed
<_<
<_<OP2mo ago
yep the output showing that is what threw me off because i didnt look at the top to see if it lets me publish
Phorcys
Phorcys2mo ago
pretty weird still, could you make a video showing the bug so I can report it to our engineers?
<_<
<_<OP2mo ago
let me see if it happens again hm so it queues for a little while
<_<
<_<OP2mo ago
because its still currently "enqueued"
No description
<_<
<_<OP2mo ago
after like a minute not sure why it would be going so slow and building for minutes usually its instant
<_<
<_<OP2mo ago
could be this? because im pretty sure it does build
No description
<_<
<_<OP2mo ago
yeah if i refresh it has built already
Phorcys
Phorcys2mo ago
yes, likely the issue
<_<
<_<OP2mo ago
i dont see any ws logs is that seperate?
Phorcys
Phorcys2mo ago
could you send a screenshot of the health page?
No description
Phorcys
Phorcys2mo ago
there's no logs, it just fails to connect
<_<
<_<OP2mo ago
No description
<_<
<_<OP2mo ago
weird
<_<
<_<OP2mo ago
No description
Phorcys
Phorcys2mo ago
are you using a reverse-proxy in front of Coder?
<_<
<_<OP2mo ago
yes nginx
worker_processes auto;

events {
worker_connections 1024;
multi_accept on;
}

http {
include mime.types;
default_type application/octet-stream;

log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';

access_log /var/log/nginx/access.log main;
error_log /var/log/nginx/error.log warn;

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
server_tokens off;

gzip on;
gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

server {
listen 80;
server_name something.com;

location / {
proxy_pass http://coder:7080;

proxy_pass_request_headers on;

proxy_http_version 1.1;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Accept-Encoding gzip;
}
}
}
worker_processes auto;

events {
worker_connections 1024;
multi_accept on;
}

http {
include mime.types;
default_type application/octet-stream;

log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';

access_log /var/log/nginx/access.log main;
error_log /var/log/nginx/error.log warn;

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
server_tokens off;

gzip on;
gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

server {
listen 80;
server_name something.com;

location / {
proxy_pass http://coder:7080;

proxy_pass_request_headers on;

proxy_http_version 1.1;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Accept-Encoding gzip;
}
}
}
i replaced the server name with a placeholder but this is how my config looks i checked nginx logs for /logs?follow=true&after=-1 and none of the logs show any issues all 101 status code
Atif
Atif2mo ago
This could be a Provisioner bug. Could you move this to a GitHub issue?
Phorcys
Phorcys2mo ago
(@<_<)
<_<
<_<OP2mo ago
my bad didnt see this what should i put in the issue?
Atif
Atif2mo ago
Your Coder version, template code and everything we can do to reproduce the behavior.
<_<
<_<OP2mo ago
GitHub
websocket connection fails sometimes when building template · Issue...
this causes the frontend to show as if it is still enqueued but if refreshed everything built fine my coder version is v2.18.3+a5a7326 here is a screenshot of health check: and here is the nginx co...

Did you find this page helpful?