CA API GatewayAPI SECURITYCA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)CA API Gateway Enterprise Service Manager (Layer 7)STARTER PACK-7CA Microgateway
Patching can fail without providing an intuitive message on the SSGCONFIG menu console similar to below.
1) ID: CA_API_PlatformUpdate_64bit_v9.X-RHEL-2020-01-23 DESCRIPTION: Upgrades the CA API 64bit Platform to the 9.X-RHEL-2020-01-23 version. This patch requires that the 9.X Platform Update be installed first. It also requires a restart of the CA API Gateway Appliance. X) Exit menu
Please make a selection: 1 You have chosen to install the following patch " CA_API_PlatformUpdate_64bit_v9.X-RHEL-2020-01-23 " Press [Enter] to continue
Please wait while the patch is installed ... Patch ID CA_API_PlatformUpdate_64bit_v9.X-RHEL-2020-01-23 (Upgrades the CA API 64bit Platform to the 9.X-RHEL-2020-01-23 version. This patch requires that the 9.X Platform Update be installed first. It also requires a restart of the CA API Gateway Appliance.) is ERROR, last modified on 2020-02-18T08:28:38-0600 There were errors during the patch operation.
Press [Enter] to continue
Release : 9.2, 9.3
Component : API GATEWAY
The most common reason a patch will fail to install is simply disk space. First from the ssgconfig menu choose 3) Privileged shell Then check disk space below, # df -h
You want to be sure you have plenty of space in most mounts including /opt /tmp /var and /home.
Second, another common scenario for failure is stopping the gateway. Patches are uploaded by default to the gateways parent process sspc (controller.jar). You should not stop the gateway before applying a patch.
Third, logging for this menu (more detailed failures) are usually listed in the process controller log. which can be viewed at, /opt/SecureSpan/Controller/var/logs/sspc_0_0.log
This will usually have details on the patch application and at times rpm packager errors (and disk space check failures).
For problems not covered in this document you should open a support case for review and provide a df -h and a copy of the sspc_0_0.log