diff --git a/doc/settings/ssl/ssl_troubleshooting.md b/doc/settings/ssl/ssl_troubleshooting.md index 27546a1524ba4bc4980c9c59a1325e8061441f5f_ZG9jL3NldHRpbmdzL3NzbC9zc2xfdHJvdWJsZXNob290aW5nLm1k..299616abd4ff4975c06adb0b1726bda206d75693_ZG9jL3NldHRpbmdzL3NzbC9zc2xfdHJvdWJsZXNob290aW5nLm1k 100644 --- a/doc/settings/ssl/ssl_troubleshooting.md +++ b/doc/settings/ssl/ssl_troubleshooting.md @@ -335,9 +335,7 @@ the certificate and key. Contact the provider of the SSL certificate for further support. -<!-- markdownlint-disable line-length --> - -## Using GitLab Runner with a GitLab instance configured with internal CA certificate or self-signed certificate +## Error: `certificate signed by unknown authority` Besides getting the errors mentioned in [Using an internal CA certificate with GitLab](ssl_troubleshooting.md#using-an-internal-ca-certificate-with-gitlab), @@ -353,8 +351,6 @@ Follow the details in [Self-signed certificates or custom Certification Authorities for GitLab Runner](https://docs.gitlab.com/runner/configuration/tls-self-signed.html). -<!-- markdownlint-enable line-length --> - ## Mirroring a remote GitLab repository that uses a self-signed SSL certificate When configuring a local GitLab instance to [mirror a repository](https://docs.gitlab.com/user/project/repository/mirror/) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 27546a1524ba4bc4980c9c59a1325e8061441f5f_ZG9jL3Ryb3VibGVzaG9vdGluZy5tZA==..299616abd4ff4975c06adb0b1726bda206d75693_ZG9jL3Ryb3VibGVzaG9vdGluZy5tZA== 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -231,7 +231,7 @@ your security settings at `/etc/security/access.conf` and make sure the Git user is not blocked. -## PostgreSQL error `FATAL: could not create shared memory segment: Cannot allocate memory` +## Error: `FATAL: could not create shared memory segment: Cannot allocate memory` The packaged PostgreSQL instance tries to allocate 25% of total memory as shared memory. On some Linux (virtual) servers, there is less shared memory @@ -254,9 +254,7 @@ Run `sudo gitlab-ctl reconfigure` for the change to take effect. -<!-- markdownlint-disable line-length --> - -## PostgreSQL error `FATAL: could not open shared memory segment "/PostgreSQL.XXXXXXXXXX": Permission denied` +## Error: `FATAL: could not open shared memory segment "/PostgreSQL.XXXXXXXXXX": Permission denied` By default, PostgreSQL tries to detect the shared memory type to use. If you don't have shared memory enabled, you might see this error in `/var/log/gitlab/postgresql/current`. @@ -269,9 +267,7 @@ Run `sudo gitlab-ctl reconfigure` for the change to take effect. -<!-- markdownlint-enable line-length --> - -## PostgreSQL error `FATAL: remaining connection slots are reserved for non-replication superuser connections` +## Error: `FATAL: remaining connection slots are reserved for non-replication superuser connections` PostgreSQL has a setting for the maximum number of the concurrent connections to the database server. If you see this error, it means that your GitLab instance is trying to exceed