Postgres install hangs on RHEL 7.5

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

After launching the 10.7 installer in silent mode (see below), the "Launching installer..." message is still showing after 45 minutes.

[/CA_APM/software]# ./introscope10.7.0.45linuxAMD64.bin LAX_VM /usr/bin/java -f /CA_APM/software/APM_10_7_DB_silent_install_response_file.txt

Preparing to install
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Note: LAX_VM is pointing to OpenJDK JRE 1.7

Running ps command indicates that the installer has started the Postgres DB engine:

[/CA_APM/DB/10_7_0]# ps -ef | grep postgres

root 18952 18942 1 14:30 pts/0 00:00:19 ./postgresql-9.6.2-3-linux-x64.run --serverport 5432 --mode unattended --unattendedmodeui none --prefix /CA_APM/DB/10_7_0 --datadir /CA_APM/DB/10_7_0/data

root 19081 18952 0 14:30 pts/0 00:00:00 /bin/sh /CA_APM/DB/10_7_0/installer/server/initcluster.sh postgres postgres /CA_APM/DB/10_7_0 /CA_APM/DB/10_7_0/data 5432 DEFAULT

root 19135 19081 0 14:30 pts/0 00:00:00 su -s /bin/sh - postgres -c mv /CA_APM/DB/10_7_0/datapostgresql.conf.19081 /CA_APM/DB/10_7_0/data/postgresql.conf

postgres 19137 19135 0 14:30 ? 00:00:00 mv -i /CA_APM/DB/10_7_0/data/postgresql.conf.19081 /CA_APM/DB/10_7_0/data/postgresql.conf

Environment

Release : 10.7.0

Cause

The silent installer was failing when the PostgreSQL installation failed to move postgresql.conf in the installation process. This could be due to a permission issue or a system issue. "mv -i /CA_APM/DB/1070/data/postgresql.conf.52181 /CA_APM/DB/1070/data/postgresql.conf " This statement hung.

[/CA_APM/software]# ps -eaf | grep postgres

root 52052 52042 13 15:12 pts/0 00:00:20 ./postgresql-9.6.2-3-linux-x64.run --serverport 5432 --mode unattended --unattendedmodeui none --prefix /CA_APM/DB/1070 --datadir /CA_APM/DB/1070/data --xxxxxx xxxxx

root 52181 52052 0 15:13 pts/0 00:00:00 /bin/sh /CA_APM/DB/1070/installer/server/initcluster.sh postgres postgres /CA_APM/DB/1070 /CA_APM/DB/1070/data 5432 DEFAULT

root 52237 52181 0 15:13 pts/0 00:00:00 su -s /bin/sh - postgres -c mv /CA_APM/DB/1070/data/postgresql.conf.52181 /CA_APM/DB/1070/data/postgresql.conf

postgres 52238 52237 0 15:13 ? 00:00:00 mv -i /CA_APM/DB/1070/data/postgresql.conf.52181 /CA_APM/DB/1070/data/postgresql.conf

root 52378 47896 0 15:15 pts/0 00:00:00 grep --color=auto postgres

Resolution

We killed the process "mv -i /CA_APM/DB/1070/data/postgresql.conf.52181 /CA_APM/DB/1070/data/postgresql.conf" which allowed the installer to complete.