output.log

Answered

This log file is always growing:
/opt/buildagent/logs/output.log
All other log file rotations are configured in /opt/buildagent/conf/teamcity-agent-log4j.xml, but this one isn't. It comes from the script ./bin/agent.sh.
is there a way, we can use logrotate.

8 comments
Comment actions Permalink

Hi,

Output.log file contains launcher output and it should not be large. Could you please attach your output.log file, we will analyze it?

0
Comment actions Permalink

Hello ,

would it be possible to send this log in an email.?

Regards,

Ron Barrett

0
Comment actions Permalink

Hi,

Yes, please send it to teamcity-feedback@jetbrains.com with a link to this thread.

0
Comment actions Permalink

You've sent teamcity-agent.log instead of output.log file. When teamcity-agent.log reaches 10MB size, old logs are put in file with postfix .N, so you can delete these old files if they are not needed.

0
Comment actions Permalink

Hi,

Sorry for delay. There is nothing incorrect in your output.log file. Lots of messages are generated when server is down and agent is trying to connect to it.
We are implementing new version of agent launcher now, its logs will be splitted in the same way as agent logs.
The solution for now is to restart agent or to delete output.log file manually.

0
Comment actions Permalink

Bump on this. The launcher pipes all output of the build agent to output.log, and does not rotate it. output.log contains everything that teamcity-agent.log contains, seemingly, so it grows quite quickly and without bound.

How do I resolve the issue?

1
Comment actions Permalink

Hi Jordan,

At the moment the file is not limited in size. We have the related request https://youtrack.jetbrains.com/issue/TW-4752, please vote for it. 

As current workaround, you can delete the file manually.

1
Comment actions Permalink

I decided to modify the build agent start script to pipe the output to /dev/null instead as I don't think I have a use for it. Thanks!

0

Please sign in to leave a comment.