New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres fails to start due to too large a shared memory setting #211
Comments
It seems that current Chef server 12 embedded private_chef cookbook did not fix this issue. In https://github.com/chef/chef-server/blob/master/omnibus/files/private-chef-cookbooks/private-chef/attributes/default.rb#L410, the shmmax has been set to However, in the following logic to calculate shared_buffer from line 424 - line 432:
It is actually treating this But this can still be covered if the block in https://github.com/chef/chef-server/blob/master/omnibus/files/private-chef-cookbooks/private-chef/recipes/postgresql.rb#L68 did not put 16GB limit sysctl. |
BYTES_IN_GIG = 1048576 just a bit off....maybe closer to 1073741824? |
This is being worked on here: #309 |
It appears #309 has been merged, so I'm going to close this one out. |
On a machine with 128Gb of RAM chef is configuring postgres for 32Gb of shared memory, in
/var/opt/opscode/postgresql/9.2/data/postgresql.conf
:but it has only configured the kernel for 16Gb of shared memory, in
/etc/sysctl.d/90-postgresql.conf
:Postgres then fails to start, and the upgrade from chef server 11 fails a a result.
This looks like it may be a return of https://tickets.opscode.com/browse/CHEF-3889?
The text was updated successfully, but these errors were encountered: