[Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)

[library at princeofpeaceabbey.org]

Quoting Blake Carver <blake.carver at lyrasis.org>:

Blake: I am using Amazon Corretto\jdk 1.8.0_265 instead of Java 8

Br Raphael

If this is a second sending I did not see that I sent it

> Yep, that's it. ArchivesSpace is unhappy with 11.
> Java 8 only:
> https://archivesspace.github.io/tech-docs/administration/getting_started.html
> ________________________________
> 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)
>
>
> Hi,
>
> Java –version on the affected server gives the following:
>
> openjdk version "11.0.9.1" 2020-11-04
>
> OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04)
>
> OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04,  
> mixed mode, sharing)
>
>
>
> Regards,
>
>
>
> Phil
>
>
>
> 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
>
> Andrew.
>
>
>
> On 13/01/2021 12:56,  
> philip.webster at sheffield.ac.uk<mailto:philip.webster at sheffield.ac.uk>  
> wrote:
>
> Hi,
>
> 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?
>
>
>
> Thanks,
>
>
>
> 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>
>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group