Strange behavior during server-agent synchronization

Continua CI Bugs
1

Dear Sir/Madam

We have yet encountered another problem which is a little bit puzzling to us. We hope that you can help us to understand and resolve the problem.

We encountered a strange behavior related to the server-agent synchronization.

As described in an earlier bug-report. We have a setup with several agents on different physical machines. Therefore build stages of a configuration can run on different machines during a build sequence. The exact sequence is runtime dependent.

Every stage of a configuration build starts with a server -> agent synchronization and ends with an agent -> server synchronization.

The strange behavior we have encountered looks like this: If it is the first time during a configuration build that the server synchronizes with a particular agent it happens very fast (30 seconds) however if there was already a synchronization in a previous stage between the server and the same agent the synchronization takes much longer (30 minutes).
To us it seems that there are some issues with copying files if they already exist on the agent from a previous stage synchronization. So probably something stalls and times out during the synchronization.

Can you please help us to resolve this issue?

Best regards,

2

Hi Marcel,

We’re not seeing this issue on our servers so we’ll need some more information to understand what it going on in your environment and to allow us to reproduce the issue. 

Can you send us a build log and the relevant sections of the timeline? This will show us where the bottle neck is occurring. Ensure that “Log repository files copied” and “Log workspace files copied” are ticked in the stage options for each stage, before running the build to generate the build log. 

Can you also send us details of the repository and workspace rules in the stage options for each relevant stage? You can simply download the diagnostics log which includes this information from the Event Log in the Administration section. Send this to support@finalbuilder.com rather than posting here publicly. 

The quickest way for us to diagnose this type of problem is using the debug logs. If you can enable debug logging for both the server and agent services. Then, after restarting the service and rerunning the build to reproduce the issue, send us the generated debug logs, we should be able to rapidly get to the bottom of the issue.