CA APM Enterprise Manager 10.7 install on Amazon Web Services (AWS) fails with "Not Enough Disk Space"
Article ID: 111209
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
Using root user installing APM EM 10.7 on Amazon Web Services (AWS) under Linux 7.4 fails with message:
=======
Not Enough Disk Space
---------------------
Warning!
This installation requires 1,614.86 MB of free disk space, but there are only 1,330.71 MB available at:
/caapim2/Introscope10.7.45
Please free at least 284.14 MB to proceed with the installation.
PRESS <ENTER> TO RECALCULATE AVAILABLE DISK SPACE,
OR TYPE 'QUIT' TO EXIT THE INSTALLER:
=======
/caapim2/Introscope10.7.45 is the specified install directory
Environment variable IATEMPDIR=/caapim2 is also defined and exported
The output of command "df -h" is:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.4G 112K 7.4G 1% /dev
tmpfs 7.4G 0 7.4G 0% /dev/shm
/dev/mapper/system-root 2.5G 1.1G 1.3G 44% /
/dev/xvda2 482M 73M 385M 16% /boot
/dev/mapper/system-home 488M 424K 452M 1% /home
/dev/mapper/system-opt 31G 225M 29G 1% /opt
/dev/mapper/system-tmp 11G 1.3M 9.9G 1% /tmp
/dev/mapper/system-var 488M 60M 393M 14% /var
/dev/mapper/system-varlog 488M 7.8M 445M 2% /var/log
/dev/mapper/system-varlogaudit 488M 2.7M 450M 1% /var/log/audit
/dev/xvdf 296G 63M 281G 1% /caapim
/dev/xvdd 394G 7.0G 367G 2% /caapim1
/dev/xvdg 493G 5.0G 463G 2% /caapim2
Therefore the filesystem /caapim2 being used has 400GB+ free and the installer seems to be checking the free space on the / filesystem instead of the /caapim2 filesystem.
=======
Not Enough Disk Space
---------------------
Warning!
This installation requires 1,614.86 MB of free disk space, but there are only 1,330.71 MB available at:
/caapim2/Introscope10.7.45
Please free at least 284.14 MB to proceed with the installation.
PRESS <ENTER> TO RECALCULATE AVAILABLE DISK SPACE,
OR TYPE 'QUIT' TO EXIT THE INSTALLER:
=======
/caapim2/Introscope10.7.45 is the specified install directory
Environment variable IATEMPDIR=/caapim2 is also defined and exported
The output of command "df -h" is:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.4G 112K 7.4G 1% /dev
tmpfs 7.4G 0 7.4G 0% /dev/shm
/dev/mapper/system-root 2.5G 1.1G 1.3G 44% /
/dev/xvda2 482M 73M 385M 16% /boot
/dev/mapper/system-home 488M 424K 452M 1% /home
/dev/mapper/system-opt 31G 225M 29G 1% /opt
/dev/mapper/system-tmp 11G 1.3M 9.9G 1% /tmp
/dev/mapper/system-var 488M 60M 393M 14% /var
/dev/mapper/system-varlog 488M 7.8M 445M 2% /var/log
/dev/mapper/system-varlogaudit 488M 2.7M 450M 1% /var/log/audit
/dev/xvdf 296G 63M 281G 1% /caapim
/dev/xvdd 394G 7.0G 367G 2% /caapim1
/dev/xvdg 493G 5.0G 463G 2% /caapim2
Therefore the filesystem /caapim2 being used has 400GB+ free and the installer seems to be checking the free space on the / filesystem instead of the /caapim2 filesystem.
Environment
CA APM Unix/Linux Enterprise Manager (EM) installer
Versions: 9.x, 10.x
Versions: 9.x, 10.x
Cause
Root cause appears to be due to the disk space check performed by InstallAnywhere, a third party application used by the Enterprise Manager installer.
Resolution
To workaround disable the InstallAnywhere disk space check as follows:
Define and export InstallAnywhere environment variable CHECK_DISK_SPACE=OFF e.g. for bash shell:
export CHECK_DISK_SPACE=OFF
Additional Information
The symptoms are similar to this existing KB article for an NFS mounted filesystem:
(So having the environment variable CHECK_DISK_SPACE=0 may also be a valid workaround)
APM Engineering confirmed that AWS filesytem is currently treated as a kind of NFS and a code change will be made to fix this problem (Defect DE380753) in a future release.
Feedback
Yes
No
Powered by
