Unable to install AXA

[Robert Wadra]

Hi Team,

During installation of AXA 17.3 i get the following error
please help

Database Connection failed: psql: FATAL: no pg_hba.conf entry for host "fe80::e2:c7ff:fe2e:7be%eth0", user "aopuser", database "ao_platform", SSL off

[Evangelos Lampropoulos]

Hello,
I have exactly the same issue.
Looking at the installation log it seems that the error is produced by validateDBConnection.sh script which is calling $AXA_BUILD_DIR/resources/dbscripts/postgresql/test-db-connection.sql
This sql script is trying to execute the clause select 'HELLO_POSTGRES';
It seems that we have to add something in pg_hba.conf file so that we can query the database but what is it ?
Should we put it under IPv6 local connections section and then restart the installation wizard ?

I tried simulating the command which produced this error and took the below:

Command
/opt/ca/aoPlatform/tools/usr/pgsql-9.6/bin/psql -U aopuser -w -h ΧΧ.ΧΧ.ΧΧΧ.ΧΧ -d ao_platform -f /opt/ca/AXA17.3.2_Install/resources/dbscripts/postgresql/test-db-connection.sql

Output
/opt/ca/aoPlatform/tools/usr/pgsql-9.6/bin/psql: error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory

Please check if a prerequisite check is missing about libpq.so.5 and if by installing it we can proceed normally with the installation.

------------------------------
Infrastructure Software-Systems Engineer
SYNTAX
------------------------------

[Evangelos Lampropoulos]

Robert please try to add the below line in pg_hba.conf under IPv6 local connection section

host   all   all   fe80::e2:c7ff:fe2e:7be/96   md5

Then save the file and restart postgres service

/opt/ca/aoPlatform/pgsql/bin/pg_ctl -D /opt/ca/aoPlatform/pgsql/data stop
nohup /opt/ca/aoPlatform/pgsql/bin/pg_ctl -D /opt/ca/aoPlatform/pgsql/data start &

Then restart the installation wizard and inform us about the results.

------------------------------
Infrastructure Software-Systems Engineer
------------------------------

[Evangelos Lampropoulos]

Hello again,
A possible root cause for the problem is a misconfigured /etc/hosts file.
Please check if you have a line similar to the below, uncommented in your hosts file.

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4

------------------------------
Infrastructure Software-Systems Engineer
------------------------------

[Jörg Mertin]

Please note that for the /etc/hosts file, the format is:
IP FQDN ALIAS1 ALIAS2 ... ALIASn

means, it should look like:

127.0.0.1  localhost.localdomain localhost bestserver blafoo
127.0.1.1  localhost4.localdomain4 localhost4 sendserver foo

Putting 2 FQDN's into the same line is bad and will cause weird results on some applications..
If you need to add another FQDN, use anything in the 127.x.x.x range for it, as shown in the previous example.