[Piuparts-devel] Bug#801575: piuparts.d.o (piu-slave-bm-a) fails to start PostgreSQL

Evgeni Golov evgeni at debian.org
Mon Oct 12 07:53:34 UTC 2015


Package: piuparts.debian.org
Severity: normal

Ohai!

I have uploaded a new Bareos to sid yesterday, and it seems piuparts
failed to test it properly:
 https://piuparts.debian.org/sid/fail/bareos-database-common_14.2.5-2.log

Dissecting the log further, one sees that piuparts calls its
pre_install_database-server script, which decides to run
 apt-get -y install postgresql
and that seems to fail as the port it wants to use is already use:

  Setting up postgresql-common (170) ...
  Adding user postgres to group ssl-cert
  
  Creating config file /etc/postgresql-common/createcluster.conf with new version
  Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  Removing obsolete dictionary files:
  Running in chroot, ignoring request.
  No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning).
  Setting up postgresql-9.4 (9.4.5-1) ...
  Creating new cluster 9.4/main ...
    config /etc/postgresql/9.4/main
    data   /var/lib/postgresql/9.4/main
    locale C
    port   5433
  update-alternatives: using /usr/share/postgresql/9.4/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
  Running in chroot, ignoring request.
  Starting PostgreSQL 9.4 database server: mainThe PostgreSQL server failed to start. Please check the log output: 2015-10-12 00:24:03 UTC [19161-1] LOG: could not bind IPv6 socket: Address already in use 2015-10-12 00:24:03 UTC [19161-2] HINT: Is another postmaster already running on port 5433? If not, wait a few seconds and retry. 2015-10-12 00:24:03 UTC [19161-3] LOG: could not bind IPv4 socket: Address already in use 2015-10-12 00:24:03 UTC [19161-4] HINT: Is another postmaster already running on port 5433? If not, wait a few seconds and retry. 2015-10-12 00:24:03 UTC [19161-5] WARNING: could not create listen socket for "localhost" 2015-10-12 00:24:03 UTC [19161-6] FATAL: could not create any TCP/IP sockets ... failed!
   failed!
  invoke-rc.d: initscript postgresql, action "start" failed.
  dpkg: error processing package postgresql-9.4 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of postgresql:
   postgresql depends on postgresql-9.4; however:
    Package postgresql-9.4 is not configured yet.
  
  dpkg: error processing package postgresql (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.19-22) ...
  Processing triggers for systemd (227-2) ...
  E: Sub-process /usr/bin/dpkg returned an error code (1)
0m24.8s ERROR: Command failed (status=100): ['chroot', '/srv/piuparts.debian.org/tmp/tmpyDdDgr', 'tmp/scripts/pre_install_database-server']

As PostgreSQL works just fine in a fresh Sid chroot after installation,
I suspect a problem on piu-slave-bm-a or in its specific configuration.

Regards
Evgeni

-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



More information about the Piuparts-devel mailing list