Обсуждение: BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started

The following bug has been logged online:

Bug reference:      5896
Logged by:          Nacho Mezzadra
Email address:      nachomezzadra@gmail.com
PostgreSQL version: 8.3.14-1
Operating system:   Red Hat 5.3 Enterprise
Description:        When server cannot be started, first it says that it
couldn't be started and then Server Started
Details:

When running the command service postgresql-8.3 start, and, lets say that
the port is already in use, and server cannot be started, then a message
comes up saying that the server could not be started (which is correct given
that the specified port was already in use), and right after that a message
says that PostgreSQL started successfully (which is obviously wrong).

Here is the output I get:

[root@RHEL53Nachao 40594]# service postgresql-8.3 start
Starting PostgreSQL 8.3:
waiting for server to
start...............................................................could
not start server
PostgreSQL 8.3 started successfully
[root@RHEL53Nachao 40594]#

"Nacho Mezzadra" <nachomezzadra@gmail.com> wrote:

> could not start server
> PostgreSQL 8.3 started successfully

That looks like a packaging problem.  The lines starting with
uppercase letters appear to have come from the service script, not
PostgreSQL itself.

-Kevin

[rearranged to eliminate top-posting]

Nacho Mezzadra <nachomezzadra@gmail.com> wrote:
> Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
>> "Nacho Mezzadra" <nachomezzadra@gmail.com> wrote:
>>
>>> could not start server
>>> PostgreSQL 8.3 started successfully
>>
>> That looks like a packaging problem.  The lines starting with
>> uppercase letters appear to have come from the service script,
>> not PostgreSQL itself.

> Meaning that I should fix the service script myself? It's not that
> i wouldn't do it, but just making sure what you are saying.

Sorry.  I don't remember you saying whose build you installed, so
I'm not sure whether the packager will be tracking this list.  If
not, you might want to look for another venue to raise the issue.

Of course, if you feel comfortable adjusting the script, you're in
good shape to work around it yourself.  If you go that route, you
might want to look at my attempt at an LSB-conforming script to see
if any of that is useful for you.  When I suggested this script
there were objections that it was too long and that most of that
logic really belonged in pg_ctl, so I just threw it into the Wiki in
case anyone finds it useful:

http://wiki.postgresql.org/wiki/Lsb_conforming_init_script

-Kevin

Meaning that I should fix the service script myself? It's not that i
wouldn't do it, but just making sure what you are saying.

Thanks and regards,
Nacho.-

On Tue, Feb 22, 2011 at 13:24, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> "Nacho Mezzadra" <nachomezzadra@gmail.com> wrote:
>
>> could not start server
>> PostgreSQL 8.3 started successfully
>
> That looks like a packaging problem. =C2=A0The lines starting with
> uppercase letters appear to have come from the service script, not
> PostgreSQL itself.
>
> -Kevin
>