Please feel free to respond to Marco. Have you seen this before? What solved the issue for you?
RedHat 7 and Postgres on APM 10.7 is supported
PCM for CA Software - Agile Operations Product Compatibility Search
I would check the postgres install logs especially post-install logs
Problem running post-install step. Installation may not complete correctly
Marco, would there have been pre-existing Postgres instance installed on this Redhat 7 server?
Please attach the postgres install logs. Also as Francis said, check if there is another instance of Postgres on there. Generally some Redhat distributions already have a pre-installed postgres.
In addition to what Francis & Matt suggested is this a root or non-root install?
I have checked a similar issue and I believe Lynn is right. I guess you are using non-root user for the installation and it is trying to overwrite some folders owned by the root.
thank for answer.
This is a new installation, executed under root user.
Examining postgres-log file we found:
initialising the database cluster (this may take a few minutes)...Executing /appl_bin/CA/APM10.7.0/APMDB/installer/server/initcluster.sh "postgres" "postgres" "/appl_bin/CA/APM10.7.0/APMDB" "/appl_bin/CA/APM10.7.0/APMDB/data" 5432 DEFAULTScript exit code: 1
Script output: Failed to initialise the database cluster with initdb
Script stderr: su: warning: cannot change directory to /appl_bin/CA/APM10.7.0/APMDB: Permission denied-sh: /appl_bin/CA/APM10.7.0/APMDB/.profile: Permission denied-sh: /appl_bin/CA/APM10.7.0/APMDB/bin/initdb: Permission denied
So it seems a problem related at the permissions on the folders.
We solved forcing a chmod 777 on the dbscripts and installation folder.
Marco is working with support via issue 01194182. Install seems to have been done with root user and in-house we have not been able to replicate the problem. Currently awaiting result of uninstall and reinstall to different target directory with InstallerAnywhere debug enabled (export LAX_DEBUG=true (console mode) or export LAX_DEBUG=/Install.log). Also checking root ~/.bash_profile