Downloading the system report can cause the instance to crash or restart on Docker or Kubernetes

[akirayamamoto]

Team

• I've assigned a team label to this issue

Severity

Affects Octopus Cloud and customers running Octopus server on Docker or Kubernetes

Version

From 2019.5.12

Latest Version

I could reproduce the problem in the latest build

What happened?

When running Octopus server on Docker or Kubernetes downloading the system report can cause the instance to crash or restart.

Octopus server might receive a SIGABRT message which will bubble up as exit code 139 to Docker/Kubernetes when we collect the stack traces of the running threads.

Reproduction

Download the system report until the server crashes or restarts. It happens somewhat often but not every time.

Error and Stacktrace

No response

More Information

No response

Workaround

Avoid downloading the system report. If needed then do it during a maintenance window.

[octoreleasebot]

Release Note: Removed stack traces from the system report to fix an issue where the instance could crash when downloading such report.

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2022.3	2022.3.6878
2022.4+	all releases