After update cannot push.

Using the Ubuntu package, after an update I get the following error when pushing: GitLab: API is not accessible Then, on the server I did gitlab-ctl status:

run: gitlab-git-http-server: (pid 1766) 784s; run: log: (pid 579) 931s
run: logrotate: (pid 1773) 783s; run: log: (pid 582) 931s
run: nginx: (pid 1779) 783s; run: log: (pid 583) 931s
down: postgresql: 1s, normally up, want up; run: log: (pid 580) 931s
run: redis: (pid 1796) 777s; run: log: (pid 588) 931s
run: sidekiq: (pid 1805) 775s; run: log: (pid 581) 931s
run: unicorn: (pid 1825) 773s; run: log: (pid 591) 931s

So it must be postgresql. Do a gitlab-ctl restart, and a reboot, same thing. So then I do a gitlab-ctl tail, and find this exert:

==> /var/log/gitlab/postgresql/current <==
2015-09-24_18:43:34.87636 FATAL:  could not create shared memory segment: Invalid argument
2015-09-24_18:43:34.87660 DETAIL:  Failed system call was shmget(key=5432001, size=293978112, 03600).
2015-09-24_18:43:34.87668 HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 293978112 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
2015-09-24_18:43:34.87674       If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.

sysctl -a | grep shmmax:

kernel.shmmax = 33554432

And this keeps repeating aver and over again. This is an openVZ VPS, if it can help.

So, in attempt to fix this, I changed shmmax to 134217728 (4x the previous val). Now postgreSQL says:

2015-09-25_01:02:45.08026 FATAL:  could not create shared memory segment: Invalid argument
2015-09-25_01:02:45.08051 DETAIL:  Failed system call was shmget(key=5432001, size=293978112, 03600).
2015-09-25_01:02:45.08057 HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 293978112 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
2015-09-25_01:02:45.08066       If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
2015-09-25_01:02:45.08074       The PostgreSQL documentation contains more information about shared memory configuration.

It seems like a bad idea to use more than 1/4 of my RAM in shared mem.

+1 Though considering the request size in the error log, you shouldn't be surprised only increasing it some of the way didn't resolve it

sysctl -w kernel.shmmax=293978112 worked

Tried to get away with running the upgrade to 8.0.2 & reducing the value back to normal & restarting services but this was failing again.

It's a pretty severe bug since the whole instance errors 500 as a result!!!

Found possible resolution. Change /etc/gitlab/gitlab.rb under the postgreSQL section so that the shared buffers and max conections are less. I used 16M in the memory and 20 connections. plenty if you are using it only for personal use.

I didn't want to waste all that ram for a small server.

Hi @kkprince1998,

First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 4 months
• Unlabelled
• Unassigned
• It's not associated with a particular milestone

We'd like to ask you to help us out and determine whether this issue should be reopened.

If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.

If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks for your help

Status changed to closed

Added ~761915 label

mentioned in merge request !14785