Thread: BUG #14967: Postgresql won't start after upgrade frompostgresql93-9.3.20-1PGDG.rhel7.x86_64

BUG #14967: Postgresql won't start after upgrade frompostgresql93-9.3.20-1PGDG.rhel7.x86_64

From
martinsson.patrik@gmail.com
Date:
The following bug has been logged on the website:

Bug reference:      14967
Logged by:          Patrik Martinsson
Email address:      martinsson.patrik@gmail.com
PostgreSQL version: 9.3.20
Operating system:   CentOS 7.4.1708
Description:

Hi, 

I'm not sure where the "bug" lies here, but I just noticed that running an
yum update from postgresql93-9.3.20-1PGDG.rhel7.x86_64 ->
9.3.20-3PGDG.rhel7.x86_64 makes postgresql impossible to start through
systemd. 

The issue seems to be related to the parameter "TimeoutSec=infinity" in
/usr/lib/systemd/system/postgresql-9.3.service. 

Running "systemctl start postgresql-9.3.service" immediately fails with 

> "Job for postgresql-9.3.service failed because a timeout was exceeded. See
"systemctl status postgresql-9.3.service" and "journalctl -xe" for details."


Running "systemctl status postgresql-9.3.service" reveals following, 

$ > systemd[1]: Starting PostgreSQL 9.3 database server...
$ > systemd[1]: postgresql-9.3.service start operation timed out.
Terminating.
$ > systemd[1]: Failed to start PostgreSQL 9.3 database server.
$ > systemd[1]: Unit postgresql-9.3.service entered failed state.
$ > systemd[1]: postgresql-9.3.service failed.

The difference I see in the /usr/lib/systemd/system/postgresql-9.3.service
between these two versions are that the "TimeoutSec-parameter-value" is
changed from "300" to infinity. Changing the parameter back to 300 makes
postgresql start again as normal. 

I have to admit I don't really understand whats going on here, since I'm
under the impression that setting the value to "infinity" would disable the
timeout and thus wait forever on "ExecStartPre=" to do its thing. However,
there is clearly something I'm missing. 

This is not a bug in postgresql per say, but I couldn't find a better place
to put this. 

Any suggestions ? 
Best regards,
Patrik Martinsson
Sweden









Hi,

On Tue, 2017-12-12 at 10:00 +0000, martinsson.patrik@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      14967
> Logged by:          Patrik Martinsson
> Email address:      martinsson.patrik@gmail.com
> PostgreSQL version: 9.3.20
> Operating system:   CentOS 7.4.1708
> Description:
>
> Hi,
>
> I'm not sure where the "bug" lies here, but I just noticed that running an
> yum update from postgresql93-9.3.20-1PGDG.rhel7.x86_64 ->
> 9.3.20-3PGDG.rhel7.x86_64 makes postgresql impossible to start through
> systemd.
>
> The issue seems to be related to the parameter "TimeoutSec=infinity" in
> /usr/lib/systemd/system/postgresql-9.3.service.

<snip>

You are right. A test commit accidentally went into prod repos. Apologies for
that. I just pushed updated packages to repos. yum update will fix the issue.

Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Thanks for the update. 
Luckily no one else is running automatic yum update every morning on their production postgresql-database ¯\_(ツ)_/¯ :D 

// Patrik
 

On Tue, Dec 12, 2017 at 6:26 PM Devrim Gündüz <devrim@gunduz.org> wrote:

Hi,

On Tue, 2017-12-12 at 10:00 +0000, martinsson.patrik@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      14967
> Logged by:          Patrik Martinsson
> Email address:      martinsson.patrik@gmail.com
> PostgreSQL version: 9.3.20
> Operating system:   CentOS 7.4.1708
> Description:
>
> Hi,
>
> I'm not sure where the "bug" lies here, but I just noticed that running an
> yum update from postgresql93-9.3.20-1PGDG.rhel7.x86_64 ->
> 9.3.20-3PGDG.rhel7.x86_64 makes postgresql impossible to start through
> systemd.
>
> The issue seems to be related to the parameter "TimeoutSec=infinity" in
> /usr/lib/systemd/system/postgresql-9.3.service.

<snip>

You are right. A test commit accidentally went into prod repos. Apologies for
that. I just pushed updated packages to repos. yum update will fix the issue.

Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR