Ubuntu
postgresql-common package

package postgresql-common 114 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #784068 reported by Seth Rosenblum on 2011-05-17

This bug report is a duplicate of: Bug #264336: pgsql fails to start due to shared buffer setting greater than kernel allows. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	postgresql-common (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: postgresql-common

Was installing a large group of updates, didn't even notice that postgresql was part of the update list.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: postgresql-common 114
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Tue May 17 10:51:24 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: postgresql-common
Title: package postgresql-common 114 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2011-04-29 (17 days ago)

Tags:

Revision history for this message

Seth Rosenblum (ricklerre) wrote on 2011-05-17:

AptOrdering.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (480 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (54.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.6 KiB, application/x-gzip)

Revision history for this message

Martin Pitt (pitti) wrote on 2011-10-12:

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.