To troubleshoot the UDCA in Apigee hybrid, look at the log files. UDCA logs are
written to stdout/stderr and can be viewed using the kubectllogs command.
On the Kubernetes administration machine, execute the following command:
kubectl logs pod_name apigee-udca -n namespace
The following table lists common error messages that might
appear in the UDCA log files and their meanings. Log messages will
include a timestamp and often a stacktrace or other information to
help you diagnose and fix the issue.
Entry Type
Log message
Meaning
Error
Failed to create directory for dataset
dataset_name
The directory configured for the given dataset did not exist
and the UDCA failed to create it. It could be a permission issue in
the setup.
This issue prevents UDCA from starting.
Error
Shutdown action was interrupted. It is possible that some
data will be lost
As part of a shutdown, UDCA tries to upload all files on disk.
This message indicates that the shutdown took longer than
expected and some data might not be uploaded and hence lost.
Error
Scheduled DatasetHandler for dataset
dataset_name encountered an exception.
An attempt to perform an action on the given dataset
encountered an unexpected exception while polling the configured
directory or while uploading the files.
Error
Upload failed for file filename. Max Retries
exceeded! Moving dir to failed folder.
The UDCA failed to upload the given file and moved the file to
the dataset's /failed subdirectory.
Error
Re-queuing files from failed directory encountered an exception.
The UDCA requeues files from the /failed directory after a
successful upload. This ensures that the UDCA retry to upload files
after network/upstream issues are resolved.
This message indicates that UDCA experienced an error when
trying to requeue the file.
Error
Shutting down datasetHandler encountered an exception.
The UDCA experienced an exception when trying to shut down.
Error
Failed to move file from directory_name to
directory_name.
The UDCA encountered an exception while moving a file between
sub-directories for internal lifecycle management.
Error
Failed to delete file filename.
The UDCA encountered an exception while deleting a file after a
successful upload.
Error
Failed to rename file from file_name to file_name.
The UDCA encountered an exception while appending UUID to a file while renaming.
Warning
Received 429 - Too many Requests from upstream service.
Skipping remaining files in this iteration and will retry
again
The UDCA received an error that it had exceeded its quota from
an upstream service. As a result, the UDCA skipped the remaining
files in this iteration and will retry in the next interval.
Warning
File upload failed for filename.
error_message
The UDCA failed to upload the given file due to the returned
error.
The UDCA will attempt to upload the file 3 times before moving
it to the dataset's /failed subdirectory.
Warning
Request request_URI timed out. Aborting request
The specified asynchronous request to upload the file timed out
and was cancelled.
Warning
Request request_URI failed. Exception
exception
The specified asynchronous request failed with an exception.
Warning
Metrics Computation Failed:
error_message
The periodic computation of the UDCA's file system metrics
encountered an exception.
Warning
Will attempt to upload api file file_name uncompressed
The UDCA encountered an issue trying to compress the file before uploading.
The uncompressed file will be uploaded in this case.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis documentation pertains to version 1.10 of the Apigee hybrid system and provides details on how to troubleshoot the UDCA.\u003c/p\u003e\n"],["\u003cp\u003eUDCA logs can be accessed and viewed using the \u003ccode\u003ekubectl logs\u003c/code\u003e command on the Kubernetes administration machine, which is shown using an example within the document.\u003c/p\u003e\n"],["\u003cp\u003eThe log messages in the UDCA logs, which are detailed in the document's table, will show errors regarding file management issues, including directory creation failures, upload failures, and file manipulation errors.\u003c/p\u003e\n"],["\u003cp\u003eThe log messages will also report warning errors, which can arise from upstream service rate-limiting, file compression issues, or problems with asynchronous requests.\u003c/p\u003e\n"],["\u003cp\u003eThe provided table in the document serves as a guide to understanding various error and warning messages that may appear in the UDCA logs, along with their meanings, to help diagnose and fix issues.\u003c/p\u003e\n"]]],[],null,["| You are currently viewing version 1.10 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nTo troubleshoot the UDCA in Apigee hybrid, look at the log files. UDCA logs are\nwritten to `stdout/stderr` and can be viewed using the [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) `logs` command.\n\nOn the Kubernetes administration machine, execute the following command: \n\n```\nkubectl logs pod_name apigee-udca -n namespace\n```\n\nThe following table lists common error messages that might\nappear in the UDCA log files and their meanings. Log messages will\ninclude a timestamp and often a stacktrace or other information to\nhelp you diagnose and fix the issue.\n\n| Entry Type | Log message | Meaning |\n|------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Error | `Failed to create directory for dataset `\u003cvar translate=\"no\"\u003edataset_name\u003c/var\u003e | The directory configured for the given dataset did not exist and the UDCA failed to create it. It could be a permission issue in the setup. This issue prevents UDCA from starting. |\n| Error | `Shutdown action was interrupted. It is possible that some data will be lost` | As part of a shutdown, UDCA tries to upload all files on disk. This message indicates that the shutdown took longer than expected and some data might not be uploaded and hence lost. |\n| Error | `Scheduled DatasetHandler for dataset `\u003cvar translate=\"no\"\u003edataset_name\u003c/var\u003e` encountered an exception.` | An attempt to perform an action on the given dataset encountered an unexpected exception while polling the configured directory or while uploading the files. |\n| Error | `Upload failed for file `\u003cvar translate=\"no\"\u003efilename\u003c/var\u003e`. Max Retries exceeded! Moving dir to failed folder.` | The UDCA failed to upload the given file and moved the file to the dataset's `/failed` subdirectory. |\n| Error | `Re-queuing files from failed directory encountered an exception.` | The UDCA requeues files from the `/failed` directory after a successful upload. This ensures that the UDCA retry to upload files after network/upstream issues are resolved. This message indicates that UDCA experienced an error when trying to requeue the file. |\n| Error | `Shutting down datasetHandler encountered an exception.` | The UDCA experienced an exception when trying to shut down. |\n| Error | `Failed to move file from `\u003cvar translate=\"no\"\u003edirectory_name\u003c/var\u003e` to `\u003cvar translate=\"no\"\u003edirectory_name\u003c/var\u003e`.` | The UDCA encountered an exception while moving a file between sub-directories for internal lifecycle management. |\n| Error | `Failed to delete file `\u003cvar translate=\"no\"\u003efilename\u003c/var\u003e`.` | The UDCA encountered an exception while deleting a file after a successful upload. |\n| Error | `Failed to rename file from `\u003cvar translate=\"no\"\u003efile_name\u003c/var\u003e` to `\u003cvar translate=\"no\"\u003efile_name\u003c/var\u003e`.` | The UDCA encountered an exception while appending UUID to a file while renaming. |\n| Warning | `Received 429 - Too many Requests from upstream service. Skipping remaining files in this iteration and will retry again` | The UDCA received an error that it had exceeded its quota from an upstream service. As a result, the UDCA skipped the remaining files in this iteration and will retry in the next interval. |\n| Warning | `File upload failed for filename. `\u003cvar translate=\"no\"\u003eerror_message\u003c/var\u003e | The UDCA failed to upload the given file due to the returned error. The UDCA will attempt to upload the file 3 times before moving it to the dataset's `/failed` subdirectory. |\n| Warning | `Request request_URI timed out. Aborting request` | The specified asynchronous request to upload the file timed out and was cancelled. |\n| Warning | `Request request_URI failed. Exception `\u003cvar translate=\"no\"\u003eexception\u003c/var\u003e | The specified asynchronous request failed with an exception. |\n| Warning | `Metrics Computation Failed: `\u003cvar translate=\"no\"\u003eerror_message\u003c/var\u003e | The periodic computation of the UDCA's file system metrics encountered an exception. |\n| Warning | `Will attempt to upload api file `\u003cvar translate=\"no\"\u003efile_name\u003c/var\u003e` uncompressed` | The UDCA encountered an issue trying to compress the file before uploading. The uncompressed file will be uploaded in this case. |"]]