[Pkg-postgresql-public] Bug#710093: postgresql: not started automatically after installation in chroot
anbe at debian.org
Tue May 28 08:20:18 UTC 2013
User: debian-qa at lists.debian.org
I'm experimenting with db support for piuparts tests and therefore
postgresql needs to be installed and started in the test chroots.
Until now this worked fine (with an adjusted policy-rc.d that allows
starting of certain services), but has recently stopped to do so in
sid. It still works fine in wheezy.
apt-get install postgresql in the chroot ends with
Setting up libpq5 (9.1.9-1) ...
Setting up openssl (1.0.1e-3) ...
Setting up postgresql-client-common (143) ...
Setting up postgresql-client-9.1 (9.1.9-1) ...
update-alternatives: using /usr/share/postgresql/9.1/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode
Setting up ssl-cert (1.0.32) ...
Setting up postgresql-common (143) ...
Adding user postgres to group ssl-cert
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning).
Setting up postgresql-9.1 (9.1.9-1) ...
Creating new cluster 9.1/main ...
update-alternatives: using /usr/share/postgresql/9.1/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Starting PostgreSQL 9.1 database server: main.
Setting up postgresql (9.3+142really9.1+143) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
and this looks like some service should be running, but it is not.
I could now chroot into the installation and run manually
invoke-rc.d postgresql start
and this will work.
As a consequence of not starting postgresql properly, no packages
depending on this service can be tested.
I don't really know anything about postgresql ... so you will need to give
me some aid if you need more dbugging information.
More information about the Pkg-postgresql-public