Symptoms
A Provider installed some external tool which connects to the PBA 5.1 database to fetch data from it. For example, it may be some reporting or monitoring system.
After PBA was upgraded to 5.4, the external tool lost the ability to connect to the PBA PostgreSQL database. The error message like provided below appears when attempting to connect to the PBA database:
FATAL: no pg_hba.conf entry for host "192.168.1.11", user "pba", database "pba", SSL off
192.168.1.11 is the IP address of the host where the external tool that is trying to connect to PBA database is installed.
Cause
Access to the PBA database from the external host was lost during the upgrade from 5.1 to 5.4.
During the update from PBA 5.1 to 5.4, the database engine is upgraded from PostgreSQL 8 to PostgreSQL 9 and the new configuration file pg_hba.conf is generated. Access to the PBA database from external hosts should be configured in the mentioned configuration file. Since PBA knows nothing about the manually configured external systems which had access to the PBA database before the upgrade, the PBA upgrade tool configures access to the database for known systems only.
Resolution
Get information about the hosts that are allowed to connect to the PBA database from the backup configuration file saved on the PBA Database Server at /var/lib/pgsql/data.old/pg_hba.conf (usually, access data is written into the end of the file) and add all needed hosts into the current configuration file /var/lib/pgsql/data/pg_hba.conf.
Changes can be applied to PoetgreSQL following way without restart:
# su postgres
# cd /var/lib/pgsql/data/
# /usr/pgsql/bin/pg_ctl -D /var/lib/pgsql/data/ reload
Please be aware that paths depend on particular PostgreSQL version. For example for PostgreSQL 9.1:
# cd /var/lib/pgsql/9.1/data/
# /usr/pgsql-9.1/bin/pg_ctl -D /var/lib/pgsql/9.1/data/ reload