package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-8.4 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: postgresql-8.4
The PostgreSQL server failed to start. Please check the log output:
2011-06-10 21:54:24 IST FATAL: could not create shared memory segment: Invalid argument
2011-06-10 21:54:24 IST DETAIL: Failed system call was shmget(key=5432001, size=35332096, 03600).
2011-06-10 21:54:24 IST 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 35332096 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 18).
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.
The PostgreSQL documentation contains more information about shared memory configuration.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: postgresql-8.4 8.4.8-0ubuntu0.
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelMo
AptOrdering:
postgresql-8.4: Install
postgresql-8.4: Configure
Architecture: i386
Date: Fri Jun 10 21:26:48 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Custom Live CD - Release i386
SourcePackage: postgresql-8.4
Title: package postgresql-8.4 8.4.8-0ubuntu0.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 264336, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.