From: | Roland van Laar <roland(at)micite(dot)net> |
---|---|
To: | LOUBRADOU, Rémy <r(dot)loubradou(at)adveez(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: BDR install broken on Ubuntu 14.04 |
Date: | 2016-01-13 18:39:27 |
Message-ID: | 569699DF.8080504@micite.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 13-01-16 17:48, LOUBRADOU, Rémy wrote:
> Hi,
>
> I have the same issue. It was working fine a month ago. I wrote a
> cookbook with chef to install BDR a month ago since then I did not
> change the cookbook but now I got this error.
>
> This seem to be the heart of the issue:
>
> Removing obsolete dictionary files:
> ==> ldev4: * No PostgreSQL clusters exist; see "man pg_createcluster"
> ==> ldev4: /usr/share/postgresql-common/maintscripts-functions: line
> 95: db_stop: command not found
> ==> ldev4: dpkg: error processing package postgresql-bdr-9.4
> (--configure):
> ==> ldev4: subprocess installed post-installation script returned
> error exit status 127
>
>
> Anyone know what's going on ? I'm going to investigate.
The debconf source file is missing.
db_stop, stands for debconf stop.
It is supposed to be fixed but it is not.
See this closed issue on Github:
https://github.com/2ndQuadrant/bdr/issues/156
I "fixed" it in ansible by
- installing bdr accepting the fail
- removing the db_stop line
- installing bdr again.
This is the relevant part of my ansible configuration:
- name: install postgresql bdr
apt:
name=postgresql-bdr-9.4-bdr-plugin
state=present
ignore_errors: yes
- name: remove db_stop from postgres postinstall script
lineinfile:
dest=/usr/share/postgresql-common/maintscripts-functions
regexp=db_stop
state=absent
- name: reinstall postgresql bdr to mitigate the db_stop problem
apt:
name=postgresql-bdr-9.4-bdr-plugin
state=present
Regards,
Roland
>
> Thanks for your replies,
>
> Rémy
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-01-13 18:48:57 | Re: plv8 binaries for PostgreSQL 9.5 on Windows |
Previous Message | Jim Nasby | 2016-01-13 18:25:20 | Re: Changing varchar length by manipulating pg_attribute |