Enable db init job logs

You can enable db init job logs for troubleshooting.

Procedure

  1. To enable db init job logs, use the following specification under baw.configuration[x].upgrade_job in the custom resource configuration:
      baw_configuration:
      - name: instance1
        upgrade_job:
          trace_specification: "WLE.*=all:com.ibm.bpm.*=all:com.ibm.workflow.*=all"
  2. To see the logs, you can log in to the workflow server pod.

    The following example shows how to check the db init job logs in Business Automation Workflow server pod:

    $ kubectl exec -it icp4adeploy-instance1-ibm-workflow-server-0 bash
    $ cd /logs/application/icp4adeploy-instance1-baw-db-init-job-sj6vd
    $ ls -l
    -rw-r--r--. 1 1000710000 root 145410690 May 10 06:36 bootstrapData_2023.05.10.06.34.12.log
    -rw-r--r--. 1 1000710000 root     21214 May 10 06:29 dbConfig_check2023.05.10.06.30.08.167.log
    -rw-r--r--. 1 1000710000 root    814422 May 10 06:33 dbConfig_init2023.05.10.06.30.13.869.log
    
    Note: Use this option to collect log or trace files when you report issues to IBM.
  3. To copy the log or trace files from the pod to the local directory, run either of the following commands.
    • To copy individual db init log files from the pod:
      kubectl cp 
      <baw-namespace>/<baw-server-pod-name>:logs/application/<db-init-job-pod-name>
      /bootstrapData_timestamp.log
      <local-path>/bootstrapData_timestamp.log
      
    • To copy all log files from the pod to the local:
      kubectl cp <baw-namespace>/<baw-server-pod-name>:logs/application/<db-init-job-pod-name> <local-path>
  4. Alternatively, you can find the logs in your storage.

    To see the log or trace files from the storage, run the following commands:

    • To see the name of the log persistent volume claim (PVC), run the following command:
      $ kubectl get pvc|grep logs-storage-pvc
    • To see the name of the persistent volume (PV), run the following command:
      kubectl describe pvc pvc_name
    • To see the folder path, run the following command:
      kubectl describe pv pv_name
    • Go to the log folder path to check the db init logs, see the example:
      $ cd /nfsdata/tensor-icp4adeploy-bawins1-baw-logs-storage-pvc-pvc-dc165a5e-337e-47eb-9fe8-0a7a1df10556/icp4adeploy-bawins1-baw-db-init-job-sj6vd
      $ ls -l
      -rw-r--r-- 1 1000710000 root 145410690 May 9 23:36 bootstrapData_2023.05.10.06.34.12.log
      -rw-r--r-- 1 1000710000 root     21214 May 9 23:29 dbConfig_check2023.05.10.06.30.08.167.log
      -rw-r--r-- 1 1000710000 root    814422 May 9 23:33 dbConfig_init2023.05.10.06.30.13.869.log