Roberto,

If would be easier if you can attach full build log as there might be relevant messages.

It seems that the duplicates finder fails for some reason. One of possible reasons is JVM memory issues: either too small that is fails with OutOfMemory (so need to increase -Xmx), or large for the JVM to initiazlize on the machine.

Roberto,

Pleae check that the processes launched by the TeamCity agent can connect to the agent's port (http://localhost:9090 in the case from the logs). Seems like this is not the case for the build, while this is a necessary pre-requisite for the due functionaing of TeamCity agent logic.

Roberto,

Sone runners do work. But not the others.

Can you please try Ant build runner?

Roberto,

Idea duplicates and inspectinos runned will not works until the process launched fromt he agent can connect to the agent's port (http://localhost:9090 in the case from the logs).

Maven runner does not need the ability.

I asked you to try Ant as it also requires the ability to connect to the port and would expose the same issue.

Robert,

> How could he not have access to port 9090?

I am not a Linux administratino guru, so won't help you much here.

I'd start by opening the address ( http://localhost:9090 , but may vary, can be seen in the command line in the build log) on the agent machine in the browser (message "Method GET not implemented" means the agent is accessible). You might need ot run theat on behalf of the same user running TeamCity agent.

If it works, I'd try to run the agent from the same user's console (agnet.sh start).

Next, I'd try to connect to the port from a test script run as a build in TeamCity.