[Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)

Blake Carver blake.carver at lyrasis.org
Mon Jan 18 12:17:10 EST 2021

Yep, that's it. ArchivesSpace is unhappy with 11.
Java 8 only:
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Philip Webster <philip.webster at sheffield.ac.uk>
Sent: Monday, January 18, 2021 11:57 AM
To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)


Java –version on the affected server gives the following:

openjdk version "" 2020-11-04

OpenJDK Runtime Environment (build

OpenJDK 64-Bit Server VM (build, mixed mode, sharing)



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Andrew Morrison
Sent: 15 January 2021 14:51
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)

Which version of Java are you running?

See http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-February/007388.html


On 13/01/2021 12:56, philip.webster at sheffield.ac.uk<mailto:philip.webster at sheffield.ac.uk> wrote:


We're currently in the process of deploying ArchivesSpace 2.8.1 to our production server following a lengthy period of testing and development on some other servers. Strangely, the public user interface is failing to load due to a Ruby dependency not being pulled in when the service starts up. The dependency is SASSC, which is present in the gems folder within the ArchivesSpace 2.8.1 installation.

An error message appears in the logs suggesting that SASSC isn't being imported due to it not having native extensions built, and in turn that causes a 500 error to be visible in the browser together with a stack trace showing the root cause to be the missing library. I tried building the extension using the native Ruby tools in our Linux distribution and found that had no effect. After some lengthy investigation it turned out that the development and test servers do not even have the native Ruby packages installed, and that everything runs entirely through jRuby. That being the case, I have no idea how to solve the issue with this dependency.

None of this is mentioned in the documentation, so I’m at a loss as to what to do next.

Does anyone have any suggestions?


Philip Webster

The University of Sheffield


Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210118/d235c328/attachment.html>

More information about the Archivesspace_Users_Group mailing list