IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift: Difference between revisions

From Wiki
No edit summary
Line 29: Line 29:
  oc describe pod/mycd-ibm-connect-direct-0
  oc describe pod/mycd-ibm-connect-direct-0


the output
get the output and check




I suggest to you open a case on IBM
==


= Ver também =
= Ver também =

Revision as of 17:05, 14 March 2024

Get Pods
 oc get pod

the output

NAME                        READY   STATUS             RESTARTS       AGE
mycd-ibm-connect-direct-0   0/1     CrashLoopBackOff   19 (55s ago)   74m
Check logs in Pod
oc logs mycd-ibm-connect-direct-0

the output

[2024/03/13 16:31:07.38 ] | [INFO]  | Running entry script
[2024/03/13 16:31:07.44 ] | [INFO]  | Initializing deployemnt
[2024/03/13 16:31:07.46 ] | [INFO]  | Populating configuration parameters
[2024/03/13 16:31:08.18 ] | [INFO]  | SUM enabled is set to true
[2024/03/13 16:31:08.19 ] | [INFO]  | New deployment detected
[2024/03/13 16:31:08.25 ] | [INFO]  | Applying default configuration
[2024/03/13 16:31:08.28 ] | [ERROR] | The certificate/password for secure plus configuration is not provided. Line no: 135
[2024/03/13 16:31:08.35 ] | [INFO]  | Exiting


Verifying Pod definitions
oc describe pod/mycd-ibm-connect-direct-0

get the output and check


I suggest to you open a case on IBM


==

Ver também