TeamCity Support | JetBrains

Erik Baan

Total activity 21
Last activity January 11, 2026 07:08
Member since August 22, 2022 07:51
Following 0 users
Followed by 0 users
Votes 0
Subscriptions 4

Created January 11, 2026 07:08

We have downgraded to the previous version (and restored from a recent backup as the current state was not ‘downgradable’), and our builds are running properly again.So it really seems to be an iss...
- 0 votes
Created January 09, 2026 01:22

Hi Tom,Thanks for investigating and the clear explanation.It does sound like a problem with the latest TeamCity server and/or agent version.If a build step suddenly is waiting hours for ‘artifact p...
- 0 votes
Created January 08, 2026 15:51

Hi Tom,Thanks. Is there any problem visible in the thread dump that I shared?
- 0 votes
Created January 08, 2026 08:12

The agent thread dump file can be found here:Upload id: 2026_01_08_LrLYwmfUPLDV3KHkhyiYCT (file: scratch_526.txt)
- 0 votes
Created January 08, 2026 08:02

Hi Tom,Thanks for your answer.I've tried to enable DEBUG level for the agent by editing both teamcity-agent-log4j2.xml and buildAgent.properties , but I'm still only getting INFO level logs , nothi...
- 0 votes
Created January 07, 2026 06:15

The build step is hanging for between 2 and 5 hours, and is continuing without error after hanging (see bump from 03:47 to 06:04 in this example):[2026-01-07 03:47:35,272] INFO - ildStages.Runner...
- 0 votes
Created September 05, 2024 10:17

Apparently, the problems are still active:- I cannot SSH into agent containers that are runningdocker exec -it teamcity-agent3-1 bashNotFound: task c29e722a27aff89d0f8a1807683a90cd9be00ab4ea621aa30...
- 0 votes
Created September 03, 2024 10:16

Looks like the problem was specifically in the volumes that were bound to /var/lib/docker, and needed to be purged / recreated. Perhaps this was related to a docker update on the host system.Fully ...
- 0 votes
Created September 03, 2024 08:42

Still don't have a clue how to solve this with docker compose. Adding user: 0 does not solve the problem.Perhaps something changed regarding privileged with recent docker compose changes.
- 0 votes
Created September 03, 2024 07:59

So the good news is, starting another agent with this command is working properly:docker run -e SERVER_URL="http://server:8111" \ -u 0 \ -v /home/webdev/services/teamcity/agent4_conf:/data/t...
- 0 votes