API Portal service containers are not starting up correctly
search cancel

API Portal service containers are not starting up correctly

book

Article ID: 232138

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

When restarting Portal 4.5 the startup process got stuck and the containers are not started correctly. The docker service status "systemctl status docker" shows the following error message:

Jan 04 10:06:42 <portalHost.PortalDomainName> dockerd[2140]: time="2022-01-04T10:06:42.444910380-08:00" level=info msg="Error logging in to endpoint, trying next endpoint" error="Get \"https://apim-portal.packages.ca.com/v2/\": x509: certificate is valid for *.jfrog.io, jfrog.io, not apim-portal.packages.ca.com"
Jan 04 10:06:42 <portalHost.PortalDomainName> dockerd[2140]: time="2022-01-04T10:06:42.445457205-08:00" level=error msg="Handler for POST /v1.41/auth returned error: Get \"https://apim-portal.packages.ca.com/v2/\": x509: certificate is valid for *.jfrog.io, jfrog.io, not apim-portal.packages.ca.com"

Environment

Release : 4.5, 4.5.0.1

Component : API PORTAL

Cause

The portal containers URI in Docker Hub are changed to caapim and the URI "apim-portal.packages.ca.com" is no longer available.

Resolution

The portal startup script (portal.sh) will reach out to Docker Hub to retrieve the latest containers for the API Portal. The image URI at the Docker Hub is now changed to caapim and apim-portal.packages.ca.com URI is no longer available. As a result, the portal startup process failed to start the portal services.

The updated portal.sh script (apim-portal-4.5.0.1-patch.zip) is available here: https://support.broadcom.com/external/content/release-announcements/CA-API-Developer-Portal-Solutions--Patches/3010 

Back up the existing portal.sh file and then replace with this file. You can use this file for Portal 4.5 and 4.5.0.1 versions.

Note: If you apply this patch on Portal 4.5 then the portal_dispatcher container and the Portal UI will show the version as 4.5.0.1 but the portal is not upgraded to 4.5.0.1. You still need to apply the "API Developer Portal Installer 4.5.0.1.tar.gz" patch to upgrade the portal to the 4.5.0.1 version. This patch file is also available in the above-noted link.