ca pc 3.7.3 to 3.7.11 upgrade fails

[Shanmuga Sundaram MP]

Hi,
   We are currently running capm 3.7.3 on linux and today when we try to upgrade the CAPC it is showing less disk space but we have enough space for installation target. We don't use the default path instead we use different path but somehow it is showing the default path eventhough the installation path what it is showing in the instructions are correct but this installation file doesn't considering this.

Any thoughts . Can someone help me here. 

Thanks.

[Carlos Radice]

Does have /tmp space?
Did you try to move forward with the installation?

[Jeffrey Pinard]

There is a bug in InstallAnywhere we use to install the product.  It can't determine free space correctly in some cases.

We put in a workaround to get installer to run.

https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=121288

Pass on the command line  -DCHECK_DISK_SPACE=OFF

It won't check disk space.  Be sure there is enough disk space in /tmp and /opt/CA to upgrade the product.

[Shanmuga Sundaram MP]

Hi Jeffrey,
    I have tried that with the disk space off command but this time it throws the error as below:
Preparing to install
WARNING: /tmp does not have enough disk space! Attempting to use /root for install base and tmp dir.

WARNING! The amount of /root disk space required to perform this installation is greater than what is available. Please free up at least 1249947 kilobytes in /root and attempt this installation again.

But when I check the /tmp I noticed the below directories occupies more space 
ls -ld /tmp/install.dir.*
drwxr-xr-x. 3 root root 4096 May 15 03:15 /tmp/install.dir.13607
drwxr-xr-x. 4 root root 4096 May 15 03:22 /tmp/install.dir.20887
drwxr-xr-x. 4 root root 4096 Aug 20 2019 /tmp/install.dir.23142
drwxr-xr-x. 4 root root 4096 May 15 03:30 /tmp/install.dir.23229
drwxr-xr-x. 3 root root 4096 May 15 05:58 /tmp/install.dir.31846
drwxr-xr-x. 4 root root 4096 May 15 02:57 /tmp/install.dir.6045

So shall I remove them and try to proceed to install?.

[Jeffrey Pinard]

You can remove those old /tmp/installs.dir.XXXXX directories.  They are previous failures and consuming disk space from /tmp.

we need like 4GB free /tmp space.  This is so it can extract the installer, and create temp files to install the product to it's final location.

If you don't have enough /tmp space, or /tmp is noexec perms, you can: 
   export IATEMPDIR=/sometempplace

then run the installer and it will use /sometempplace for extracting the installer/jre/etc.

[Shanmuga Sundaram MP]

Hi Jeffrey,
   I tried that too but I see the below information
Disk Space Information (for Installation Target):
Required: 2,581.4 MegaBytes
Available:1,782.39 MegaBytes

But it doesn't point to /tmp instead it is pointing to /opt/CA. My installation directory is different and all the installation path is showing correctly but only the above one shows incorrect

[Jeffrey Pinard]

The IATEMPDIR= setting only tells the installer where to extract itself temporarily to run the install, if there isn't enough space in /tmp.

You still need to also do -DCHECK_DISK_SPACE=OFF argument to turn off the available space checker installer does for our product (due to the bug in InstallAnywhere).

[Shanmuga Sundaram MP]

I tried both the one you mentioned but still getting the same as above.

[Jeffrey Pinard]

I see you opened a case, good, I was gonna suggest that. 

Working with support person on next steps.