Transfers not appearing on Transfer tab after migrating server

[Micah Ellison]

Hello,

I migrated an Archivematica 1.15.1 installation to a new Ubuntu 22.04.4 LTS machine after using apt to install, and so far everything seems to work except that transfers don't appear in the the Transfer tab. I'm wondering if anyone could help me narrow this down.

The problem

On the new machine, when I set up a new test transfer on a small file (4.1 MB) and click "Start transfer" I see the same message as on the old machine: Transfer "Test" started with processing configuration "default". However, no information appears in the table below like it does on the old machine.

Things I've tried

- Everything in the "Transfer Won't Start" documentation

- Researched the issue on this forum and GitHub. This issue looks similar, though it's from several versions ago, has no resolution, and there are slightly different symptoms in the database. I don't see anything in the release notes for 1.16 that suggests a fix for this issue.

- Looked through the logs, browser data, and database for clues (see below).

- Increasing various timeout and max file size settings in configuration, however I don't think those are related since this is such a small file and nobody else is doing anything on this machine.

Log findings

- No errors found in any log in /var/log/archivematica

- storage_service.log shows INFO entries about moving files, and I've verified that the file exists in the path specified in the last log entry, a subdirectory of /archivematica/sharedDirectory/tmp/.

- MCPServer.log has no new entries, however, on the old machine, there is a lot of INFO chatter starting with the word "Running" when I run the same transfer.

Browser developer tools

- No console errors reported after clicking "Start transfer"

- In the Network tab, I see the Transfer page constantly sending requests to /status that always return one of these two values:

  - {"objects": [], "mcp": true}

  - {"sip": 0, "transfer": 0, "dip": 0}

- The old machine, on the other hand, shows lots of information in "objects" in the first response and shows a value of 1 for "transfer" in the second response.

MCP database

A new record gets created in the Transfer table with a transferUUID and an accessionID that matches my input in the UI, but every other field is blank, 0, or NULL.

+--------------------------------------+-----------------+------+-------------+---------------------+----------------+-------------+-------+--------+----------------------------+----------+------------------+--------------+--------+
| transferUUID                         | currentLocation | type | accessionID | sourceOfAcquisition | typeOfTransfer | description | notes | hidden | transferMetadataSetRowUUID | dirUUIDs | access_system_id | completed_at | status |
+--------------------------------------+-----------------+------+-------------+---------------------+----------------+-------------+-------+--------+----------------------------+----------+------------------+--------------+--------+
| 59b7ee73-780a-4702-82f7-dbf02d8101ce |                 |      | Test        |                     |                |             |       |      0 | NULL                       |        0 |                  | NULL         |      0 |
+--------------------------------------+-----------------+------+-------------+---------------------+----------------+-------------+-------+--------+----------------------------+----------+------------------+--------------+--------+

On the old working server, the currentLocation value is filled out. However, I'm not familiar enough with the code to figure out what happens between this record being created and that field being populated.

Any troubleshooting suggestions welcome!

Thanks,

-Micah