Dashboard -/- Storage ("Error retrieving source directories")

393 views
Skip to first unread message

C.C. Miller

unread,
Feb 6, 2014, 3:00:29 PM2/6/14
to archiv...@googlegroups.com
We have a 1.0 instance standing, and all seems well. With the crippling exception of the Dashboard refusing to see the Storage Server, erroring with "Error retrieving source directories: is the storage server running?" I've been poking around in various logs and trying to determine a cause but the returns are diminishing. Some context:

  • Storage server is running on port 8000 and appears to be (?) operating properly
  • A pipeline was established in Storage using the UUID of the Dashboard, this pipeline was verified to be associated with each Location
  • gearman service is running on :4370
    • i can telnet to this service and do things like `status` and see expected results
  • Default Locations exist (using Local Filesystem space), error persists even after establishing an additional Transfer Source location (that had lax permissions, jic)
  • the periodic /status call from Dashboard returns the following (expected) JSON:
    • {"transfer": 0, "sip": 0, "dip": 0}
  • the periodic /transfer/status call from Dashboard returns the following (expected?) JSON:
    • {"objects": [], "mcp": true}
  • There are foreboding errors in archivematicaDashboard.log that might hint at the problem but i'm super interested in wading through a bunch django stuff if someone here could recognize the issue instantly:
    • ServerUnavailable: Found no valid connections: [<GearmanConnection localhost:4730 connected=False>]
    • ERROR:django.request:Internal Server Error: /status/
  • The issue persists with all of the following Storage Service URL settings in Dashboard's Admin module:
...So anyway for reasons I can't determine yet, Dashboard simply can't communicate with Storage Server. Question mark. Could be that Storage Server isn't actually operating properly, but the error doesn't necessarily suggest that. The upshot is that I'm hoping somebody here has educated guesses that can trump my uneducated guesses.

Thanks,
Chris

C.C. Miller

unread,
Feb 14, 2014, 3:41:56 PM2/14/14
to archiv...@googlegroups.com
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.

Courtney Mumma

unread,
Feb 14, 2014, 7:41:02 PM2/14/14
to archiv...@googlegroups.com
Hi Chris,

Glad to hear you got things up and running. It's hard to know what was going on without intimate knowledge of your system, settings, etc., but your documentation of it here might be very helpful to other users. Thanks for sharing in such detail.

Best,
Courtney


--
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 post to this group, send email to archiv...@googlegroups.com.
Visit this group at http://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/groups/opt_out.



--
Courtney C. Mumma, MAS/MLIS
Archivematica Product Manager/Systems Analyst 
Artefactual Systems, Inc.
604-527-2056
Reply all
Reply to author
Forward
0 new messages