Azure Blob Upload Fails With Request Inputs Is Out of Range Error

Symptom

A worker reports failed to upload file to the external object store, and restarting the service or rebooting the host does not clear the error.

In affected cases, Cribl logs an error similar to request inputs is out of range while retrying the same staged file.

Environment

• Cribl Stream
• Azure Blob Storage destination
• Self-managed deployment
• Last validated on version 4.17.0

Resolution

1. Identify the staged file that is failing under the Azure Blob output staging directory, for example under /opt/cribl/state/outputs/staging/<destination_name>/....
2. Manually remove the stuck staging file to stop the retry loop and clear the persistent error. Note that removing the file causes data loss for that file.
3. Review the pipeline field used in the destination partition expression and confirm it cannot contain unexpectedly long values such as URLs.
4. Update the pipeline so the extracted field only contains valid values. For example, exclude values containing :// or enforce a maximum length before the value is used in the partition path.
5. Update the Azure Blob destination partition expression so the generated blob name cannot exceed Azure’s 1024-character blob name limit.

Cause

A field used in the partition path contained a URL instead of the expected username value.

That long value was appended to the partition path, producing an Azure blob name longer than Azure’s 1024-character limit, which caused the request inputs is out of range error.

Because the staged file remained on disk, Cribl kept retrying the same file, so the error persisted even after a worker restart.

Last Validated

4.17.0

Additional Information

Some destination upload errors are transient and may clear after later retries, but the specific request inputs is out of range error persists until the offending staged file is removed or otherwise handled.

To prevent files with persistent destination errors from retrying indefinitely, enable dead-lettering on the Blob destination and configure a reasonable maximum retry value under the destination’s advanced settings.