APAR status
Closed as program error.
Error description
Post upgrading to 2018.4.1.16 the scripts dbstatus and the status scripts in the portal-www admin container report the Mysql service to be down, while in fact the DB pod is up and running and report its status as Primary.
Local fix
N/A
Problem summary
The dbstatus and status scrips report Mysql service being down, while it's up and running. This occurs when the default service address provided by Kubernetes is not the full address, and therefore nsloop with the -nosearch argument fails to find the database service. This results in the admin container believing that the database is down when it is not.
Problem conclusion
Fix targeted at release 2018.4.1.17, v10.0.1.4, and v10.0.3.0
Temporary fix
Comments
APAR Information
APAR number
LI82121
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
18X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-04-28
Closed date
2021-08-05
Last modified date
2021-08-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
R18X PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 September 2021