IBM Support

context deadline exceeded error in pod logs

Troubleshooting


Problem

Some pods are failing to start and in the logs we can see 'Liveness probe failed: Get "https://9.254.36.139:8443/diag": context deadline exceeded (Client.Timeout exceeded while awaiting headers)    "
Note that that the same error is seen in other pods, like asset-files-api and event-logger-api pods.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"ARM Category":[{"code":"a8m3p000000UoRRAA0","label":"Administration-\u003EUpgrade"}],"ARM Case Number":"TS015076030","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.7.0;4.7.1;4.7.2;4.7.3;4.7.4;4.8.0;4.8.1;4.8.2;4.8.3;4.8.4;4.8.5"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
23 October 2024

UID

ibm17105604