Skip to content
Snippets Groups Projects
Commit 5feb9a44ccba authored by Omar Qunsul's avatar Omar Qunsul
Browse files

Add docs for troubleshooting connection problems due to two connections

Addressing: https://gitlab.com/gitlab-org/gitlab/-/issues/387905

Changelog: other
parent 313dbfc14e4e
2 merge requests!102heptapod#1237: making 0.38 the new oldstable,!90Merged upstream 15.9.0+ce.0 into heptapod branch
......@@ -248,6 +248,30 @@
Run `sudo gitlab-ctl reconfigure` for the change to take effect.
## PostgreSQL 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
this limit on the number of concurrent connections.
To fix this problem, you have two options:
- Either increase the max connections value:
1. Edit `/etc/gitlab/gitlab.rb`:
```ruby
postgresql['max_connections'] = 600
```
1. Reconfigure GitLab:
```shell
sudo gitlab-ctl reconfigure
```
- Or, you can consider [using PgBouncer](https://docs.gitlab.com/ee/administration/postgresql/pgbouncer.html) which is a connection pooler for PostgreSQL.
## Reconfigure complains about the GLIBC version
```shell
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment