Ubuntu
postgresql-common package

SysV status script returns the wrong exit code when postgresql is not running

Bug #921001 reported by Glenn Aaldering on 2012-01-24

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	postgresql-common (Ubuntu)	Triaged	Low	Unassigned

Bug Description

SysV status script returns the wrong exit code when postgresql is not running:

[Precise]
# /etc/init.d/postgresql status
Running clusters:
# echo $?
0

This seems to work ok in Lucid:

[Lucid]
# /etc/init.d/postgresql-8.4 status
Running clusters:
# echo $?
3

Tags:

Martin Pitt (pitti) on 2012-03-06

affects:	postgresql-9.1 (Ubuntu) → postgresql-common (Ubuntu)
Changed in postgresql-common (Ubuntu):
status:	New → Triaged
importance:	Undecided → Low

Revision history for this message

Lars Tobias Skjong-Børsting (larstobi) wrote on 2012-05-22:

Exit non-zero if any postgres cluster is stopped. Edit (306 bytes, text/plain)

The attached patch fixes the exit status for me.

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2012-05-22:

The attachment "Exit non-zero if any postgres cluster is stopped." of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags:

added: patch