Cloudera Docs

Troubleshooting

If the configuration synchronization process fails or the Cloudera Data Engineering Service does not restart successfully, perform the following steps to diagnose and resolve the issue.

  1. Retry the synchronization.
    Temporary network fluctuations or environmental issues can cause transient failures. Before conducting a deeper investigation, attempt to run the process again.
    1. Update and synchronize the stale configurations and click Review and Sync.
    2. Click Restart and Sync.
  2. Review Cloudera Data Engineering Service event logs.
    1. In the Cloudera console, click the Data Engineering tile. The Cloudera Data Engineering Home page is displayed.
    2. Click Administration in the left navigation menu. The Administration page is displayed.
    3. In the Services column, click the Service Details icon for the Cloudera Data Engineering service you want to review the event logs.
    4. Click Monitoring > Logs.
    5. Review the event logs to identify which Kubernetes pod is failing and to locate the error message causing the failure.
  3. Inspect Cloudera Data Engineering namespaces.
    Isolate the root cause by checking the health of the underlying Kubernetes pods.
    1. Access your Kubernetes environment monitoring tools.
    2. Examine the pod statuses within the dex-base and dex-app namespaces.
    3. Look for any pods that are failing to spin up or are trapped in an Error or CrashLoopBackOff state.
  4. Contact Cloudera Support.
    If you cannot resolve the synchronization failure using the previous steps, reach out to Cloudera Support. To expedite the troubleshooting process, gather and attach the required diagnostic information before submitting your ticket.
    • The exported event logs.
    • The dex-cp pod logs, which are located within the cdp namespace.