search

OctopusDeploy / Issues

| Public | Bug reports and known issues for Octopus Deploy and all related tools
https://octopus.com
161 stars 20 forks source link

`Exception appending to log with correlationId` in the Auto-deploy log #6748

Open droyad opened 3 years ago

droyad commented 3 years ago

The following error message is shown in the server log:

Exception appending to log with correlationId

This occurs if the background process that handles machine auto-deploy triggers swaps to another node within on minute of the previous run.

Cause

A node keeps log files open for 1 minute as performance optimisation when dealing with high latency storage (e.g. network shares). This is usually ok since only one node ever runs a deployment. However this is not the case for auto-deploy background detection process as it can switch nodes.

Affected Version

Octopus Server 2018.7.5 and later, caused by this change.

Impact

Once all nodes are running, this message should be rare as the process will tend to run on the same node.

Some entries in the "recurring scheduled deployments" logs may be lost. These are diagnostic messages only.

The only performance impact is that the background loop that creates the Process recurring scheduled triggers server task is delayed. It does not affect deployments.

droyad commented 3 years ago

Related to #6522 Probably fixed in 2020.6.0 by https://github.com/OctopusDeploy/OctopusDeploy/pull/7536

droyad commented 1 year ago

Some entries in the "recurring scheduled deployments" logs may be lost. These are diagnostic messages only.

The only performance impact is that the background loop that creates the Process recurring scheduled triggers server task is delayed. It does not affect deployments.

paraicoceallaigh commented 1 year ago

Related ticket: [private link] https://octopus.zendesk.com/agent/tickets/113435