Your message dated Fri, 12 Aug 2016 21:39:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#795410: postgresql-common: pg_createcluster fails on
clean install of postgresql
has caused the Debian Bug report #795410,
regarding postgresql-common: pg_createcluster fails on clean install of
postgresql
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.)
--
795410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795410
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-common
Version: 169
Severity: grave
Justification: renders package unusable
Dear Maintainer,
On a clean install of postgresql on debian sid, using a minimal system,
/etc/postgresql is created with owner root:root and permissions 750.
postgres user can't read /etc/postgresql/9.4/main/postgresql.conf. Several
utilities fail because of this, namely pg_createcluster during install.
The base system is running on a container, created with debootstrap
--include=locales,openssh-server sid <directory> <mirror>
Just after system install, postgres was installed with: apt-get install
postgresql.
The installer produces this output:
Setting up postgresql-9.4 (9.4.4-1) ...
Creating new cluster 9.4/main ...
config /etc/postgresql/9.4/main
data /var/lib/postgresql/9.4/main
locale en_US.UTF-8
Flags of /var/lib/postgresql/9.4/main set as -------------e-C
Warning: The socket directory for owners other than 'postgres'
defaults to /tmp. You might want to change the unix_socket_directories parameter
in postgresql.conf to a more secure directory.
Error: could not open /etc/postgresql/9.4/main/postgresql.conf for reading at
/usr/share/perl5/PgCommon.pm line 194.
Can't exec "/bin/sh": Permission denied at /usr/bin/pg_createcluster line 590.
Error: could not create default cluster. Please create it manually with
pg_createcluster 9.4 main --start
or a similar command (see 'man pg_createcluster').
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postgresql-common depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.57
ii init-system-helpers 1.23
ii lsb-base 4.1+Debian13+nmu1
ii postgresql-client-common 169
ii procps 2:3.3.10-2
ii ssl-cert 1.0.36
ii ucf 3.0030
Versions of packages postgresql-common recommends:
ii logrotate 3.8.7-2
postgresql-common suggests no packages.
-- debconf information:
postgresql-common/obsolete-major:
postgresql-common/ssl: true
--- End Message ---
--- Begin Message ---
Re: Sérgio Carvalho 2015-08-17
<CADLrx4E257hnACmg1_bWiWRimOtEk=dvq3gm6ssuysxyq-i...@mail.gmail.com>
> Can't exec "/bin/sh": Permission denied at /usr/bin/pg_createcluster line
> 590.
> Sorry for the long mail. It was inevitable. It seems pg_createcluster is
> actually wrong, the configuration change should be done as root (from what
> I infer from the rest of the script). However, something in debian
> triggered this, as it didn't use to happen (I last did this operation over
> a year ago, so my the bisection is not much use, really).
Hi Sérgio,
I still think that '"/bin/sh": Permission denied' is the root cause of
the problem. That's nothing we can fix in postgresql-common.
Christoph
--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
