Ubuntu
postgresql-8.3 package

package postgresql-8.3 8.3.7-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #494610 reported by A L Nachiappa on 2009-12-09

This bug report is a duplicate of: Bug #225125: /etc/ssl/private/ssl-cert-snakeoil.key is world readable. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	postgresql-8.3 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: postgresql-8.3

i am not able to update to 9.10

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: postgresql-8.3 8.3.7-1
SourcePackage: postgresql-8.3
Title: package postgresql-8.3 8.3.7-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.28-11-generic i686

Tags:

Revision history for this message

A L Nachiappa (a-thekkur-nachiappa) wrote on 2009-12-09:

Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (4.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-12-10:

Thanks for your report.

Postgresql didn't start for the following reasons:
2009-12-09 22:42:16 IST FATAL: unsafe permissions on private key file "server.key"
2009-12-09 22:42:16 IST DETAIL: File must be owned by the database user or root, must have no write permission for "group", and must have no permissions for "other".

Check the database log files, fix the configuration and permissions and retry. This will likely solve your problem.
I'm closing this pb because it is not a bug in Ubuntu. Don't hesitate to submit any new bug.

Changed in postgresql-8.3 (Ubuntu):
status:	New → Invalid

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-03-13:

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 225125, 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.