Your message dated Fri, 01 Mar 2019 21:24:29 +0000
with message-id <[email protected]>
and subject line Bug#872660: fixed in postgresql-common 200
has caused the Debian Bug report #872660,
regarding postgresql-common: When creating a cluster from pg_createcluster, the 
cluster starting command displayed is incorrect
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 [email protected]
immediately.)


-- 
872660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872660
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-common
Version: 184.pgdg+1
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Step to reproduce 
 - install postgresql 10
 - create a new 10 postgresq cluster from pg_createcluster command 
   ex :  pg_createcluster 10 jp -p 5444
   The cluster is well created and the following information is displayed :
     Success. You can now start the database server using:

    /usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/jp -l logfile 
start

 - connect under postgres Debian account and try to start the cluster with the 
previous command. It fails.
    /usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/jp  start
       waiting for server to start....postgres: 
       could not access the server configuration file 
"/var/lib/postgresql/10/jp/postgresql.conf": No such file or directory
        stopped waiting
        pg_ctl: could not start server

  The reason is when you use pg_createcluster to create the cluster, the 
postgresql.conf file is 
      under     "/etc/postgresql/10/<CLUSTERNAME>" 
      not under "/var/lib/postgresql/10/jp/postgresql.conf" .

  So, correct command for starting the cluster is  
/usr/lib/postgresql/10/bin/pg_ctl -D /etc/postgresql/10/<CLUSTERNAME> start

For me, the correct command for starting the cluster should be displayed when 
creating a cluster from pg_createcluster.

Thanks for your work.

*** End of the template - remove these template lines ***


-- 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/1 CPU core)
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15), 
LANGUAGE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser                   3.115
ii  debconf [debconf-2.0]     1.5.61
ii  init-system-helpers       1.48
ii  lsb-base                  9.20161125
ii  postgresql-client-common  184.pgdg+1
ii  procps                    2:3.3.12-3
ii  ssl-cert                  1.0.39
ii  ucf                       3.0036

Versions of packages postgresql-common recommends:
ii  logrotate  3.11.0-0.1

Versions of packages postgresql-common suggests:
pn  libjson-perl  <none>

-- debconf information excluded

--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 200

We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <[email protected]> (supplier of updated postgresql-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 01 Mar 2019 20:47:06 +0100
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all 
postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all
Architecture: source
Version: 200
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <[email protected]>
Changed-By: Christoph Berg <[email protected]>
Description:
 postgresql - object-relational SQL database (supported version)
 postgresql-all - metapackage depending on all PostgreSQL server packages
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-server-dev-all - extension build tool for multiple PostgreSQL 
versions
Closes: 653870 810615 839954 872660 891234 910991 916449 918784 920248
Changes:
 postgresql-common (200) unstable; urgency=medium
 .
   * pg_createcluster: Don't refuse explicit -p argument even when port is
     already in use. (Closes: #653870)
   * pg_createcluster: Override suggested cluster start command in initdb.
     (Closes: #872660)
   * pg_upgradecluster, t/052_upgrade_encodings.t: pg_dumpall 11 retains the
     database encoding, so switching encodings via dump-restore does not work
     anymore.
   * pg_upgradecluster: Deprecate 'replacement_sort_tuples' in version 11.
   * pg_upgradecluster: Migrate postgresql.auto.conf to new cluster.
     (Closes: #810615)
   * pg_ctlcluster: Die early if logfile is not available. (Closes: #891234)
   * pg_ctlcluster: Die early if pg_ctl cannot be found. (See: #918784)
   * pg_ctlcluster: Document --skip-systemctl-redirect, and skip redirect if
     --foreground is requested.
   * pg_renamecluster: Notify systemd. (Closes: #839954)
   * pg_renamecluster: Document that cluster_name is updated as well.
   * pg_dropcluster: Delete tablespace directories. (Closes: #916449)
   * pg_dropcluster: Silence warning if data_directory is already gone.
     Spotted by Jean-Christophe Arnu, merci!
   * get_cluster_port: Fall back to 5432 if port is not defined in config.
     (Closes: #920248)
   * read_cluster_conf_file: Use cluster_data_directory instead of hardcoding
     /var/lib/postgresql.
   * [email protected]: Add After=network.target to ensure the server is
     stopped before networking goes down on shutdown. Thanks Elrond!
     (Closes: #910991)
   * [email protected]: Drop /var prefix from PIDFile, systemd complained
     about legacy directory /var/run/postgresql.
   * postgresql-generator: Don't attempt to auto-start removed versions.
     (Closes: #918784)
Checksums-Sha1:
 d6675402a5fe29fd14fb57c3d4539b7617f2d8f6 2309 postgresql-common_200.dsc
 fe8db48a9d888ed6008ae803a77298430cf7ee5e 212312 postgresql-common_200.tar.xz
Checksums-Sha256:
 f1328615b2b2b99cd0ac5d641887670f75b3b355a056e35ec2618fdf93ccc221 2309 
postgresql-common_200.dsc
 ccd6f45ce5674d1a0115be98f370e0016b96edba796584ebc46bc933e42c8761 212312 
postgresql-common_200.tar.xz
Files:
 88628166ef7ccb1b61a842159d1b799b 2309 database optional 
postgresql-common_200.dsc
 fa65f945b2cf4bf6a8c5a303014661e5 212312 database optional 
postgresql-common_200.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlx5mrkACgkQTFprqxLS
p67U6RAAnoidZEhJJL+vvNhewfEXqseDJgY5NJ7vVsewdAg33kDxwnbXXf562Qet
kyPwvIycL8sJJ2d3THPV7oRTUtAgjhx+JUWmpY3FHran3Em9jQ0oJrw297xrhJSc
lsznchLV0xmJHnCFVVWX6pOX576BMVQbMFC094VclW6OXEZNauvBOaLYakqjU5Xr
wjfPCJxzTIOQkOWap8hrNGGLA49rapX7p9sZY7V8naaybk3zclv/MuEZ1wXRc2Cz
x+TIWG7ceLFFndAtITBC0xX/k0dVXGPWxQbJkr970soLPIvMTxNr3WbMFamKwn03
LTbsf2zhO82i15fuaPNApE8CbBVjmbR9wUzH8oTcZVKwJj8N9XWArPU7TGqw2au1
sY+rhWxLv6jSVqrN75iiNtFJ5usFBQAWAAPl4rG+elLgDNTpTKZ8iMNiH/hncwUM
JBpSP+rzRZH7Of7vV/F+R9soNlF8akQNdEm4VXOrygk/dZOW/7wgDb62b/wiPgwF
9NZ6cWMmtLXxBBptARM+XctVzHbB5ac2Vu9tBkOeu2UfQC8eOTtS2RKUJ223RA0e
Lh4TfgV1I+AqwCxd6dN9oJiv18dN5209HjnNNDxkyEdqPMOJ9cEVqIDbVnmsbIR+
5lsIjoV0S2eRf61oXpPnCbMz5pubdvx9dTM3C1+tnzFbgilX9mE=
=STnB
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to