transfer not starting

[Maddalena Ghiotto]

Hi, first of all, I must share that I am at my first steps in using docker.
I'm trying to work with archivematica developer environment to make some changes to the code in my instance. So far, I only addedd a new transfer source directory with new data in the storage container. I'm not sure how that could have affected things (I now see the new folder correctly in the transfer tab UI) but now when I start the transfer nothing happens.

These are the error I found running docker compose logs --follow

nginx-1                    | 2025/12/04 14:22:25 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /status/?1764858145866 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/" 

nginx-1                    | 2025/12/04 14:22:28 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /transfer/status/?1764858148871 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:28 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /media/images/bullet_delete.png HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:31 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /status/?1764858151861 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:37 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /status/?1764858157861 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:39 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /transfer/status/?1764858159863 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:39 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /media/images/bullet_delete.png HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

nginx-1                    | 2025/12/04 14:22:43 [error] 21#21: *1 archivematica-dashboard could not be resolved (2: Server failure), client: <CLIENT_IP>, server: _, request: "GET /status/?1764858163863 HTTP/1.1", host: "<HOST_IP>:62080", referrer: "http://<HOST_IP>:62080/transfer/"

archivematica-mcp-server-1       |     with self.wrap_database_errors:
archivematica-storage-service-1  |     with self.wrap_database_errors:

elasticsearch-1                  | {"@timestamp":"2025-12-04T14:22:38.172Z", "log.level": "WARN", "message":"Failed to revoke access to default inference endpoint IDs: [rainbow-sprinkles, rerank-v1, multilingual-embed-v1, elser-v2], error: org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[am-node][inference_utility][T#1]","log.logger":"org.elasticsearch.xpack.inference.services.elastic.authorization.ElasticInferenceServiceAuthorizationHandler","elasticsearch.cluster.uuid":"<CLUSTER_UUID>","elasticsearch.node.id":"<NODE_ID>","elasticsearch.node.name":"<NODE_NAME>","elasticsearch.cluster.name":"<CLUSTER_NAME>"}

Does anybody have any idea how to fix it or how to troubleshoot further?
Thank you

[Douglas Cerna]

Hello,

You could remove the --follow flag in the logs command to see the full log from when you created the service containers.

Also, I think it's easier to inspect each service logs separately, and for errors such as "when I start the transfer nothing happens" I'd check the containers in this order:

docker compose logs archivematica-mcp-server

docker compose logs archivematica-storage-service

docker compose logs archivematica-dashboard

docker compose logs archivematica-mcp-client

When there's any problem you usually see Python tracebacks in the logs that you need to figure out (file and directory permission issues, database connection errors, etc). And if the transfer didn't start I don't think you should worry about the archivematica-mcp-client yet.

This is the logs command reference in case you haven't seen it yet https://docs.docker.com/reference/cli/docker/compose/logs/

Hope this helps.

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/archivematica/123e8c57-450d-4842-aba1-71f70257432an%40googlegroups.com.

--

Douglas Cerna (he/him),
Software Developer, Artefactual Systems Inc.
http://www.artefactual.com