For anyone else with this problem I have bittersweet news: I fixed this but A) have no idea how, B) ended up removing/installing archivematica components about a hundred times over the course of several days, and C) introduced/solved many subsequent issues during that time :-(
Some things to check, though, that plagued me during this procedure:
- make sure there's an MCP db and your archivematica user has access
- watch yr apache log for version mismatch announcements for mod_wsgi -- I ended up manually compiling/installing mod_wsgi over the one that shows up as an archivematica dependency, used this post, more or less
- make sure the archivematica directories that are supposed to exist actually do
- e.g. maybe you'll have to scp -r /local/git/clone/of/archivematica/src/archivematicaCommon/etc archivematicaHost:/etc/archivematica/archivematicaCommon (or more likely put it in an interim spot on yr archivematica host box and then sudo mv it into place
- if you see "NoSectionError: No section: 'client'" errors, u might be able to get around it with brute-force DB settings in /usr/share/archivematica/dashboard/settings/common.py
- also, before u lose your wits on any given failure, make sure to do ps aux | grep archivem* to make sure things are running that you need
Dunno what really fixed it. I tried a lot of stuff. If I had to guess it was the mod_wsgi. Maybe. Question mark.