IBM Support

IBM API Connect Mustgather - Portal 2018

Troubleshooting


Problem

Contact IBM Support if you experience a problem with IBM API Connect. Use the details in this document to provide all of the relevant information to the Support team to help with problem resolution.

Resolving The Problem

IMPORTANT
This document has been replaced. Please use the following document instead: API Connect v2018 postmortem tool: Collect the MustGather output required by IBM support with a single command
  • Deprecated Instructions: Do Not Use

    Please collect and upload following data to CASE.

    apiconnect-up.yaml

    Also output file of 'apic logs' ran as root. (only for OVA)

    Following is example, pod names will vary, and '-n <namespace>' may also be needed depending on users config:
    > kubectl get pods
    NAME                                                                   READY     STATUS    RESTARTS   AGE
    portal-apic-portal-db-mct5r                                   2/2       Running   0          4d
    portal-apic-portal-nginx-74d9b96c85-2f95c       1/1       Running   0          4d
    portal-apic-portal-nginx-74d9b96c85-bzftb        0/1       Pending   0          4d
    portal-apic-portal-nginx-74d9b96c85-z6wdk      0/1       Pending   0          4d
    portal-apic-portal-www-zhqxf                               2/2       Running   0          4d

    Then for each pod output from previous command:

    For www pod:
    > kubectl logs portal-apic-portal-www-zhqxf admin > admin.log
    > kubectl logs portal-apic-portal-www-zhqxf web > web.log
    For db pod:
    > kubectl logs portal-apic-portal-db-mct5r db > db.log
    > kubectl logs portal-apic-portal-db-mct5r dbproxy > dbproxy.log
    For nginx pod:
    > kubectl logs portal-apic-portal-nginx-74d9b96c85-2f95c > nginx.log
    (ignoring the 2 status 'pending' pods)
    Get the pod descriptions:
    > kubectl describe pod portal-apic-portal-db-mct5r > dbpod.desc
    > kubectl describe pod portal-apic-portal-nginx-74d9b96c85-2f95c > nginxpod.desc
    > kubectl describe pod portal-apic-portal-www-zhqxf > wwwpod.desc
    copy off and upload all the generated files.
    Extra logs for CASEs involving pods restarting
    For these PMRs, it is also worth getting the logs from the previous pod incarnation (to see why it failed), to do this, run the same kubectl logs commands as above, but add the '-p' option, e.g.:
    kubectl logs -p portal-apic-portal-db-mct5r db > db.log
    Note: We are working on creating a command which will collect all this detail. It is still work in progress.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Component":"Portal","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"2018.x","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 March 2020

UID

ibm10717015