📦
Storage service
  • Introduction
  • How-to: basic operations
    • Ingest a bag into the storage service
    • Look up an already-stored bag in the storage service
    • Look up the versions of a bag in the storage service
  • How to: advanced usage
    • Getting notifications of newly stored bags
  • How to: debugging errors
    • Where to find application logs
    • Manually marking ingests as failed
  • Reference/design decisison
    • The semantics of bags, ingests and ingest types
    • How identifiers work in the storage service
    • How files are laid out in the underlying storage
    • Compressed vs uncompressed bags, and the choice of tar.gz
  • Developer information/workflow
    • An API reference for the user-facing storage service APIs
    • Key technologies
    • Inter-app messaging with SQS and SNS
    • How requests are routed from the API to app containers
    • Repository layout
    • How Docker images are published to ECR
  • Wellcome-specific information
    • Our storage configuration
      • Our three replicas: S3, Glacier, and Azure
      • Using multiple storage tiers for cost-efficiency (A/V, TIFFs)
      • Small fluctuations in our storage bill
      • Delete protection on the production storage service
    • Wellcome-specific debugging
      • Why did my callback to Goobi return a 401 Unauthorized?
    • Recovering files from our Azure replica
    • Awkward files and bags
    • Deleting files or bags bags from the storage service
Powered by GitBook
On this page
  1. Wellcome-specific information
  2. Wellcome-specific debugging

Why did my callback to Goobi return a 401 Unauthorized?

When Goobi sends a bag to the storage service, it includes a callback URL. This URL is called by the notifier when the bag is successfully stored.

If a bag takes a long time to ingest (or especially if it gets stuck), the notifier can return an error:

Callback failed for: [ingest ID], got 401 Unauthorized!

This is because Goobi's callback URLs are only valid for three days. If a bag takes more than three days to store, the callback URL will expire.

This isn't a major issue – the bag will still be stored correctly, but somebody will need to manually advance it in Goobi.

PreviousWellcome-specific debuggingNextRecovering files from our Azure replica

Last updated 1 year ago