I can see the teamcity agents in my teamcity UI and when I check the teamcity-agent.log. when i see the server logs it says WARN - jetbrains.buildServer.AGENT - Agent "macagent2" {id=3} tries to register while it is already registered.

I am using nginx reverse proxy and build agents are on premise and server running as container on gcp. I can see the agents on UI and they look okay. When I see the agent logs and server logs they are miss leading actually as mentioned above. 

 

Teamcity version 2017.1.3

 

nginx.conf: |
server {
listen 80;
server_name teamcity.example.com;
error_log /var/log/nginx/error.log;
proxy_intercept_errors on;
error_page 401 403 404 /404.html;
location / {
proxy_set_header Host $host;
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;
client_max_body_size 100M;
proxy_pass http://127.0.0.1:8111;
proxy_read_timeout 300;
proxy_redirect http://127.0.0.1:8111 https://teamcity.example.com;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_ignore_client_abort on;
keepalive_timeout 0;
}
}
map $http_upgrade $connection_upgrade {
default upgrade;
'' '';
}
1 comment
Comment actions Permalink

Hello,

Such log lines regarding agent re-registration usually do not designate a problem by themselves. Do you observe any problems caused by this such as dropped jobs, hanging builds, etc? If it is the case, please share with us the following logs via our secure upload service (https://uploads.jetbrains.com/), and send the upload ID back to us so that we can check what is going on:

-teamcity-server.log;

-teamcity-agent.log.

Thank you,

Guilherme

0

Please sign in to leave a comment.