Your message dated Sun, 13 Aug 2017 21:17:01 +0200
with message-id <20170813191701.xxwmt4er47z7l...@msg.df7cb.de>
and subject line Re: [Pkg-postgresql-public] Bug#871986: Bug#871986:
postgresql-9.6: PostgreSQL fails to start after upgrade
has caused the Debian Bug report #871986,
regarding postgresql-9.6: PostgreSQL fails to start after upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
871986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-9.6
Version: 9.6.4-0+deb9u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Last night I upgraded "postgresql-9.6" to the most recent version
(went from 9.6.3-3 to 9.6.4-0+deb9u1).
As a part of the upgrade PostgreSQL was shut down, and it has not come
up since then.
% ls -lFNart /var/log/postgresql
totalt 16
-rw-r----- 1 postgres adm 700 jul 2 06:25 postgresql-9.6-main.log.2.gz
-rw-r----- 1 postgres adm 341 aug 13 06:25 postgresql-9.6-main.log.1
drwxrwxr-t 2 root postgres 4096 aug 13 06:25 ./
-rw-r----- 1 postgres adm 0 aug 13 06:25 postgresql-9.6-main.log
drwxr-xr-x 10 root root 4096 aug 13 06:25 ../
% tail /var/log/postgresql/postgresql-9.6-main.log.1
2017-08-12 19:33:04 CEST [2060-2] LOG: received fast shutdown request
2017-08-12 19:33:04 CEST [2060-3] LOG: aborting any active transactions
2017-08-12 19:33:04 CEST [2065-2] LOG: autovacuum launcher shutting down
2017-08-12 19:33:04 CEST [2062-1] LOG: shutting down
2017-08-12 19:33:04 CEST [2060-4] LOG: database system is shut down
%
I've tried "sudo service postgresql restart" without any visible effect.
/Jacob
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=da:da_DK:fo:fo_FO:nb:nb_NO:nn:nn_NO:no:no_NO:sv:sv_SE:sv_FI:en_GB:en_DK:en_AU:en:it:it_IT:is:is_IS:fr:fr_FR:de:de_DE:en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postgresql-9.6 depends on:
ii libc6 2.24-11+deb9u1
ii libgssapi-krb5-2 1.15-1
ii libldap-2.4-2 2.4.44+dfsg-5
ii libpam0g 1.1.8-3.6
ii libpq5 9.6.4-0+deb9u1
ii libssl1.1 1.1.0f-3
ii libsystemd0 232-25+deb9u1
ii libxml2 2.9.4+dfsg1-2.2
ii locales 2.24-11+deb9u1
ii postgresql-client-9.6 9.6.4-0+deb9u1
ii postgresql-common 181
ii ssl-cert 1.0.39
ii tzdata 2017b-1
Versions of packages postgresql-9.6 recommends:
ii postgresql-contrib-9.6 9.6.4-0+deb9u1
ii sysstat 11.4.3-2
Versions of packages postgresql-9.6 suggests:
ii locales-all 2.24-11+deb9u1
-- no debconf information
--- End Message ---
--- Begin Message ---
Re: Jacob Sparre Andersen 2017-08-13
<051d907f-37cd-73ff-e55d-a84a3c955...@jacob-sparre.dk>
> Christoph Berg wrote:
>
> > Is /etc/postgresql/9.6/main/start.conf set to "auto"?
>
> No. :-(
>
> It appears that I simply hadn't switched from "manual" to "auto" after I
> finished the upgrade from 9.4 (Jessie) to 9.6.
>
> I'm sorry about filling trivial problems like that in the bug database.
No worries, thanks for reporting it. This is way better than the
reverse - having problems not fixed just because they happen to
everyone except the maintainer doesn't make sense :)
> > > I've tried "sudo service postgresql restart" without any visible effect.
> >
> > postgresql.service is just a stub which forwards all actions to the
> > individual services like postgresql@9.6-main.service. Unfortunately
> > systemctl doesn't really relay any errors back if there's any.
>
> Could "postgresql.service" be expanded such that running "service
> postgresql" will output a suggestion to use "systemctl" instead?
Using the "service" program to start/stop services is fine - what I
meant to say was that "service postgresql status" or "systemctl status
postgresql" (which are backed by /lib/systemd/system/postgresql.service)
won't output much, while "service postgresql@9.6-main status" (or via
systemctl) gives you the real information.
The idea to add a hint to the "postgresql status" output is
interesting. I'm not sure we can really put any text there, but I'll
investigate. Thanks for the idea!
Christoph
--- End Message ---
