Add troubleshooting for SSL SYSCALL error observed when using external PostgreSQL
What does this MR do and why?
This MR updates the Configure GitLab using an external PostgreSQL service documentation to introduce a troubleshooting section that provides guidance on how to resolve this error that the GitLab Support team has noticed recently:
pg_dump: error: Error message from server: SSL SYSCALL error: EOF detectedThis error sometimes happens when running gitlab-backup create. As described in the #364763 (closed) issue, when we see SSL SYSCALL error: EOF detected in the GitLab Rails logs, we see an indication that PostgreSQL experiences a segmentation fault.
- This error occurs when an instance is using an external PostgreSQL service.
- Upgrading to a version of PostgreSQL that at least meets the minimum PostgreSQL requirements resolves this error.
This error can occur after the GitLab instance has been using the impacted version of PostgreSQL for some period of time.
We previously updated the docs to make 12.10 the minimum PostgreSQL version in !84183 (merged) when we first encountered this issue.
🎫 Tickets
The GitLab Support team has used this approach to resolve multiple tickets. These tickets are available to GitLab team members with access to Zendesk:
| Ticket | When SSL SYSCALL error: EOF detected
|
RDS? | Resolution | GitLab version |
|---|---|---|---|---|
| 279581 | unclear | Y | Upgrade to 13.3 | unclear |
| 286985 | Running ANALYZE
|
Y | Upgrade to 12.10 | ~14.8 |
| 292436 | Observed in the logs | Y | Upgrade to 13.3 | ~14.9 |
| 293012 | gitlab-backup create |
Y | Upgrade to 12.10 | ~14.10 |
| 298774 | gitlab-rake gitlab:doctor:secrets |
RDS | Upgrade to 12.10 | ~14.9 |
| 299181 | gitlab-backup create |
Y | Upgrade to 12.11 (we believe) | ~14.10 |
🌐 Links
See the External PostgreSQL 12 and 13 servers should be upgraded to the latest minor version blog post.
The gitlab-org/gitlab#364763 issue discusses this behavior further.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.